Scaling & advisoryThe leadership your business needs, before you can hire it.

Senior technical, product and commercial leadership taken on directly — as a fractional CTO or CPO, an operator alongside you, or both. Usually for founders who are not engineers themselves: a team that needs direction you cannot give it, or an idea that needs building before there is a team at all.

  • 20+ years operating
  • Founded and exited a 7-figure studio
  • B Corp founder
  • Tech & AI
What's included

What the work looks like

In whatever combination the business needs. Most engagements start with one and grow into the others.

  • Fractional CTO

    Architecture, delivery and the engineering team, owned rather than advised on. We run the standups, make the technical calls and carry the consequences of them. Product sense comes with the seat: what to build and what it will cost are the same conversation, so the roadmap gets the scrutiny the architecture does, and someone is willing to say no to most of it. Where there is no team yet, we build it ourselves — a prototype, or a first working version, written to be handed over rather than thrown away. And if you are not an engineer, all of it means someone senior to take decisions to, and those decisions coming back as commercial ones: what it costs, what it buys, and what it rules out later.

  • Commercial and operations

    Pricing, process, and the systems a business needs to scale past the founder. Most businesses that feel stuck are not short of demand — they are short of the operational structure to serve it without the founder in every decision. We work on the pricing model, the delivery process, the reporting, and the infrastructure underneath all three.

  • Founder mentoring

    One-to-one support for the decisions only the founder can make — the hire you are avoiding, the client you should fire, whether to raise, whether to sell. Regular, private, and unstructured by design. Having been on both sides of most of these calls, we are more use as a sounding board than as a framework.

How it works

From first note to working together

  1. A conversation

    Forty-five minutes on where the business is and what is actually in the way. No deck required, and no obligation on either side at the end of it.

  2. A short diagnostic

    A couple of weeks inside the business — the team, the codebase, the numbers, the roadmap. You get a written view of what we found and what we would do about it, whether or not the engagement goes further.

  3. In the seat

    An agreed number of days a month with a defined remit, and specific things we own outright rather than advise on. Fixed monthly fee, reviewed quarterly.

  4. Handover

    The point of the work is that it ends. We hire our replacement, document what we built, and hand over deliberately rather than leaving when the invoicing stops.

Who it's for

This is probably you if

  • You are not an engineer, and there is nobody senior setting technical direction for the team.
  • You have an idea and no team, and need someone who can actually build the first version of it.
  • Your developers are good, and are being left to make calls that were never theirs to make.
  • The technical choices in front of you are really commercial ones, and nobody is framing them that way.
  • You need a CTO, but that hire is six months and a six-figure salary away.
  • You are heading into a raise, a diligence process or an exit and the technology story needs to hold up.
  • You can build it perfectly well yourself — what you need is someone to help decide what is worth building.
Questions

Scaling and advisory — common questions

I am not an engineer. How does that change the way we would work?

Very little about the work itself, and a good deal about how it reaches you. We run the technical side directly rather than advising you on it, so your team has someone senior to take decisions to, and you get those decisions back as commercial ones — what it costs, what it buys, and what it rules out later. You should not have to form a view on the database in order to run the business. The short diagnostic at the start is written with exactly that in mind: a plain account of where the technology is, in language you can act on and put in front of a board or an investor.

Do we need a CTO or a CPO?

Earlier than most people expect, they are the same seat. What to build, what it will cost and what it forecloses are one set of decisions, and splitting them across two people before there is enough of either to justify it tends to slow both down. The honest test is where the pain shows: if delivery is late, unpredictable or fragile, you want the technical side. If the team ships steadily but the wrong things — a busy roadmap and a flat set of numbers — you want the product side. We take either, or both, and we would rather tell you which you actually need than sell you the larger version of it.

Can you build it, or only lead it?

Both, and they are priced differently. Where there is a team, we lead it. Where there is not — an idea, a prototype, a first version that has to exist before anything else can sensibly be decided — we write the code ourselves. That is scoped and quoted as a piece of work rather than charged as a monthly seat, because it has a defined end. What we will not do is hand you something disposable. A first version built to be thrown away costs more in the rebuild than it saved in the sprint, and most of what makes an MVP expensive later is decided in its first fortnight. It gets built to be handed to a team, because the point is that one day it is.

How much time does a fractional CTO actually spend with you?

It varies with what the business needs, and it is agreed up front rather than billed by the hour. A typical engagement is a set number of days each month with a defined remit, reviewed every quarter. Businesses in the middle of a rebuild or a raise usually want more at the start and less once the structure is in place.

Do you work with our existing team, or replace them?

Work with them, in almost every case. The team usually knows where the problems are — what tends to be missing is someone senior enough to make the calls and carry the consequences. Where a change is genuinely needed, we will say so early and directly rather than letting it sit.

How is it priced?

A fixed monthly fee against an agreed scope, so the cost is predictable and there is no incentive to stretch the work out. The short diagnostic that usually precedes it is priced separately and on its own, so you can stop there if that is all you needed. Build work — a prototype, or a first version — is quoted as a piece of work rather than as a seat, for the same reason: it has an end.

Can we pay in equity rather than cash?

Yes, and often that is the better structure. Advisory for equity puts operating, technical and product leadership into the business in place of cash — or alongside it, where a business wants to reduce the monthly cost without losing the seat. See investment and equity partnerships for how those deals are shaped.

Do you work outside the South West?

Yes. We are based in Cornwall and have a particular interest in businesses across the South West, but the work is not geographic. Good businesses are not only built within an hour of London.

Work with us

Tell us what is in the way.

A short note about the business and what you are trying to do next is enough to start. We read everything ourselves and reply to most notes within a couple of working days.