Custom or ready-made?
Use an existing product when it supports the important workflow with manageable compromises. Consider custom software when a valuable, specific requirement cannot reasonably be met through configuration or integration.
Start a projectDescribe the workflow
Start with the work, not a list of screens. Follow a real task from its trigger to its outcome: who does it, what information moves and where decisions happen. Include exceptions, approvals and the records that must be kept.
Separate requirements that are essential from habits created by the current tool. A familiar spreadsheet layout is not necessarily a business requirement. A permission rule or an approval that protects a customer may be.
- The task and the people responsible
- Essential records, approvals and permissions
- What fails or gets repeated today
- Requirements that cannot be compromised
Test existing options
Try a representative task in a suitable ready-made product. Check the whole journey rather than a feature list. Can people complete the work, retrieve the records and handle an exception without building a manual system around it?
Configuration or a small integration may close the gap. Check subscription levels, API limits, export options and the effort of keeping the connection working. A product that nearly fits can still be the right choice if its remaining compromises are explicit and acceptable.
- A realistic workflow trial
- Data import and export
- Integration access and limits
- Permissions and the exception path
Compare ownership costs
Compare more than the initial build price or monthly subscription. Consider setup, migration, training, integration, maintenance and the time people spend compensating for gaps. Avoid claiming a saving until those assumptions have been checked.
Custom software needs an owner after launch. Someone must manage access, updates, backups, operating guidance and incident response. Owning the code gives options, but does not remove the ongoing work of running a system.
- Initial work and continuing provider charges
- Migration and training
- Maintenance and operational responsibility
- Exit options, documentation and account ownership
Choose a bounded start
If custom development is justified, choose the smallest complete workflow that is useful to the business. Write acceptance checks for both normal use and failure cases. Keep later ideas visible without making them all launch requirements.
The answer can be a combination: an existing accounting or customer system with a focused custom portal, for example. That is a possible architecture, not a claim about a client project. Discovery should establish whether the connection is practical before a build is agreed.
- Why existing options do not meet the essential need
- A useful first-release boundary
- Acceptance checks and realistic test data
- A handover and support plan
Your next step
Choose the smallest approach that reliably supports the important work. That may be a subscription, configuration, an integration or custom development. The decision should be explainable before the build starts.
The project brief helps you describe what exists today and what should improve. For scope and handover, read how delivery works and what affects project investment.
