Try a ready-made system against real tasks first. Configure it when supported changes solve the gap. Consider custom development when important workflows genuinely need different rules and you can own the operating responsibilities.
01 / Define the work the system must support
Follow a real record from creation to outcome. Who enters information, what must be checked, who approves it and which systems need an update? A sales pipeline, a marketing campaign workspace and an appointment-based service business may all be described as CRM, while needing very different objects and states.
Write acceptance scenarios with the people who perform the tasks. Include corrections, duplicate records, failed integrations and access restrictions. Ask prospective tools or development partners to demonstrate those scenarios instead of giving a general product tour.
02 / Compare three workable routes
A ready-made CRM can provide an established product with an existing release and support operation. Configuration uses its supported fields, workflows and integrations to fit the business. Custom software gives you more control over the application experience, while moving more delivery and operational responsibility to your organisation and its suppliers.
These routes are not mutually exclusive. A custom interface might connect to an established CRM as the system of record. Before choosing this hybrid, verify API coverage, limits, licensing and how permissions remain consistent across both experiences.
| Route | Good fit | Check carefully |
|---|---|---|
| Ready-made | Your core workflow fits supported capabilities. | Seat costs, permissions, export and essential integrations. |
| Configured | Supported customisation closes specific gaps. | Upgrade compatibility and ownership of configurations. |
| Custom or hybrid | Critical workflows need a distinct experience or business logic. | Delivery scope, data ownership, maintenance and operational support. |
Evaluate the workflow you need to run, not the longest feature list in the demonstration.
03 / Compare total cost over a useful period
Choose a common planning horizon and include implementation, migration, licences, integration work, training, support and expected changes. Separate one-off costs from recurring ones. For subscriptions, check the actual plan and seat assumptions; for a custom build, include infrastructure and the people responsible for maintaining it.
Run a base case and a higher-usage case rather than presenting one precise lifetime total. Record what happens if the team doubles, an API becomes more expensive or a workflow changes. Treat an assumed time saving as a hypothesis until it has been tested in live work.
04 / Decide who owns each piece of information
Define the source of truth for contacts, campaign status, appointments and reporting. If several systems can edit the same record, decide how conflicts are resolved. Check identifiers, synchronisation timing, duplicate prevention, retries and a visible way to investigate failed actions.
Data migration is a project activity, not a final export button. Review quality and retention needs, map fields, test imports and reconcile a sample of records. Agree how users will work during the transition and which historical data needs to remain accessible.
One source of truth for contacts
- Contact IDUse a stable ID to match shared records.
- Shared fieldsMap the fields used by marketing and support.
- DuplicatesHold records that may describe the same contact.
- Conflicting editsLet an owner resolve conflicting values.
05 / Use interface examples to ask better questions
Our Orbita CRM case presents campaign creation, previews and analytics in a connected workspace. Matrix CRM presents a mobile operational environment for a service business. They illustrate why different teams may need different interface structures, even when both projects sit under the CRM label.
Use those examples to identify a journey worth improving in your own organisation. Do not assume that a similar screenshot means the same backend, permissions, commercial terms or integration scope. The right proposal should explain those details for your specific system.
06 / Validate the choice with a limited pilot
Select one workflow, a representative group and a clear owner. Establish a baseline for task time, corrections and handoffs, then observe the same work during the pilot. Include the training required and the work people still perform outside the system. A successful demo is only the start of evaluation.
Before expanding, confirm support, access to exports, documentation and the plan for future changes. Custom development is sensible when its additional control solves a meaningful problem and its responsibilities are affordable. A standard product is sensible when it meets the job with less unnecessary work.
What to take away
Choose the CRM route by workflow fit, total operating cost and ownership. Demonstrate the important tasks, test the migration assumptions and validate the decision with a limited pilot.
Describe the workflow before choosing the platform.
Use the brief builder to record your team, existing systems and the task you want to improve.
Create a brief