Operations Diagnostic
Find where the operation leaks time and money — and leave with one fix already running.
- Price
- from €3,500, fixed
- Duration
- 2 weeks
- Commitment
- One-off, no obligation to continue
The problem it solves
You know the operation is leaking. Orders sit in a queue nobody watches, crews are dispatched on a spreadsheet, the monthly report is rebuilt by hand, and nobody can say which subcontractor is costing you money until the quarter closes. You don't know whether the fix is process, a system you already pay for, or something that has to be built — and guessing wrong is expensive enough that nothing happens.
What you get
-
A ranked opportunity list
Every leak found — process, system, data or handover — ranked by annual cost against effort to fix, with an estimate and a recommendation on each. Six pages, not forty.
-
A working prototype of the top item
Built and running on your data, with a recorded walkthrough. A real tool, not a mockup — usually the tracker, dashboard or exception view your team has been asking IT for.
-
A decision memo
What to fix, what to leave alone, and what to do instead about the things we recommend not building. Including the ones where the answer is a process change, not software.
-
A 90-minute readout
Delivered to whoever needs to hear it — ops director, CTO, CFO — with the evidence attached.
Timeline
-
Days 1–3
Interviews
Six to eight people, 45 minutes each — dispatchers, provisioning, field supervisors, the person who builds the monthly report. The people doing the work, not only the ones who own it.
-
Days 4–5
Systems and data review
What the OSS, the ticketing platform, the ERP and the field app each hold, where they disagree, and which numbers people actually trust.
-
Days 6–7
Process and handover mapping
Where work stalls between teams. The handovers are almost always where the time goes.
-
Days 8–9
Build the prototype
The top-ranked item, on your real data.
-
Day 10
Readout and handover
Roadmap, memo, prototype and repository.
What moves the price
- How many systems are in scope, and whether they expose APIs or only exports
- Number of sites, regions or subcontractors involved
- Whether field operations are in scope as well as back office
- How many stakeholders have to agree on what "fixed" means
What we need from you
- Read access to the relevant systems, or exports from them
- 45 minutes each from six to eight people who do the work
- One decision-maker who can say yes
- Someone to answer questions within a day while it runs
A good fit if
- You know the operation is leaking but can't name where
- Ops, IT and finance each have a different explanation
- You've been quoted six figures by an integrator and want a second read first
- You want to test how we work before committing to a build
Not a fit if
- You already know exactly what needs building — go straight to a sprint, don't pay for this
- You need a formal audit for a regulator or an investor — that's a different profession
- Nobody internally has time to talk to us for two weeks
- You want the roadmap but have no budget to act on it this year
Why this one ends with something running
Most paid assessments end with a document, and you have to take the next step on faith — usually towards a six-figure integrator quote for the thing the document recommended.
This one ends with a tool that works. The highest-value item on the list, built on your data, in your hands by day ten.
That is deliberate. It proves the approach instead of asserting it, you keep something useful even if we never speak again, and the decision about a larger build gets made from evidence rather than from a proposal.
What we look for
Twenty-five years of running network and customer operations means we arrive knowing where the leaks usually are, and we are rarely wrong about which stone to turn over first:
- Orders and jobs that stall between two teams because neither owns the handover
- The report somebody rebuilds by hand every month, that three people then disagree with
- Subcontractor and crew performance that only becomes visible after it has cost you
- The field app and the back-office system that were never properly joined
- Rework caused by bad data at intake rather than bad work in the field
- Regulatory and SLA reporting held together by one person and a spreadsheet
Common questions
Can you handle the regulatory and compliance side, not just the software?
Yes, and it is usually the part that decides whether something is workable. Reporting obligations, licensing and permitting, and what a regulator will actually accept as evidence shape the data model long before anyone writes code. We would rather raise those constraints in week one than discover them at go-live.
Is what you build a prototype, or is it production software?
Production. A build sprint ends with a system deployed at a URL, running on real data, with the repository handed to you. The diagnostic includes a genuine working prototype rather than a mockup, but it is scoped as a proof — the sprint is what hardens it.
You use AI to build. Does that mean the work is generated?
No. AI compresses implementation — scaffolding, boilerplate, integration glue, iteration speed. It does not decide which problem is worth solving, sit in the room with your team, or own the outcome. Those are the job. The speed is why this is affordable; the judgement is what you're buying.
Will you work with our IT and security review?
Yes, and it is better to involve them in week one than week three. Tell us at scoping that a review is required and we will plan for it — it affects the architecture and the timeline, and pretending otherwise is how fixed-price projects go wrong.
How do you price?
Fixed price for a defined scope, never an hourly rate. You agree the number before work starts and carry no overrun risk. Ranges are published on each service page along with what moves them, so you can estimate before we speak.
We're small. Are we too small for this?
Probably not — small companies are the ones with no analyst and no spare engineering capacity, which is the whole reason this exists. If a diagnostic is more than the problem is worth, we will tell you on the call and suggest something cheaper, including doing nothing.
We reply within one business day.