Why your next competitive advantage may sit between your systems.

The invisible work

Moving an enquiry from an inbox to a CRM involves more than transferring data. Someone interprets it, finds context and decides who should act. When this coordination is not represented in the workflow, it remains dependent on individuals. The company may have digital tools without a coherent operating process.

Not every problem is an AI problem

A clear status change can be handled with a fixed rule. An incomplete message may require interpretation and clarification. Our recommendation is to capture these differences explicitly. Architecture should follow the work, not a desire to use as many models as possible.

The smallest useful unit

We start with a bounded task. Its input should be identifiable, its completion verifiable and its ownership clear. This prevents a pilot from quietly becoming a complete organisational rebuild. It also makes comparison possible: what remains with people, where does rework fall and what new oversight is needed?

A useful first test

Choose a recurring workflow that currently requires manual handoffs. Document real examples, including difficult ones. Let the system prepare rather than decide at first. Then assess the whole task, not just the quality of a single answer.

Example: from an incoming enquiry to a quotation draft

Suppose a technical distributor receives enquiries by email. A colleague finds product information, checks delivery conditions and copies details into the CRM. A useful first scope would not be “automate sales”. It would be to match an enquiry to a customer, flag missing details and prepare a sourced quotation draft. Prices, availability and sending remain with the responsible person until an explicit approval boundary is agreed. This is an illustrative approach, not a client case study.

What should acceptance cover?

• A complete enquiry produces one correctly assigned draft, including when the same message arrives again.
• Missing quantities or conflicting product codes trigger a clarification, not an invented answer.
• A system outage leaves the enquiry visible and available for manual handling.
• Access and approvals can be traced to an accountable owner.

Then compare handling time, clarification requests and corrections with the previous workflow. A quickly written answer alone does not establish a saving. Any additional review work belongs in the comparison too.

Use seven questions to narrow down a first area of work