Business improvement
Before you automate, decide how the work should run
Why roles, handoffs, exceptions and service costs matter as much as the automation itself, from dealerships to service businesses.
A working automation is one part of a working service. Someone must supply the information, approve the output, deal with exceptions and respond when the customer needs a person.
That is an operating model question: how do people, processes, information and tools fit together to deliver the service? It is also a practical starting point for improvement in a small business.
Our recent service-development work has brought marketing production, enquiry handling, reporting and commercial planning into the same conversation. These are lessons from designing and developing workflows; the cross-sector examples below are illustrative, rather than claims about unnamed client deployments.
Name the handoff
“The system sends a notification” sounds complete until nobody knows who should act on it. A useful workflow names the next owner, the information they receive and what they are expected to do.
For a dealership, that might mean an enquiry enters a Lead Desk with a vehicle reference and a requested next step. For a professional service, it might mean a qualified request reaches the appropriate adviser. For a trade business, it could be a quote request that needs a site visit before anyone can price the work.
The systems differ, but the design question is the same: who owns the next action?
Design the exception as well as the routine
Most neat workflow diagrams describe the easy case. Real work includes missing information, changed prices, unavailable stock, duplicate enquiries and customers who ask an unexpected question.
A useful design sets out when the automation stops and what the team sees. A flagged item with an explanation is often more valuable than a confident response based on incomplete information.
Make the service deliverable
Business-model development adds another test: can the work be delivered consistently at the agreed scope and cost?
For a managed marketing service, the unit of work might be a vehicle, an image or a content batch. The delivery plan needs to account for source quality, revisions, approvals, support and reporting. The same applies to a service business processing quotes or recurring customer requests.
We use operating-model planning to make those assumptions visible before treating a pilot as a repeatable offer. Volumes, responsibilities, service fees, advertising budgets and third-party costs need their own definitions.
Start with a small, measurable change
A useful pilot has a clear boundary:
- Choose one process and record how it works today.
- Agree the information, owner and expected outcome at each step.
- Build and test the routine path and the common exceptions.
- Train the people who will use and support it.
- Review the result against the starting point before expanding.
Possible measures include administration time, response time, rework and the number of items awaiting action. The right measure depends on the problem. A forecast is an assumption to test, rather than a result to publish.
Improvement is a way of working
Experience in complex transformation brings a useful habit: consider the whole operation, then make the change small enough to introduce and assess properly.
For growing businesses, that can mean a simpler process, clearer responsibilities or a connection between existing tools. Automation earns its place when it supports that better way of working. Explore operating model and process improvement or tell us where work gets stuck.