The case for taking fewer projects

The pitch every independent studio makes is depth: senior people, in the room, from the first call to the last handoff. It is a real advantage, and it is the first thing to disappear when the calendar fills.

What the calendar actually buys

Six projects running at once does not mean six projects getting attention. It means the senior team is in review mode — arriving late, reacting to work, leaving before the consequences land. The client bought the person who sold the work and got that person’s opinion, delivered quickly, on someone else’s execution.

Three projects running at once means the same people are in the material. That is a different product, and it is the one worth charging for.

Saying no is a design decision

Turning work down feels like a business decision. It is a design decision, because every yes sets the conditions the rest of the year’s work happens in.

We ask three questions before taking a project on:

1. Is the real problem the one they named? If the brief says identity and the problem is positioning, the project fails at launch no matter how good the identity is.
2. Is there a decision-maker in the room? Work that has to survive a committee it never met comes back diluted, and the studio takes the blame for the dilution.
3. Can we do the strongest version of this? Not the acceptable version. If the timeline or the budget only supports the acceptable version, the answer is no, kindly and early.

Utilisation is the wrong number

Agencies optimise for utilisation because it is easy to measure. It is also the metric most directly opposed to the thing clients hire a small studio for.

The metric	What it optimises	What it costs
Utilisation	Hours billed per person	Thinking time, which is where the value is
Projects per year	Pipeline confidence	Depth on each one
Outcome per project	The work’s life after handoff	Short-term revenue, occasionally

The third is harder to put on a dashboard and it is the only one a client ever feels.

Nobody has ever renewed a contract because the studio was busy.

What this looks like in practice

We run a handful of engagements a year. Each one has a named lead who does the work rather than supervising it, a fixed scope agreed before the first invoice, and a deliberate gap after launch where we are still available and not yet booked.

That gap is not slack. It is where the launch actually gets fixed — the state nobody anticipated, the asset the team needs in week two, the question that only surfaces once real customers are through the door.

The trade, honestly

Fewer projects means a longer wait for a start date, and it means we sometimes recommend a studio better suited to the brief. Clients occasionally find both frustrating. It is still the trade we make, because the alternative is being a slightly cheaper version of a company that already exists at scale.