Operations practice
Most AI projects cannot prove they worked.
For established businesses: we take one expensive workflow, establish what it costs you today, implement it inside the systems you already run, and measure the difference at 30 days. If the evidence is not there, we say so — and you stop.
The problem
Established businesses with more process than people to run it.
This engagement fits a company where a repeating, high-volume workflow is quietly losing money — enquiries answered too late, quotes that go cold, information re-typed between systems that should talk to each other.
It fits best when there is an executive who will sponsor the change, a system of record already in place, enough volume that a small improvement is worth real money, and nobody internally who already owns the problem.
It is a poor fit if the volume is low, the baseline cannot be measured, or the request is to automate a consequential decision with no human in the loop. We say that on the first call rather than after an invoice.
Deliverables
What you receive.
- Executive AI value assessment
- A focused conversation at no cost. We identify one candidate workflow, size the opportunity roughly, and give an honest read on whether paid work is justified.
- AI opportunity blueprint
- A fixed-scope paid diagnostic: the workflow mapped end to end, a baseline from your system data, risks reviewed, opportunities ranked, and a conservative business case with success criteria and a 90-day plan.
- 30-day value pilot
- One narrow workflow implemented in your systems, with agreed baseline, success metrics and acceptance criteria, human escalation, monitoring, testing, training, documentation, a fallback — and a value review at the end.
- Managed AI operations
- Ongoing responsibility in production: monitoring, incident handling, integration maintenance, evaluation, optimisation, vendor and model change management, and reporting. A defined service, not access to an advisor.
- AI leadership for several initiatives
- For companies running several initiatives at once: roadmap, prioritisation, vendor governance, portfolio measurement and reporting to leadership — fractional Chief AI Officer capability, described in the terms a board uses.
This practice is separate from the positioning work, with a different buyer and a different method. It shares one rule with it: establish what is true before deciding what to do. About the sprint
Where the money usually leaks
Five patterns with a countable baseline and a clear owner.
Enquiries answered too late
Calls missed after hours or during peak load, and web leads that wait until someone opens the inbox.
Quotes and estimates that go cold
Work priced, sent and never followed up on a consistent cadence — then lost to whoever called back.
Re-typing between systems
Staff moving the same information between phone, CRM, scheduling and accounting.
Records nobody trusts
Reporting built on a CRM that is incomplete because updating it is the last task of a long shift.
No view of the leak
An owner who suspects opportunities are lost between first contact and invoice, with no instrument that shows where.
The boundary
What we build, and what stays human.
We implement: detection of the triggering event; response in the approved channel and language; capture of the information the business needs; creation and update of records in your system of record; routing to the right person; follow-up on an approved cadence that stops when a customer replies or opts out; summaries and flagged exceptions; and an owner-level view of where opportunities are lost and whether the system is healthy.
Stays under human control: custom pricing, unusual discounts, contractual commitments, complaints and legal threats, anything touching safety, and any action that cannot be reversed. When uncertain, the system stops and hands over to a person.
Reliability, privacy and ownership
The parts nobody asks about until something goes wrong.
You own everything
We build in your accounts. Credentials, data, prompts, configurations, integrations and documentation are yours, with a written credential-revocation checklist at offboarding.
Least-privilege access
The narrowest access that does the job, under named accounts with multi-factor authentication and access logging.
Tested before production
Every workflow is evaluated against a fixed set of normal, edge and adversarial cases before it reaches a live customer.
Monitored after deployment
Success rate, exceptions, latency, cost, opt-outs and integration health, watched continuously.
A documented fallback
A written path back to your normal process, a named owner on both sides and an escalation route.
Measured against a baseline
Value compared with a baseline taken before anything was built, using a method agreed in advance.
Governance follows the structure of the NIST AI Risk Management Framework — govern, map, measure, manage — scaled to a company of your size.
Why it matters now
The first workflow is rarely glamorous. That is why it pays.
We do not begin with a tool. We begin with the workflow, the volume and the gross profit attached to it, because that arithmetic decides whether any of this is worth doing.
Where ordinary automation will do the job, we use ordinary automation. A deterministic rule that always works is worth more than a model that usually does — and is cheaper to operate.
Questions
On ai implementation and operations.
Related answers
Questions buyers ask before they ask a firm.
Find the first workflow.
Request an executive assessment. We will identify one workflow worth measuring, and tell you plainly if it does not justify paid work.
If we can help, you leave with one specific observation about your positioning. If we cannot, we say so.
Other engagements