An enquiry arrives through the website. One colleague replies, another prepares the proposal, and a manager wants to know what happens next. When that information sits in separate inboxes, spreadsheets and chats, a custom CRM may help. Before commissioning one, ask a more precise question: which rules of your process cannot be handled well with the tools you already have?
A dedicated CRM is more than a tidier database. It should make the relationship status, owner and next action clear. Custom development becomes worth considering when genuinely specific needs cannot be covered sustainably by configuring an existing product.
The short answer: test the workflow before choosing technology
Take ten recent enquiries, remove personal details and trace their path: receipt, qualification, assignment, proposal, reply and closure. Mark where information goes missing or tasks are duplicated. Testing actual cases lets you compare a ready-made product, automation between tools and a dedicated system. E-ROE’s guide to custom versus off-the-shelf business software helps structure that comparison.
If the only problem is moving data between two otherwise suitable systems, consider integrating the CRM and business software first. A custom CRM focuses on the internal way of working: records, rules, roles and screens people use each day.
What information should it bring together?
A first map can distinguish four elements. These are planning prompts, not mandatory modules.
| Element | Working question | Mistake to avoid |
|---|---|---|
| Contact and company | Who is the person, and which organisation do they represent? | Creating a duplicate for every new enquiry |
| Opportunity | Which need, indicative value and decision are being followed? | Treating an enquiry as a won contract |
| Task | Who must do what, and when? | Relying on one person’s memory |
| History | What happened, and with what result? | Keeping notes without context or appropriate access |
For each field, decide who creates it, who may correct it and how long it is useful. A long form does not improve sales work if nobody can find the next action. Start with necessary information and add detail when an actual case justifies it.
Design stages together with exceptions
“New”, “in progress” and “closed” sound simple, but do not explain what happens when an enquiry is incomplete, a prospect replies weeks later or a proposal changes. For each stage, document who may move a record into it, what action triggers the move and what follows.
For example, an unqualified enquiry may wait for more information; a sent proposal may create an assigned follow-up; a lost opportunity should retain a useful reason without forcing the team to invent categories. Test these exceptions before automating them.
Roles, permissions and connections
A salesperson, manager and system administrator may need different views and permissions. Define who can read data, reassign an opportunity and export records. Hiding a menu item or sharing an obscure link is not access control.
If the CRM receives website enquiries, decide what is saved after a successful submission and how repeated messages are handled. If it exchanges data with invoicing, calendars or ecommerce, agree which system owns each field. Keep preferences for promotional messages separate from responding to an enquiry; review privacy information and choices for the specific business.
A useful first release can be tested
The first release may cover one complete journey: new enquiry, assignment, next task, proposal and closure. With test users and records, check that:
- a repeated enquiry does not create two indistinguishable records;
- an absent colleague can be covered without losing the history;
- users cannot see information outside their role;
- an integration failure is visible and recoverable;
- the team can complete the work without maintaining a parallel spreadsheet.
The people who do this work should take part in testing. If the process only succeeds in a guided demonstration, it is not ready for daily use.
Prepare a brief before requesting a quote
Bring one anonymised enquiry, a list of current tools, the roles involved, three common exceptions and the result you want from the first release. Identify what must be imported, what can remain in existing systems and who will maintain the records.
E-ROE lists an internal CRM among the possible applications of its custom business software service. A review begins with the real workflow and may conclude that an existing tool should be configured, connected more effectively or supplemented with dedicated software. Tell us where your process breaks down to define a useful first step.
