A custom CRM brief should describe how a lead becomes a customer and how staff handle ownership, follow-ups, exceptions and renewals. Feature names such as pipeline, automation and dashboard are not enough to compare quotes. Define the decisions the system must support, the information required at each stage and the work that should remain in existing applications.
Let’s plan your custom CRM.
Bring your workflow and the decisions you need to make. We’ll help you define the requirements, examine the trade-offs and plan a practical next step.
Begin with one lead-to-renewal journey
Choose a representative customer journey rather than combining every sales team's process into the first workshop. Identify how the enquiry arrives, who accepts it, what qualifies it, when a quotation becomes an order and who manages the account after sale.
Write a rule for leaving each stage. “Qualified” might require an agreed customer need and a scheduled next action; it should not simply mean that someone clicked a label. Decide which fields are mandatory because a decision needs them, and which can be collected later.
| Stage | Decision | Required evidence | Exception to demonstrate |
|---|---|---|---|
| Capture | Is this a new enquiry? | Source and contact identifier | Duplicate across two channels |
| Assign | Who owns the next action? | Team, territory or product rule | Owner unavailable |
| Qualify | Is further sales work justified? | Agreed qualification fields | Incomplete or conflicting details |
| Quote | What has been offered? | Version, validity and approval | Revised price after approval |
| Close | What commitment exists? | Accepted order or loss reason | Reopened opportunity |
| Renew | Who contacts the customer next? | Contract reference and due date | Renewal owner has left |
The table is an illustrative requirements worksheet, not a recommended sales policy for every organisation.
Separate configuration from custom development
Ask whether an existing CRM can support the workflow through supported configuration and integration. A distinctive field name alone is not a strong reason to commission software. A genuinely unusual approval process, offline field workflow or cross-system transaction may justify deeper work.
For each requirement, record whether it is available, configurable, requires an extension, or is unsupported in the proposed approach. Include ongoing ownership of extensions. An inexpensive initial modification can create a recurring upgrade dependency.
Make the salesperson's daily work explicit
Specify the daily queue: whom to contact, why the contact is due and what happens after the interaction. Measure the effort needed to capture the result using a representative device and realistic connectivity.
A field-sales team may need to record visits while disconnected. Decide how conflicting edits are resolved when the device reconnects. A desk-based team may instead depend on phone and email integration. Price the actual working environment rather than assuming one interface suits both.
Define permissions and data ownership
Who can export all contacts, reassign an opportunity, view another team's notes or change the expected deal value? Test those boundaries using accounts with different responsibilities.
Specify how duplicates are merged without losing communications or ownership history. Decide which application owns the customer after an order reaches ERP. A sales stage must not masquerade as a confirmed financial transaction.
Questions before requesting proposals
Should we automate lead scoring immediately?
Only when there is an agreed decision and usable evidence behind the scoring. Start with explainable qualification rules and review whether staff can use them consistently. A score without an action can become another unused field.
What should a CRM development quote include?
The scoped workflow, integrations, migration, permissions, acceptance checks, training and support. Compare these boundaries alongside the price and delivery assumptions.
Prepare a comparable brief
Bring a sample lead, a quotation revision, a duplicate record and a renewal exception. Use the existing CRM feature checklist for breadth; this guide supplies the workflow specification behind the feature list. Discuss enterprise software development after the record ownership and first-release boundary are clear.
