Choose the smallest change that solves the work.
A new system is one option. First decide whether a clearer process, existing software or a small integration will solve the problem.
On this page
When work is spread across email, spreadsheets and several applications, another tool can help or add another handover. Start by writing down one task: what arrives, who handles it, which information changes and what a correct finished result looks like.
Compare the routes against the same task
| Route | A useful fit when | Questions to settle |
|---|---|---|
| Improve the current process | The main problem is unclear responsibility, inconsistent information or duplicate checking. | Can one agreed template, owner or handover remove the problem? |
| Configure existing software | A standard CRM, booking, accounting or job-management product handles the core work. | Does the subscription include the permissions, exports, integrations and support you need? |
| Connect the tools you have | Each application works reasonably well, but people repeatedly copy information between them. | Is supported integration access available? Who handles duplicates, failed transfers and changed data? |
| Build a custom system | An important workflow, permission model or customer journey cannot be handled well by suitable existing products. | Who owns the code and accounts? What needs maintaining? How will users and data move across? |
Compare actual workflows and whole-life effort, not just a subscription price with a build quotation. Include setup, data cleaning, training, third-party charges, maintenance, access changes and eventual export or migration. Custom development needs support; standard software may still need configuration and workarounds.
Where AI earns its place
AI may help draft a reply, extract information from varied documents or organise an incoming request. It still needs clear inputs, agreed checks and someone responsible for uncertain output. A fixed rule or supported integration may be enough for a predictable task.
For example, an illustrative pilot could turn a completed enquiry form into a draft job record for staff approval. The pilot could check required fields, flag a possible duplicate and leave an uncertain request in a review queue. It would not automatically commit the business to a price or send a customer promise.
Write a first-pilot scope before building
Agree these points in plain language:
- One workflow: its start, finish, systems and responsible person.
- Inputs: a small representative set of permitted examples, including missing information and exceptions.
- Output: what staff receive and how they confirm that it is correct.
- Access: the minimum accounts, permissions and data needed; any third-party approval or licence.
- Checks: duplicate handling, failed connections, uncertain AI output, logs and a manual fallback.
- Acceptance: agreed examples the pilot must handle and the conditions for deciding to continue, revise or stop.
- Handover: documentation, account ownership, training and support responsibilities.
State exclusions too. A pilot for one workflow does not automatically include every department, historical data migration, additional integrations or unattended production operation. Agree changes to scope and cost before adding them.
Measure time without turning it into a staffing promise
Record the current frequency, time spent and correction effort. During the pilot, include checking, exceptions and ongoing running costs. Time released can improve capacity or service; it does not automatically equal a reduction in employment costs. Our first-automation guide includes a clearly hypothetical calculation, and the automation calculator lets you explore your own assumptions.
See how this connects to real work
The Jagelo and Logivo case study follows planning, driver information, proof of delivery and invoicing in a real transport operation. Its operational improvements are owner-reported; it is not a priced template or a promise of the same outcome elsewhere.
If you need help choosing, start with AI consultancy. For a known handover, explore automation; for a broader workflow, see custom business systems. Request a quotation or compare our starting routes.