For SME Tech Companies
Which One Sounds Like You?
Four common situations for a small tech company, each met with a fixed scope of work. Find the one that matches where you are.
Pre-Launch Audit
I’m About To Launch And Nobody’s Checked This Yet
The launch date is fixed, and nobody outside your own team has looked at what’s about to go live.
Most pre-launch reviews either rubber-stamp what’s already decided, or hand back a long list with no sense of what actually matters first.
This is scored against a fixed set of checks: authentication, secrets, payments logic, whether it holds up at your expected scale, and the traps that show up later as cost. The categories are already known, so the time goes on answering them, not deciding what to ask.
A fixed scope and a fixed number of working days, agreed before anything starts.
What you get
- A written verdict, split into before launch, within 90 days, and safe to ship as it is.
- Read-only access to your code, nothing more asked for.
- A fixed scope and timeline, agreed up front.
- Your material stays inside your controlled environment throughout.
Technical Blueprint
I’ve Got No CTO And Decisions I Can’t Price
You’re about to spend real money on a build, and nobody in the room can tell you whether the plan holds up.
Advice at this stage usually comes from whoever wants to build it for you, or from generic best practice that ignores what you’re actually trying to do.
The output is a written architecture and build plan, with each major decision costed, so you know what a change would cost before you commit to it, not after.
Fixed price, fixed length, and the document is yours whether or not you build with us afterward.
What you get
- A written architecture and plan, scored against your actual constraints.
- Each major decision costed before you commit.
- A fixed price and length for the work.
- Ownership of the document either way.
Production Stabilisation
Something’s Broken And It Can’t Wait
The system is failing now, and every hour it stays down is a cost you can already count.
If it’s down right now, whatever built it, this is the one. Still running but you don’t trust it? See AI-Built Code Stabilisation below.
Emergency work is usually billed by the hour, which punishes you for the outage taking longer to fix.
Fixed price, scope agreed before work starts, one named engineer throughout rather than a rotating queue relearning the system at each handover.
Stabilise first. Whether anything ongoing is needed is a separate decision, made after, not assumed up front.
What you get
- A stabilised system, priced and scoped before work starts.
- One named engineer, not a ticket queue.
- A written account of what broke and why, once it’s fixed.
- No obligation to continue past the fix.
AI-Built Code Stabilisation
I Built This With AI And I’m Afraid To Touch It Now
It runs, mostly, and nobody, including whoever prompted it into existence, can say with confidence what happens if you change one thing.
Still running today, but you’re afraid to touch it, that’s this one. System actually down right now? See Production Stabilisation above.
The instinct is either to keep bolting more onto it, or to throw it away and start again. Both are usually the wrong call before anyone’s actually looked.
A fixed-fee audit finds where it actually breaks and prices what it would take to put right: tests, boundaries, a single source of truth for how it's meant to behave, before any fix work is agreed.
You then choose whether to fix it yourselves or have us do it. Either way, nothing is locked to us.
What you get
- A fixed-fee audit that finds and prices what’s fragile.
- The choice to fix it yourselves or have us do it.
- No lock-in: your accounts and repos stay in your name.
- A plain account of what's safe to leave alone.
Contact
Get In Touch
Tell us which of these sounds like you, and we'll get back to you.