Consulting case studies — coming soon
Most of our consulting work sits behind an NDA — founders rarely want "we needed outside help" advertised. We'll publish anonymised write-ups with client permission as engagements close.
Advisory engagements
Technology Consulting
A senior voice on call. Architecture reviews, tech stack decisions, hire vs. buy calls — the questions that wake founders up at 3am. Not a slide deck, not a quarterly "strategy" — direct senior input when you need it.
Engagement
Technology Consulting
- Investment
- From £5k
- Timeline
- 1–6 weeks (or ongoing retainer)
- Pricing model
- Retainer or fixed-scope
- Next availability
- Next slot: 1–2 weeks
What you get
Senior input, not slideware
Four ways we show up on every consulting engagement.
Architecture assessment
We dig into your stack, data model, and deployment — then tell you honestly where the risk lives and what to fix first.
Written recommendations
Every engagement ends with a written document you can act on — specific, prioritised, and grounded in your code, not a generic playbook.
Roadmap workshops
Hands-on sessions with founders and engineers to turn vague "we need to modernise" into a sequenced plan with real trade-offs.
Ongoing advisory retainer
A senior engineer on call for code reviews, hiring decisions, vendor calls, and the awkward judgement questions no one else answers.
Who this is for
Use cases
- Founders without a technical co-founder who need senior input on architecture
- Teams making a significant platform or stack decision
- Startups preparing for a technical due-diligence ahead of a funding round
- Companies with growing technical debt that needs an honest assessment
- Engineering teams that need an outside view on hiring or vendor selection
- Businesses asking whether to build in-house or buy off the shelf
How we work
Our process
Context before recommendations. Written output, not verbal promises.
Discovery
Understand your context — the business, the team, the pressure. No recommendations until we know what you're actually optimising for.
Analysis
Review the code, the infrastructure, the docs, and the people. We look at what's really there — not what the architecture diagram claims.
Recommendations
A written document with prioritised actions, trade-offs, and costs. Not slideware — something your engineers can work from on Monday.
Follow-through
Code reviews, architecture check-ins, hiring input. We stay close enough to be useful — not so close that you stop needing us.
Proof of work
Advisory in the open
Most consulting work is confidential by nature. Anonymised write-ups coming as engagements close.
Before you ask
Frequently asked questions
What's actually in a consulting engagement?
Depends on the scope, but always: conversations with founders and engineers, a real look at the code and infrastructure, and a written document at the end. We don't sell generic "digital transformation" — engagements are shaped around the specific decision or problem you're stuck on.
Retainer or fixed-scope — which should I pick?
Fixed-scope suits a clear one-off — an architecture review, a platform decision, a pre-hire technical due diligence. Retainer suits ongoing judgement calls — weekly check-ins, code reviews, someone to bounce hiring and vendor decisions off. We'll tell you honestly which fits after the first call.
Will you sign an NDA?
Yes, and we expect to. Most consulting work involves code, financials, or roadmap information that isn't public. Send us your NDA or use ours — either is fine. We treat everything shared during an engagement as confidential by default, NDA or not.
What do you actually deliver — is this just slides?
No slides. You get written recommendations in plain markdown or a shared doc — prioritised, specific to your codebase, with trade-offs spelled out. Where useful we'll include architecture diagrams, spend projections, or sample code. Something your engineers can pick up and run with on Monday.
How do you handle confidentiality and conflicts?
We don't advise direct competitors in the same market at the same time. If a conflict shows up mid-engagement we'll surface it and let you decide. Code, docs, and numbers stay with us — we don't reuse client material in other engagements, and we don't name clients publicly without explicit permission.
Ready for a senior voice on call?
Tell us what you're stuck on — we'll reply within 24 hours on working days with an honest read and a scoping proposal.