A CRM is often blamed for problems it was never designed to solve. A sales pipeline can be clean while jobs are still passed around in WhatsApp, onboarding lives in somebody's inbox, delivery status sits in a spreadsheet, and leadership gets updates by asking people what is going on.
That is not necessarily a failed CRM project. It is an operating-system gap.
For a growing field-service, compliance-heavy, consultancy, agency or expert-service business, the useful question is not “Which CRM should we replace ours with?” Ask this instead: can the current system reliably move a real piece of work from enquiry to completed delivery without manual chasing?
First, separate the CRM job from the operating-system job
A CRM is usually strongest when it owns commercial activity: leads, contacts, opportunities, follow-up, meetings, proposals and sales reporting. Keep it there if it is doing that work well.
The operating system sits across the handovers. It connects the commercial promise to the delivery plan, the delivery plan to the people doing the work, and the work itself to reporting, communication and decisions. It does not have to mean forcing every process into one app.
A useful distinction
- CRM question
- Who are we selling to, what is the next commercial action, and what is the value and status of the opportunity?
- Operating-system question
- What must happen next, who owns it, what information is needed, what system should be updated, and how will a leader know the work is moving?
The trigger, object, action and API worksheet
Do not begin with software features. Begin with the moments where work changes state. Take one live workflow, such as a new enquiry becoming an active client, a booked survey becoming a job, or a signed proposal becoming an onboarding project. Complete the worksheet below with the people who actually do the work.
| Worksheet field | What to write down | Example prompt |
|---|---|---|
| Trigger | The event that should start, stop or change a workflow. | A proposal is accepted. A job date changes. A compliance document expires. |
| Object | The record that needs to move or be updated. | Lead, client, site, project, job, quote, engineer, task, invoice or renewal. |
| Action | The work that should happen next, and whether it can be automated. | Create a delivery record, assign an owner, send a client update, request approval, schedule follow-up. |
| Owner | The named role accountable for the next move. Not “the team.” | Sales owner, operations coordinator, project lead, account manager, engineer or director. |
| Required data | The information needed to do the work without asking around. | Scope, site address, service level, contact details, due date, safety documents, signed proposal. |
| System of record | The one place where the current truth should live. | CRM for opportunity status. Job system for delivery status. Finance system for invoice status. |
| API or connection need | What needs to pass between systems, and how quickly it must happen. | Create a client on deal won. Push booked work to a job board. Bring delivery milestones into a leadership dashboard. |
| Exception | What happens when the normal route breaks. | Scope changes, a client goes quiet, work cannot be scheduled, approval is overdue, a job fails quality review. |
The worksheet usually exposes the real issue quickly. If the team cannot name the trigger, owner and system of record, no dashboard will fix it. If they can name them but the data has to be copied between tools, the gap is likely connection and workflow design. If the CRM has no sensible place for the delivery object, do not bend the sales pipeline until it becomes unusable.
Map the handovers, not just the stages
Revenue leaks and delivery delays often sit in the gap between departments or roles. Sales says the deal is won. Operations discovers the information is incomplete. The client expects a start date. Nobody is technically wrong, but the handover was never designed.
Use this template for each major handover. One row is enough to reveal whether the next person can act without sending a message or opening five tabs.
Handover-map template
1. Handover name
Example: Signed proposal to active client onboarding.
2. Sending role and receiving role
Who has completed their part, and who takes responsibility next?
3. Trigger and deadline
What proves the handover is ready, and how soon should the next action happen?
4. Required information
What must be present before work can begin? Be specific about documents, scope, dates and contacts.
5. System update
Which record changes state, where is it updated, and what gets created next?
6. Confirmation and exception
How does the sender know it was accepted? What happens if critical information is missing?
Choose the right level of change
Not every business needs a bespoke connected system. Sometimes the practical answer is to tidy the CRM and make people use it properly. Sometimes the CRM should stay exactly where it is while an operational layer is built around it.
Choose CRM-only when sales is the real constraint
Your team has a clear sales process, delivery is simple or already controlled elsewhere, and the main problem is inconsistent follow-up, unclear opportunity stages, poor lead capture or weak commercial reporting. There is little value in rebuilding the delivery side just because it exists.
Choose CRM plus operations when handovers are the problem
The CRM works for leads and deals, but client or job delivery starts with manual copying, internal messages and missing context. You need connected workflows between the commercial record and the delivery record, clear ownership, automated prompts and live visibility across both sides of the business.
Choose a bespoke connected system when the business has outgrown point fixes
You manage multiple workflows, teams, job types, sites, client stages or compliance requirements. The same information is re-entered in several places. Reporting is a monthly detective exercise. Important work is remembered by people rather than surfaced by the system. In that situation, another isolated tool usually adds one more place to check.
Five signs your CRM is carrying work it should not carry
- 01Your sales team marks a deal won, then someone has to manually notify delivery and create the work again.
- 02Client, job or project status is only reliable after somebody asks the team for an update.
- 03The same client details, scope or dates appear in the CRM, a spreadsheet, inboxes and a separate delivery tool.
- 04Approvals wait because there is no visible owner, due point or escalation route.
- 05Leadership can see a pipeline, but cannot confidently see capacity, delivery risk, overdue actions or what is blocking revenue from becoming completed work.
What “connected” should mean in practice
Connected does not mean every tool must be replaced. It means each key record has a clear home, the right data moves when a real-world event happens, and people have a reliable place to see what needs attention.
For a field-service or compliance-heavy team, that could mean connecting enquiries, site information, job scheduling, operational status, documents, team actions and reporting. For an agency, consultancy or PR firm, it could mean linking lead capture, proposals, client onboarding, delivery milestones, communication and account visibility.
The design should follow the work. Practical AI belongs here too, but only where it supports a defined process: turning information into a usable summary, prompting a next action, preparing a draft, or helping the team find what they need. An AI tool with no owner, trigger or data source is just another tab.