Short answer: hire a lean senior-led partner when the work fits under ten people and speed of decision matters; hire a large firm when you need parallel capacity across workstreams, formal governance, or a supplier that procurement and your board will accept. The difference is structural, not a question of who is better.
The structural difference
A large firm is a pyramid because it has to be. Selling many seats requires many people, and many people at senior level is neither affordable nor available. So the shape is a few architects over a broad base, and the rate you pay is blended across that mix.
A lean studio is flat because it has to be. With five people there is no base to hide behind — everyone must be able to own a system end to end, which sets a hiring floor that cannot be lowered.
Neither is virtuous. They are different machines built for different loads.
| Lean senior-led | Large enterprise firm | |
|---|---|---|
| Team shape | Flat, all senior | Pyramid, blended |
| Parallel capacity | One or two workstreams | Many |
| Decision latency | Hours | Governance cycle |
| Rate | ~€450/day, unblended | Blended, often higher for less senior time |
| Continuity | Same people, contractually | Managed by process, people rotate |
| Procurement fit | Small contracts, fast | Enterprise frameworks, certifications |
| Risk absorption | Limited | Substantial — balance sheet and insurance |
| Bus factor | Genuine risk, ask about it | Low |
Decision latency is the real variable
On a six-month build, coding is rarely the bottleneck. Decisions are.
In a five-person team, "should this be eventually consistent?" is a twenty-minute conversation between the two people who will implement it, resolved the same morning. In a large programme the same question crosses a solution architect, a technical design authority and a change board, and lands in the following cycle.
The governance exists for good reasons — it is what lets fifty engineers work on one system without destroying it. But if your system needs five engineers, you are paying the coordination cost of a structure you are not using.
Process is what you buy instead of trust. If you can get trust from five named people, you need less of it.
What a large firm genuinely gives you
Parallel capacity. Five workstreams starting the same month. No small studio can do this honestly, and the ones that claim to are subcontracting.
Procurement and board comfort. Certifications, insurance, references, a framework agreement already in place. Sometimes this is the actual requirement and pretending otherwise wastes everyone's quarter.
Risk absorption. A balance sheet behind the contract, penalties that mean something, and continuity that survives any individual resigning.
Breadth. Specialists on call — security, data, accessibility, particular enterprise platforms — that a five-person team cannot keep employed.
What a lean partner genuinely gives you
Senior density. Everyone writing your code has built the thing before.
No layer. You talk to the engineer, not an account manager relaying to a delivery manager relaying to the engineer.
Rate honesty. Ours is published: €450 a senior day, €9,500 for a bounded first slice, €7,000 a month for a dedicated team. Unblended, because there is nothing to blend.
Speed. Two to three weeks to start, decisions in hours, and no incentive to grow the team to fill the budget.
The honest risks of going lean
Bus factor. Ask how many people could cover your system, and what the handover package contains if they stop.
Capacity collisions. Ask what happens if another client needs them at the same time. A studio that says this never happens is not being straight with you.
Breadth gaps. For a specialist security audit or an accessibility certification, expect them to bring in a partner. That is fine if they say so up front.
The size test
Roughly: under ten engineers, lean wins on speed and cost. Ten to twenty, it depends on how separable the workstreams are. Above twenty parallel engineers, you need the machine that was built for it.
We say no to the third category. If your programme is genuinely that size, we will tell you in the first call rather than staff it badly. If it is not — and most are not — here is what we charge and here is what we have built.
Frequently asked
When is a large firm genuinely the right choice?
When you need many engineers in parallel across several workstreams, when procurement requires a supplier of a certain size and certification, when the programme must survive any individual leaving, or when you are buying risk absorption as much as engineering.
Why is a lean team often faster?
Decision latency. A five-person team makes an architectural decision in a conversation; a large programme makes it in a governance cycle. Over six months the cycles, not the coding, dominate the schedule.
What is pyramid economics?
Large firms are staffed as a pyramid — a few seniors over many juniors — because that is what makes the business model work. You pay a blended rate for a mix. If you need four seniors and nothing else, you are paying for organisational shape.
What is the real risk with a small partner?
Bus factor and capacity. Ask how many people could cover your system, what happens if two clients need them at once, and what the handover package looks like if they stop.