A practical guide for consulting MDs
The mandate you can win but cannot staff
There is a conversation that happens in consulting leadership meetings roughly twice a quarter. A mandate is in scope. The client relationship is warm. The work sits inside the firm’s capability. And the answer is still no, because the people who would deliver it are committed until the autumn and the hiring cycle for the profiles involved runs longer than the mobilisation window the client will accept.
Knowing how to resource a financial services mandate without expanding permanent headcount is, for most boutique and mid-market firms, the difference between a healthy pipeline and a healthy P&L. The two are not the same thing. Work you qualify and then decline is a cost, not a near miss.
Why permanent hiring is the wrong instrument for mandate-shaped work
Mandates have a shape. They run six to 14 months. They concentrate specialist demand into two or three phases rather than spreading it evenly across the engagement. And they arrive with a mobilisation window measured in weeks, because the client has usually been sitting on the business case for a year and now wants people in the room.
Permanent headcount has a different shape. A permanent hire is priced against multi-year utilisation, recruited against a generalised job specification, and available only once a notice period has run, which at the seniority these mandates require is rarely short.
The mismatch is not only about timing. A Consumer Duty remediation, a Solvency II reporting review and a Guidewire migration all sit under the same practice, and none of them needs the same person. Permanent teams have to generalise to stay busy between mandates. Mandates reward the opposite.
None of which makes flexible resources automatically the better answer. Permanent people are cheaper per day across a long engagement, they retain the method between mandates, and they carry the client relationship into the next one. Associates cost more per day and take the knowledge with them when they leave. Anyone who tells you otherwise is selling something. The question is not which model is better in principle. It is which one the shape of this particular mandate justifies.
How to resource a financial services mandate: four decisions
1. Split the team at qualification, not after award
Decide at qualification stage which layer you carry permanently and which you bring in. The permanent layer is the engagement lead, the client relationship and the method. The flexible layer is domain depth, technical build and surge capacity through the heavy phases. Firms that make this call after the award end up hiring in a panic or delivering with the wrong people, and both outcomes cost more than the decision would have.
2. Decide up front what has to stay in the firm
The real cost of a flexible layer is that the method walks out with the people. That is manageable, but only if you decide at the start what has to remain behind: the decision log, the configuration documentation, the client-facing artefacts, and whoever on your permanent team shadows the specialist through the phase. Making that decision in month seven, when the contract is ending and knowledge transfer has become a two-day handover, is how firms end up buying the same expertise twice.
3. Build the flexible layer into the rate card, not around it
A common and expensive failure: the mandate is priced on blended permanent economics, and only afterwards does anyone check what the day rate for a Guidewire configuration specialist or a Collibra data governance lead actually looks like. By then the margin has been given away in the pricing model. Price the flexible layer in at bid stage, with real rates, and the phases that usually erode margin become the phases that protect it.
4. Contract for the requirement, not the programme
A specialist phase might need a data governance lead for 11 weeks in the middle of an 18-month programme. Contract for the 11 weeks. Extending a good associate is straightforward. Carrying a permanent hire through seven months of low-value utilisation, because the contract was written against the programme rather than the requirement, is not.
Where the difference actually shows up
Not at submission. Two firms can produce very similar documents, and often do. The difference surfaces at clarification, when the client asks who specifically will run the data migration workstream, when that person can start, and what happens to the plan if the programme slips a month.
One firm answers in the meeting. The other takes it away, makes three phone calls, and comes back with a name and a caveat attached to it. Procurement notices the caveat. So does the delivery director who will have to live with the answer for the next year.
Where SR2 fits
The resourcing conversation usually happens after the award, when the mobilisation date is already fixed and the realistic options have narrowed to whoever is available. Having it at qualification instead costs nothing and changes what you are able to bid.
SR2 Consulting works with financial services consultancies as a named delivery partner. We put practitioners into your submission by name and mobilise them inside two weeks of award. Before that, we give you a straight answer on what the specialist profiles in your scope cost and how quickly they can realistically move.
If you have something in qualification now, talk to the SR2 Consulting team while the pricing is still open.
Related reading: why financial services consultancies keep losing mandates to specialist boutiques and why specialist technical profiles are your margin lever in insurance transformation.
