Six surfaces · 2–6 business days · fixed scope
Know what to build next before you spend more.
A senior engineer spends 2–6 business days inside your business: how the work actually runs, the systems behind it, the data, the tools. You leave with a written report on what's costing you, what to change, and what we'd build first. Software, automation or AI — whichever earns its place.
What we look at
Six surfaces. Focused or full. Real depth on each.
Focused Diagnostic — One workflow, product problem, automation opportunity or system. For smaller businesses and targeted decisions.Technical Audit — The broader architecture, workflows, data, tooling and delivery environment. Same method, wider frame.
- 01
Your systems & architecture
The systems the business runs on — cloud, services, data flows, infra. Where the bottlenecks, single points of failure and undocumented complexity actually live.
- 02
Your data, and whether it's usable
What data you have, where it lives, how clean it is, and whether it's in a state where anything — a report, an automation, a model — can actually use it.
- 03
Your workflows & manual work
What your people do every day. Where humans are doing repetitive, rule-bound work that should be automated, and where they shouldn't be.
- 04
Your tooling & vendor stack
What you're paying for, what's overlapping, what's underused, and what's blocking faster delivery.
- 05
Your team & how work gets done
How decisions get made, where work gets stuck, and what's slowing delivery down — whether that's an internal team, a supplier, or you.
- 06
Where AI would earn its place
Concrete, named opportunities, not generic 'AI could help here.' Which surface, which model, what changes. Plus the parts where AI is the wrong answer and you should ship a rebuild or an automation instead.
60-second self-audit
Five questions. A first read on where the work gets stuck.
The deliverable
What's in the report.
A written document, as long as it needs to be — a concise decision brief for a focused diagnostic, a deeper report for a full audit. Never a slide deck.Delivered as a PDF and walked through live in a 60–90 minute session — written to be understood by whoever has to decide, and precise enough for whoever has to build.
- How the work actually runs today, written down in one place
- What's costing you time or money, ranked by business impact
- What should change — and what already works and should be left alone
- Build, buy or automate, decided per problem, with the reasoning shown
- Where AI earns its place inside the business, and where it doesn't
- The recommended solution: sequence, rough effort, risks, and the next step
How the audit runs
Fixed scope. Two to six days.
Kick-off & walkthrough
Half a day, on-site or on a call. We meet the people who do the work and get access to whatever the business already runs on.
Systems, tools & data
We work through the software, the data and the tooling behind the process, with whoever knows them best — technical or not.
Watching the work
We sit with operations, support, sales, or wherever the manual work lives. We watch what people actually do.
Synthesis & writing
We pull everything together into a written report: what to change, what to leave alone, what we'd build first.
Read-out & decision
60–90 minute session. We walk through the findings, answer everything, and agree the next step, including not yet.
What happens after
Three doors. You pick.
Door 01
Build it with us
If the audit reveals work you want to ship, we'll quote a fixed scope and timeline, and the diagnostic fee is credited against that build. Continuation is earned phase by phase, never assumed.
Door 02
Build it with someone else
The plan is yours to keep. Hand it to your own people, a freelancer or another supplier. We're happy either way.
Door 03
Sit on it
Some companies aren't ready to act immediately. The report doesn't expire. Come back when you are.
Honest answers.
Because the deliverable is real engineering work. A senior engineer spends 2–6 business days inside the business and writes up what's happening, what it's costing you, and what to do about it — ranked, sequenced and costed. Fixed scope, no discovery theatre, and no obligation to continue with us afterwards.
Someone who knows how the work actually gets done, access to the tools you already use, and a couple of hours of their time. If you have repos, dashboards or a ticketing system, read access helps, but no internal engineering team is required. An NDA if you want one, we'll sign yours or use ours.
A founder. The technical side is led by our CPTO, whose prior senior delivery was at Revolut, J.P. Morgan, Deloitte and Accenture. Not a junior consultant, not an account manager. The person writing the report is the person who'd build the work.
Most clients don't, and that's the point. The audit exists to name the problem properly: what is quietly costing you, what is worth fixing first, and whether the answer is a piece of software, an automation, AI, or leaving something well alone. You bring the problem, not the solution.
A discovery call is 30 minutes of questions to qualify you. The audit is 2–6 business days of work inside your business, ending in a written deliverable you keep. The output is the same whether you hire us afterwards or not.
It happens, rarely, but it happens. If we genuinely think the work isn't there right now, we'll tell you, give you the reasoning in writing, and not waste anyone's time.
That's normal, and it isn't a problem. What you need to know is your own business: where the time goes, what breaks, what it costs. Working out the architecture is our job. The report is written to be read by whoever has to decide, not only by an engineer.
When it fits
It's the right first step when any of this sounds familiar.
- Something manual or slow is costing real time or money
- You need a decision: build, buy, automate, or leave it
- You'd rather find out in days than guess for months
Discuss a diagnostic
Start with the problem. No obligation to continue.
Tell us what's slowing the business down. If a diagnostic is the right shape, we'll scope it. If it isn't, we'll say so and tell you what we'd do instead.