The decision starts with the job
Before choosing a platform or commissioning software, write down the work that needs to happen. Pick one real customer, job, or document and follow it from start to finish. Who touches it? Where does information get copied? Which decisions depend on an email, a spreadsheet, or one person’s memory?
This gives you something more useful than a feature wish list: a picture of the workflow. A tool can have a long list of capabilities and still leave the most important handoff unresolved.
Look for the smallest useful intervention
There are usually three options. You can configure an existing product, connect the tools you already use, or build a custom application. Each can be the right choice.
Configure when your process fits a product reasonably well and the friction comes from setup, permissions, reporting, or training.
Connect when the individual tools work but information does not move between them. A focused integration can solve a recurring problem without replacing everything.
Build when a distinctive workflow is central to the business, existing tools repeatedly force compromises, or the product itself is what you are creating.
Count the cost of the whole workflow
Subscription prices are visible. Repeated entry, reconciliation, and correction are easier to overlook. Ask the people doing the work to identify those tasks and estimate their frequency.
Use estimates as a starting point, then measure a representative sample. Record the task, time spent, rework, and the conditions that make it harder. Avoid turning a rough guess into an exact return-on-investment claim.
A custom system also has ongoing costs: hosting, third-party services, maintenance, support, and changes as the business evolves. Compare the complete ownership picture on both sides.
Define a first release that can stand on its own
A first release should complete one useful workflow. It might take a lead from inquiry to qualified opportunity, or turn an approved document into a scheduled task.
Decide what belongs in that release and what can wait. Include the unglamorous work: importing data, handling exceptions, assigning permissions, and making the tool understandable to its users.
Make the decision with the team
The person buying the software and the person using it every day may see different problems. Bring both into the conversation. Walk through ordinary tasks and difficult examples, then agree on what a better result would look like.
Custom software is strongest when it has a clear job, a committed owner, and a feedback loop. Start there. The technology follows.
All field notes