Where we usually start
Ops Scan
At the end you know exactly where your operation loses time, money and visibility, you have a cockpit that keeps showing it, and you know what to automate first.
Why
Most operations leak in places nobody measures
At Cadenza, where I'm COO, I built seven operating dashboards in a single long day. What came out was uncomfortable: there were deals in the pipeline that didn't exist, a leak in the billing process was systematically producing credit notes, re-billable receivables were sitting there unchased, and product engagement had dropped sharply after April without anyone noticing.
None of that was a secret. It simply wasn't visible in one place, so nobody steered on it. That's almost always the pattern: the information exists, spread across a CRM, an accounting package, a ticketing system and three spreadsheets, and there is no moment where it comes together.
The Ops Scan is exactly that, run on your company.
Sequence
How it goes
Systems and access
I connect to what you already have: CRM, billing, product analytics, ticketing, project tooling. Read access is enough. No migration, no new system.
Observe and measure
Conversations with the people doing the work, not only those managing it. Where manual effort goes in, where things get retyped, where things wait.
Build the cockpit
A working operating cockpit on your own data. Commercial, onboarding, customer health, cash conversion, delivery. Whatever is relevant to you, not a template.
Findings and priority
What leaks, roughly what it costs, and what an agent or automation could take over. Prioritised on impact against effort, with a concrete proposal for what comes first.
Deliverables
What you keep
A working cockpit
Not a screenshot in a report. A running suite on your own numbers that keeps working after I leave.
A list of leaks
Named specifically, with an estimate of what each one costs per month in time or money.
An automation plan
Which process lends itself to agents, in what order, and why that's the order.
An honest verdict
Including what you should not automate. Some processes need cleaning up before anything else.
Practical
What you probably want to know
How much time does it cost my team?
Little. A handful of conversations with the people doing the work. Beyond that I work independently.
Do I have to switch systems?
No. I connect to what's there. If a system genuinely is the problem I'll say so, but the scan itself requires no migration.
Do I get something I can use without you?
That's the premise. The cockpit and the documentation are yours, even if there is no follow-up.
What does it cost?
A fixed fee, depending on the size of your operation. I'll tell you in the first call, before you have to decide anything.
What if nothing comes out of it?
That's a result too, and it's rare. But if at the end I think there's nothing sensible to automate, I'll say that as well.
Ready to know what your operation actually does?
Thirty minutes to see whether this fits. I'll tell you in that call what it costs and what it realistically returns.