The useful takeaway
Choose the system that fits the important workflow, not the longest feature list. A custom build makes sense when its value justifies the development and ongoing responsibility.
Start with the job, not the product demo
A good sales demo makes a platform look like the answer. The more useful question is whether your team can complete its everyday work with it. A customer record is only one piece of the journey: the enquiry may become a quote, a job, a handover and a customer update.
Before comparing tools, map one recent example. Name who handled it, the information they needed and the points where work was copied or delayed. That gives you a basis for judging a product, rather than choosing from a list of attractive features.
The four options worth comparing
A CRM, an off-the-shelf operational product, an integration and a custom app can each solve different parts of the problem. They are not always competing choices. Your final setup might combine a standard CRM with a focused custom dashboard.
| Approach | Strong fit | Watch for |
|---|---|---|
| CRM | Enquiries, customer relationships, pipeline stages and follow-up activity. | How job delivery, permissions and reporting work beyond the sales pipeline. |
| Off-the-shelf business software | A repeatable workflow well supported by an established product. | Workarounds for exceptions, per-user costs and access to your data. |
| Integration | Existing tools work, but records need to move between them. | API access, conflicting updates, connection failures and licence requirements. |
| Custom business app | A specific workflow, portal or working screen has a valuable gap. | Development scope, maintenance, hosting and clear ownership. |
When a CRM may be enough
If your main problem is tracking enquiries and remembering follow-ups, start by checking whether a suitable CRM can do that well. You may need a clear process, sensible configuration and a connection from the website rather than new software.
Test a complete example: create an enquiry, assign an owner, record a conversation, set a next action and mark the outcome. Ask how duplicate records, exports and permissions are handled. If the product supports the core work comfortably, custom development may add cost without enough benefit.
When a custom app earns its place
Custom development becomes useful when the missing workflow is important enough to justify building and maintaining it. Perhaps the team needs a planning screen that combines job commitments with capacity. Perhaps customers need controlled access to documents and actions tied to an internal record.
Describe the gap precisely. “Our current tools cannot show whether accepted work fits next week’s available hours” is a stronger reason than “we want our own app”.
A custom app does not need to replace everything. A first version can read agreed data, show one useful view and capture a limited set of actions. Existing accounting, email or scheduling tools may continue doing their jobs.
Compare the cost of running it, not just buying it
Ask what happens after the first month. Subscription fees, users, additional modules, hosting, backups, support and maintenance can all affect the decision. Include the work of moving records, training the team and checking the result.
For custom development, identify what is included in the initial build and what is separately agreed. Account access, source code arrangements, deployment, handover and maintenance responsibilities should be explicit.
For an existing product, check whether the integration or permission feature you need sits in a higher plan. A low headline price is less useful if the practical workflow depends on add-ons.
- Initial configuration or development.
- Migration and cleanup of existing records.
- Recurring licences, hosting and usage-based services.
- Training, support and maintenance responsibilities.
- Data export, account ownership and the effort needed to move later.
Run a realistic trial before committing
Choose a handful of representative records, including an awkward case. Work through the process with the person who actually does the job. Record where the system helps and where they still need another spreadsheet.
Check access as a restricted user, not only as the administrator. Check the customer-facing flow too, if one exists. A polished dashboard tells you little about how permissions and exceptions behave.
Avoid importing every live customer record into a trial before access and data handling are understood. Use an appropriate test dataset and share only the information needed for the evaluation.
A decision you can explain
Write a short decision note: the problem, the options considered, the reason for choosing one and the limits of the first phase. If you cannot explain why a custom build is needed, discovery is not finished.