What 'senior-led' actually means in delivery

The pitch deck for nearly every consultancy says the same thing. The work is senior-led. The team is hand-picked. The engagement is partner-supervised. By the time the contract is signed and the first sprint starts, the people on the actual Slack channel are usually two seniors, four mid-level engineers, and a project manager who has the partner’s calendar but not the partner’s attention. Senior-led ends up meaning that a senior was at the kickoff and a senior reviews the deliverables, with most of the work happening at a level that is not the level the buyer was promised.

We say “senior-led” too. We mean something narrower by it, and the narrowness is the entire point.

The constraint we hold ourselves to

The engineer typing on your codebase has shipped to production for at least seven years. They’ve led the architecture of at least one system that handled real customer load. They’ve written, in production, the kind of code they’re now writing for you. Their work goes through review by another senior on the team, not by a tech lead two layers removed who hasn’t opened the codebase that month. There’s no junior on the team who is shipping client code unsupervised. There’s no project manager between you and the engineer.

This is a small set of rules. It costs more than the alternative. We hire fewer people, we charge engagements at a rate that reflects the seniority on them, and we turn down work where the budget would only support a thinner team than the model demands. Those are the trade-offs we made when we wrote the rules. We think they are the right trade-offs for the kind of work we want to do, and we think a buyer reading this should be able to tell whether they are the right trade-offs for the kind of work they need to commission.

Why this changes the engagement shape

A senior-led team writes a different kind of proposal. Where a generalist consultancy will scope a six-month rebuild and resource it across a pyramid of seniors and juniors, we tend to scope smaller engagements with smaller teams that finish in less time. Three senior engineers for ninety days will outpace eight engineers across a two-pyramid for six months on the kind of work we take, because the coordination cost is much lower and the rework rate is much lower. We are explicit about this in the proposal, because the per-engineer cost on our team is higher and the comparison only makes sense at the engagement level. See also hiring senior engineers vs an agency for your v1 for the buyer-side framing.

A senior-led team also pushes back differently. When a buyer asks for something that will create a maintenance burden in eighteen months, a junior will build it as specified and a tech lead will sign off because the deliverable matches the requirement. A senior who has lived through the eighteen-month consequence of similar decisions will say so on the call, propose an alternative, and absorb the awkwardness of disagreeing with the buyer in writing. This is uncomfortable for the buyer in the first week and valuable in the second quarter. It is also a small thing the engagement model has to actively protect, because the easy path for any vendor is to deliver what was asked rather than what was needed.

What we will not do under this banner

We will not put a senior name on a pitch deck and run the engagement with a different team. We will not staff a project with one senior and three juniors and call the team senior-led on the basis of that one person. We will not take on a third concurrent engagement that would dilute the seniors who are already on two. The constraint is real, and the constraint is narrow, and we would rather lose the deal than soften the meaning of the phrase.

If “senior-led” means something more flexible to a different vendor, that is a real difference between the two of us, and the buyer should know which one they are getting. We try to make it easy to tell.