Who it's for

Three situations,
one way of working.

The starting point differs. The method does not. Two of these sit inside a single business, one sits a level above it, across a portfolio. All three run through the same four stages and the same order of work. What changes is where the weight falls, and how fast.

Situation one

Scaling businesses

You might be here if

  • Growth has started outrunning the systems underneath it, and workarounds are becoming the process
  • Nobody in the building has done a transformation programme before, and the decisions are getting expensive
  • There's a sense that the current stack won't survive the next phase, without much clarity on what should replace it
  • A board or investor has started asking questions about data that take a week to answer properly
  • The obvious answer is “we need a CTO”, but the actual need is judgement on a handful of decisions, not another salary

Who usually brings this in

A founder, CEO or CFO, occasionally a growth investor pushing for professionalisation ahead of the next round.

Where the weight falls

Design-heavy. The useful work here is building the operating model and stack the next phase of growth needs, and sequencing that investment so it lands ahead of the pain rather than in response to it. Diagnosis matters, but the value is in the plan.

The pace

Measured. Aligned to funding cycles and hiring rhythms rather than a crisis.

Situation two

PE-backed and turnaround situations

You might be here if

  • A business has been acquired, or is about to be, and nobody yet has an honest map of the technology inside it
  • Costs are known to be too high but nobody can say precisely where, or what stopping them would break
  • A transformation programme is underway and quietly slipping, and the reporting has stopped feeling reliable
  • There's an incoming CEO or CRO who needs the real picture in weeks, not quarters
  • A value-creation plan assumes systems work that nobody has independently pressure-tested

Who usually brings this in

A PE operating partner, turnaround director, CRO or investor, sometimes an incoming CEO who wants an independent read before committing to a plan they'll be held to.

Where the weight falls

Discover-heavy. Rapid, evidence-based triage: what's actually broken, what it's costing, and what to stop, keep and fix, in a form that feeds straight into a value-creation or recovery plan.

The pace

Fast. Findings are often needed inside weeks, because a live decision is waiting on them.

Situation three

Funds, at portfolio level

You might be here if

  • Several holdings are being asked the same questions about AI readiness, and the answers arrive in different formats with different levels of rigour
  • There is no shared benchmark for what good looks like, so each company is assessed against whichever partner happens to be in the room
  • It is unclear which holdings genuinely need intervention and which are being over-serviced by people already inside them
  • A value-creation plan assumes technology work that nobody independent has pressure-tested
  • Diligence on a live deal needs a technical read from someone who has run these programmes rather than modelled them

Who usually brings this in

A value-creation or operating partner, occasionally a fund's head of data and AI where that role exists.

Where the weight falls

Breadth rather than depth. The same judgement applied consistently across several businesses, with a shared standard so results are comparable, and a clear view of where attention is actually worth spending.

How it works commercially

A standing relationship at fund level rather than an engagement per company. Individual pieces of work inside portfolio companies are scoped separately as they arise, and usually arrive better qualified because the context is already understood.

The common thread

All three need the same thing: someone senior who has no reason to tell them what they want to hear.

In a scale-up, that means being willing to say the expensive new platform isn't the answer yet. In a turnaround, it means being willing to say the existing delivery partner is part of the problem, or that the plan the business is already committed to won't survive its own foundations. At portfolio level, it means being willing to say a holding needs less attention than it is getting, or that a value-creation plan rests on technology work nobody has tested.

None of those conversations is comfortable. All of them are the reason to bring in someone from outside.

Before you call

The questions each side usually asks.

If you're scaling

We're probably too small for a proper ERP programme. Is this still relevant?

Usually more relevant, not less. Most of the value at this stage is in not buying the platform yet: getting the data and process foundations right so that when the spend does happen, it works first time.

Does this end with you telling us to replace everything?

Rarely. “Keep, but fix” is the most common recommendation, and the cheapest. Replacement is the answer occasionally, and when it is, the reasoning gets shown rather than asserted.

We have one developer and a lot of spreadsheets. Where does that leave us?

Exactly where most businesses at this stage are. The spreadsheets get mapped rather than judged. Several of them are probably doing real work, and one or two are almost certainly a risk nobody has named yet.

We're mid-raise. Is this the wrong time?

It's often the right time. Investors ask harder questions about data and systems than they used to, and having honest answers ready, including about the gaps, tends to go better than discovering them during diligence.

If you're investor-backed or turning something around

How quickly can you give us something usable?

Findings in weeks rather than months. The diagnostic is designed to produce something that can inform a live decision, not a document that arrives after the decision was already forced.

Will you tell us if our existing delivery partner is the problem?

Yes, and that assessment gets made against the same criteria used to qualify any new partner, with a clear keep, fix or replace position. It's frequently the reason for the call in the first place.

Can this feed directly into a value-creation plan?

That's what it's shaped for. The output is an evidenced position on what to stop, keep and fix, with indicative cost ranges, written to be used in a plan rather than read once and filed.

Will the evidence stand up to scrutiny?

Every assessment carries the evidence behind it. Nothing is scored on impression, which matters when the findings have to survive an investment committee rather than just a management meeting.

Do you work at fund level, or only with individual portfolio companies?

Both. A single portfolio company is the more common starting point; fund-level advisory across several businesses works the same way, at a different altitude.

If you are a fund

Do you work with the fund, or with individual portfolio companies?

Both, and they work differently. Portfolio-level work is a standing relationship across several holdings. Work inside a single company is scoped as its own engagement, and often starts from something the portfolio view surfaced.

How is this different from what our operating partners already do?

It is not a replacement for them. Operating partners carry relationships, sector knowledge and commercial judgement. This adds a technical read that most funds do not have in house, applied consistently enough that holdings can actually be compared against each other.

Can this support diligence on a live deal?

Yes. An independent technical read before a value-creation plan is written on assumptions is usually cheaper than discovering the same things afterwards.

What if a portfolio company already has a delivery partner in place?

That gets assessed against the same criteria as any new partner would, with a clear keep, fix or replace position. It is frequently the most useful thing the exercise produces.

Start with a conversation,
not a pitch.

Thirty minutes is usually enough for both sides to know whether there's a genuine fit, including if the honest answer is no.