Every business has a process that lives in an inbox. A new client fills in a PDF, emails it back, someone copies the details into a spreadsheet, someone else chases the missing fields, and three days later the job finally starts. Nobody owns it. Everybody complains about it.
That gap — between a customer telling you something and your business actually doing something about it — is where money quietly leaks out. Let's put a number on it, then close it.
What the inbox actually costs you
Take a fairly ordinary intake process: a quote request, an onboarding form, a service booking. Say it lands 40 times a week.
Each one needs roughly 12 minutes of human handling — opening the email, re-keying details, checking for missing info, replying to chase, updating a sheet. That's 8 hours a week. Call it £20/hour fully loaded, and you're spending over £8,000 a year moving information from one box to another.
That's the visible cost. The invisible ones are worse:
- Drop-off. Every manual back-and-forth loses people. A request that takes three days to acknowledge is a request your competitor already answered.
- Errors. Re-keyed data is wrong data. A transposed postcode or a missed VAT number costs an hour to unpick later.
- No memory. When the person who "handles those" is on holiday, the process stops dead.
None of this shows up on a P&L line called "inbox inefficiency." It just shows up as slower, more stressed, slightly poorer.
What good looks like
The fix isn't a fancier form. It's a form that does something the moment it's submitted.
Here's the shape of a system we build under forms and workflow automation:
1. Capture once, clean automatically
The form validates as it goes — postcodes, company numbers, email formats. No "please resend, you forgot section 3." If a field is missing or contradictory, the submitter knows before they hit send, not three days later.
2. Route by rules, not by who's online
A £500 job and a £50,000 job shouldn't follow the same path. The system reads the submission and routes it: small jobs auto-approved, large ones flagged for a human, urgent ones pushed to whoever's on shift. The logic lives in the system, not in someone's head.
3. Trigger the next step
This is where it stops being a form and starts being a workflow. Submission creates the record, drafts the acknowledgement, schedules the follow-up, and notifies the right person — all before anyone's had their second coffee.
4. Let AI handle the messy middle
Free-text fields are where automation usually falls over. "Tell us about your project" produces a paragraph no rule can parse. This is where a model earns its keep: reading the free text, extracting the structured bits (budget, timeline, scope), summarising it for the team, and flagging anything that needs a human eye.
Because we're model-agnostic, we pick the right engine for the job rather than forcing everything through one. Light classification might run on a cheap, fast model; nuanced summarisation on a stronger one. That's the same pooled-intelligence approach we use across our builds — the best tool for each task, not one model doing everything badly.
A worked example
A distributor we worked with took supplier price updates by email — PDFs, spreadsheets, the odd photo of a printout. Someone spent the best part of two days a week reconciling them by hand.
We built an intake that accepts any format, extracts the line items, matches them against existing SKUs, flags the changes that move margin, and pushes the clean data straight through. The two-day job became a 20-minute review. The errors that used to surface as undercharged invoices simply stopped.
That's the pattern: the human stops being a data-entry clerk and becomes a decision-maker. The system does the typing; the person does the thinking.
Where it connects to everything else
Forms automation rarely lives alone. Clean, structured intake is the front door to the rest of your operation — feeding into a small-business ERP so quotes, jobs and invoices share one source of truth, or into a pricing engine that turns a request into a costed quote without a spreadsheet in sight.
The point is that none of these are big-bang projects. You start with the one process that everyone in the business already moans about, automate that, and let the wins fund the next one.
How to spot your own leak
Ask three questions about any process:
- Does information get re-typed? If a human copies data from one place to another, that's a candidate.
- Does it wait in an inbox? Anything that sits unread until someone notices is losing you time and customers.
- Does it break when one person is away? If the answer's yes, the process lives in a person, not a system — and that's a risk, not just an inefficiency.
If you've got one process ticking all three boxes, you've found your first project. It'll pay for itself faster than you'd expect.
Want us to look at the process draining your week? Book a call or get in touch — we'll map it, cost it, and tell you honestly whether it's worth automating.