Start by evaluating an existing CRM against your essential workflow. Choose a custom application when important requirements cannot be met reasonably through configuration or integrations, and when you can support its long-term operation.
Define the workflow before comparing products
Describe what happens from the moment an enquiry arrives to the point it is resolved. Identify the records, roles, documents, and decisions involved.
Separate essential requirements from preferences. An unusual screen layout is rarely a good reason to build an entire application.
When an existing CRM makes sense
An existing product is worth considering when your needs align with its supported processes, integrations, and permission model. Configuration can avoid substantial development and maintenance work.
Review pricing at your expected user count, data export options, implementation effort, and the consequences of relying on third-party integrations. Test a complete workflow rather than comparing feature lists alone.
When a custom application may fit
Custom software may be useful when the workflow combines business-specific information that is awkward to represent in existing tools. In trading, this might include product grades, quotation terms, shipment details, and linked documents.
The benefit must justify building and maintaining it. Discuss access controls, backups, observability, deployment, and who will support the system after launch.
Compare the total operating cost
For an existing product, include subscriptions, setup, migration, training, and integration maintenance. For custom software, include development, hosting, usage-based services, upgrades, and support.
Compare these costs over a period relevant to your business. Avoid treating a temporary free tier or student credit as a permanent production budget.
Check ownership and portability
Ask what data you can export, in what format, and how attachments are handled. For custom work, agree source-code ownership, account access, documentation, and third-party licences in writing.
A useful handover includes the information needed to operate the solution, not just the files used to build it.
Test the smallest valuable workflow
Select a representative enquiry and its associated customer, supplier, quotation, and document information. Run it through the proposed approach with the team.
If a configured product works well, use it. If an important gap remains, define a focused custom phase around that gap and agree acceptance criteria before development.
Related work: Pharmet International’s website and trading workspace.