Case studies
Four programmes. Four constraints that would not move.
Our clients include energy majors, banks and global systems integrators across the Gulf and India. Their names are theirs, not ours — so here is the work instead, described precisely enough to be useful.
Every one of these turned on something that could not be negotiated: a window, a date, a standard, a shortage. That is the part worth writing down.
- BriefDate set by the plant
- SponsorshipRoute confirmed before shortlist
- VisasCleared in parallel with interviews
- MobiliseArrivals staged, not batched
The window could not move.
A turnaround window is set by the plant, not by the programme. Everyone downstream works backwards from a date that will not negotiate — and the specialist engineering support had to be on site, in country, before it opened.
- What was actually hard
- Not the shortlist. Sponsorship, visa timing, mobilisation and site access were the critical path, and they run on government timelines nobody in the room controls. A perfect candidate who lands after the window opens is not a candidate.
- What we did
- Right to work and the sponsorship route were confirmed before names reached the client, not after offer. Mobilisation ran in parallel with interviews instead of behind them, and arrivals were staged so the first engineers were productive while the rest cleared.
- What changed
- The team was on site inside the window. The date held.
We tell you the realistic mobilisation timeline in the first conversation. It is usually longer than people expect, and planning for it is what makes the date hold.
- In countryWork had to sit inside the border
- LocalisationPlanned into hiring, not bolted on
- ControlsScreened to the bank's own bar
- MarketOffers shaped for who else was bidding
A regulator's date is not a target.
A modernisation programme with a compliance deadline attached. Miss it and the conversation stops being about technology.
- What was actually hard
- Three constraints that each rule out most of the market: the work had to sit in country, the localisation commitments were part of the plan rather than a footnote, and the same small pool of specialists was being courted right across the market at the same time.
- What we did
- Built localisation into the hiring plan from the start instead of retrofitting it. Screened to the bank's own controls, not a generic bar. Shaped offers for what that market actually pays — which is sector knowledge, not negotiation.
- What changed
- Delivered to the date. More usefully, the capability stayed after it.
Hiring against a deadline rather than a standard is how a bank inherits a problem that outlasts the deadline.
- VolumeA squad's worth of roles at once
- One standardSame evaluators, every role
- CadenceA predictable slate each week
- HonestyWhich roles would not fill, said early
Thirty people. One bar.
A systems integrator won a programme and needed a delivery squad ramped in weeks, with their own client auditing the quality of every person on it.
- What was actually hard
- Volume is where standards quietly fail. Run thirty roles as thirty separate searches and the bar moves before you reach the end of it, because everyone is tired and the deadline is closer.
- What we did
- Ran it as one hiring programme, not thirty searches — a single evaluation standard applied by the same people, a predictable weekly slate, and honest early calls about which roles the market would not fill on that timeline.
- What changed
- Ramped on schedule with the bar intact. The engagement became a standing channel rather than a one-off.
Telling a client which roles the market will not fill in time is worth more than quietly filling the ones that will and going silent on the rest.
- SplitIndustrial and software, sourced apart
- PricedEach against its own market
- SequencedTo the build phase, not the plan
- SponsoredConfirmed by role type up front
The scarcity is global. The site isn't.
A large-scale data centre programme in the Gulf, with Bench FX mobilising the technology manpower behind it. Facilities at this specification are still uncommon across the region. Most people who have commissioned one built that experience somewhere else.
- What was actually hard
- Two labour markets, not one shortage. Power, cooling and commissioning specialists come out of a project-based industrial market; cluster, fabric and platform engineers come out of a software one. Different sourcing channels, different pay references, different notice behaviour, and no settled local pay reference for either at this specification — while other large builds elsewhere are bidding for the same people.
- What we did
- It is being run as two sourcing programmes under one plan. Each is priced and sourced against its own market, not against the other. Roles are sequenced to the build phase, so people arrive when there is work for them rather than waiting on site. Sponsorship routes are confirmed by role type before names go forward, and depth is drawn from our India network where the region cannot yet supply it.
- What it sets up
- This one is being staffed now, not finished. What the phase is set up to produce is a team the region keeps afterwards — people who have done it here, and who can train the teams that follow.
The hardest role to fill on an AI build is rarely the one with AI in the title. It is the person who has commissioned power and cooling at this scale before.
What is the date you cannot move?
Tell us the constraint. We will tell you what staffing to it realistically takes — including when the answer is that it does not.