For VCs, PE and angels

Know what you're buying before you buy it.

You're pricing a company whose biggest risk might be sitting in a private repo. I've been the CTO many times over, across fintech, e-commerce and legaltech. I read codebases and weigh the teams and roadmaps behind them for a living, and I'll tell you plainly what's real, what's fragile, and what it costs to fix.

When investors call me

  • A term sheet is drafted and nobody on the deal team can read the codebase.
  • The founders say "it's AI-powered" and you'd like to know if that's true.
  • A portfolio company just lost its CTO mid-raise.
  • The demo was great; the question is whether it survives 100x the traffic.
  • Post-investment, delivery has stalled and the board can't tell why.

Two ways I work with investors

Before the cheque

Technical due diligence

A focused review, typically one to two weeks, of what actually matters to the deal: architecture and scalability, code and delivery health, team strength and key-person risk, security posture, AI claims versus AI reality, and the true cost of the roadmap. You get a plain-English report with red flags ranked by deal impact, and a 30/60/90 plan for whatever we find. Written for partners, not engineers.

After the cheque

Leadership inside the company

When the finding is "good business, technology needs an owner," I step into the portfolio company as fractional CTO: roadmap, hiring, architecture, security, delivery. Same operator who wrote the DD report, accountable for fixing what it found. One to three days a week, up to a designed handover to a permanent hire I'll help you make.

Why me for this

  • A CTO and Director of Engineering, many times over. I've been the person being diligenced, and the person doing it.
  • Scaled LoyaltyLion from £4.5m to £14.5m ARR and 10,000+ merchants; built systems for Tier 1 banks at CloudMargin.
  • Led SOC 2 and ISO 27001 from scratch. I know what "we're basically compliant" usually means.
  • AI-native. I build with it weekly, so I can tell a model wrapper from a moat in an afternoon.
  • No agency, no juniors, no report written by someone who wasn't in the room.

How an engagement runs

01

A 30-minute call on the deal or the portfolio problem. Confidential, NDA on request.

02

Scope agreed in writing: questions, access, timeline, deliverable.

03

The work: repo, architecture, team interviews, infrastructure, security.

04

Report and a partner-level debrief. If you need hands afterwards, that's a separate decision, never a hidden pitch.

One deal, one portfolio company, or a standing arrangement across the fund. Start with the call.

I take on at most five engagements at a time. DD sprints are scheduled around them.