Startup operations

Startup operations consulting for Seed to Series B companies

Startup operations consulting is the work of designing how a company runs — the operating model, who decides what, how planning and delivery are sequenced, and what gets measured — and then getting it into daily use. Groundwork does this for UK technology companies between roughly 15 and 150 people, as a defined piece of work with an owner, a timeframe and a handover.

What an operating model actually is

It is not a diagram. It is the answer to a short list of questions that a growing company stops being able to answer informally: how work arrives and gets prioritised, who owns which decisions, how teams are organised against the work rather than against history, what the company measures, and what rhythm it runs to. Startups do not usually lack these answers. They hold them implicitly, in a small number of heads, and that stops scaling somewhere around twenty-five people.

The consulting work is making them explicit, testing them against how the company really behaves, and installing whatever is missing.

Accountability and decision rights

The single highest-leverage change in most companies at this stage is writing down who decides. Not a RACI matrix for its own sake — a short, blunt list of the decisions that actually come up, and who owns each. Most founding teams are surprised by how much of what they are personally deciding could be decided two levels down, and how much of the delay in the company is people waiting politely for permission nobody needed to give.

Cadence and planning

A cadence is the predictable rhythm at which priorities are confirmed, work in flight is visible, and something that is not working can be said out loud without it becoming an escalation. Start smaller than feels right. One weekly forum with a clear purpose beats four with overlapping attendance, and a meeting people quietly stop attending is worse than none because it teaches the team that structure is theatre.

Planning is the same discipline over a quarter: a short list of outcomes, named owners, and an honest read on capacity before the commitments are made rather than in the retrospective afterwards.

Hiring infrastructure

Growing headcount is not the same as growing capacity. What turns one into the other is defining the seam a role is meant to close before opening it: what decisions it owns, what it is measured on, and who it unblocks. Add the sequence — which roles have to exist before which others can succeed — and an onboarding path that gets someone useful in weeks rather than a quarter, and hiring stops being the thing that makes the organisation more complicated.

Business operations and the P&L

The unglamorous layer that becomes load-bearing at exactly this stage: the numbers the company runs on and who owns them, the link between the plan and the spend, board and investor reporting assembled from things you already measure, and the contracts and vendor commitments that quietly accumulate. Where the commercial side of that is the pressing part, it is covered in more depth under commercial operations.

Execution systems, and the capability to run them

All of the above is worth nothing if it lives with us. Every engagement is built to be handed over: the leaders who will run the cadence are in the room while it is designed, they run it while we are still there to say when it is drifting, and the coaching that goes with it is part of the work rather than an add-on. That is the difference between a company that changed and a company that had a project.

Whether this is the right fit

This is for you if

  • Roughly 15 to 150 people, in technology, with a real product and real customers.
  • A founding team prepared to change how decisions are made, not only how they are documented.
  • A specific outcome you can name, even roughly, and a date it matters by.
  • An appetite for the smallest structure that works rather than the most complete one.

This is not for you if

  • You want a framework rolled out because a board member named it.
  • You want process for its own sake. We take process out at least as often as we put it in.
  • The company is pre-product and pre-team, where the honest answer is that structure would slow you down.
  • Nobody is available to own any of it after we leave.

How the work is sequenced

Diagnose, design and validate, then coach and hand over. The shape is the same whether the engagement is six weeks or two quarters; only the depth changes.

Weeks 1–3

Diagnose

How the company actually runs, where the work gets stuck, and which two or three changes carry most of the value. Delivered as a decision-ready read, not a deck.

Weeks 3–8

Design and validate

Decision rights, cadence, planning, role definitions and the reporting line. Tested against real work and real disagreements rather than in principle.

Weeks 8+

Coach and hand over

Your leaders run it while we are still in the room, then own it. Documented, with the awkward parts written down rather than smoothed over.

Common questions

What size of company is this for?

Most of our work is with technology companies between roughly 15 and 150 people, typically Seed to Series B. Below that, structure usually costs more than it returns. Above it, the problems change shape and you are generally hiring permanently for them.

How is this different from hiring a COO?

Consulting is a defined piece of work with an end. A COO is a continuous role. Many companies need the first before they can write a sensible job description for the second — see fractional COO support for the middle option between them.

Will this add process we do not want?

We remove at least as much as we add. The test for any piece of structure is whether it makes a decision faster or a commitment more reliable. If it does neither it should not exist, and several of the things we take out were added for reasons that stopped applying a year ago.

Do you work with the leadership team or just the founders?

Both, and the leadership team is usually where the durable change happens. Whoever will still be running the cadence after we leave needs to have been in the room while it was designed, or it will not survive contact with a busy quarter.

Start with an honest read on how the company runs.

A short diagnostic sequences the problem so you fix the right thing first, rather than everything at half strength.

or email hello@groundworkconsultancy.com
Book a free call