Decision to operational, in a quarter
Twelve to eighteen months was never the true duration of this work. It was the duration of doing it sequentially. Here is what actually runs in parallel, and what genuinely cannot.
Almost none of this work is actually sequential
The traditional timeline was long because each step waited for the previous one to finish, not because any individual step is slow.
The eighteen month capability centre timeline was real, and it was mostly an artefact of sequencing. Entity formation finished before office space was signed, which finished before infrastructure was procured, which finished before hiring opened, which finished before onboarding began. Each handoff added a wait, and the waits were most of the elapsed time.
Almost none of that ordering is necessary. Entity formation, compliance registration, infrastructure provisioning and the senior search have very few genuine dependencies between them. Run in parallel, the same work compresses to roughly a quarter, and the critical path becomes what it always should have been: finding the right first hire.
Four tracks, one critical path
Three of these tracks are administrative and predictable. Only one determines the date, and it is the one most plans start last.
Track 1: Entity and compliance
Company formation, tax and statutory registration, banking, and the annual compliance calendar. Predictable, well trodden, and no reason for anything else to wait on it.
Track 2: The senior search
The actual critical path. Opens on day one, because the pod lead determines every subsequent hire and no amount of parallelism compensates for starting it late.
Track 3: Infrastructure and access
Workspace, devices, environments, identity and security tooling, provisioned under your policies. Slow only if it starts after the first hires arrive.
Track 4: Operating model
Decision boundary, escalation path, reporting lines and the transfer plan. Costs nothing, takes a few weeks, and determines whether the rest works.
What actually happens, and when
All four tracks open
Entity filing begins, the pod lead search opens, infrastructure requirements are specified and the decision boundary is drafted. Nothing waits on anything else.
Entity progresses, first candidates
Registration and banking proceed on their own timeline. First serious pod lead candidates in process. The operating model is agreed and written down, not left implicit.
Pod lead hired, team search opens
The lead joins and immediately begins interviewing the rest of the team. This is the moment the critical path unlocks and everything downstream accelerates.
Senior engineers and decision maker
Hiring against the boundary that was defined in week two. Infrastructure and access provisioning complete in parallel so nobody waits on a laptop or a login.
Onboarding and first output
Product and domain context transferred deliberately rather than absorbed. First production changes ship. Readiness is what is measured up to this point.
Transfer of a real system
A named system changes hands on a named date with the onshore approval gate removed. Escalation rate becomes the headline metric.
Four things, and only one is outside your control
In practice, launches slip for the same small set of reasons. Three of them are decisions you can make in week one.
| Cause of delay | How much it costs | Whether you control it |
|---|---|---|
| Starting the senior search late | 4 to 8 weeks | Entirely. Open it on day one. |
| Access and environments provisioned after arrival | 3 to 6 weeks | Entirely. Run it as a parallel track. |
| Decision boundary left undefined | Indefinite | Entirely. It costs a few weeks and determines everything. |
| No named transfer date | Indefinite | Entirely. A ramp without an end does not end. |
| Right pod lead not available immediately | 2 to 6 weeks | Partly. Worth waiting for; the ceiling for every later hire. |
| Statutory processing times | 1 to 3 weeks | Not really, and it is rarely the binding constraint. |
Note the pattern. The genuinely uncontrollable item is also the smallest. Almost all real delay comes from decisions that could have been made in week one and were not.
What has to be true on day one
These are cheap to settle up front and expensive to settle later, because by then people have been hired against assumptions nobody wrote down.
- A named executive sponsor who will protect the centre through its first difficult quarter
- A specific system or outcome the team will own, not a general intention to add capacity
- The decision boundary written down: what the team decides without asking
- A transfer date in the plan before the first job description exists
- A fully loaded cost model including ramp, attrition and onshore management overhead
- The baseline captured: what this work costs and produces today, before anything moves
The baseline is the one that gets skipped. It takes a week and it is only available before the work moves. Afterwards every comparison becomes an argument between people with different interests in the answer, which is how centres end up unable to prove savings they genuinely delivered.
Where the twelve months actually went
The same work, ordered differently. Almost all of the traditional duration was waiting rather than doing.
Illustrative breakdown of where elapsed time went in the traditional sequential model rather than measured research. The bottom two rows are the only ones that are really irreducible.
This is the entire argument for the compressed timeline, and it is worth being precise about it. We are not doing any individual step faster than it has ever been done. We are removing the waiting, which was always the majority of the duration, and accepting a small amount of overlap risk in exchange.
Who is accountable for what
Entity, compliance and payroll
We run it end to end: formation, registrations, banking, statutory calendar and the annual filing cycle. It is not a track you have to project manage.
The senior search
We run it, you interview. The pod lead is your hire and should feel like it, because every later hire is chosen with them rather than for them.
Infrastructure and access
Provisioned under your policies rather than ours, which matters for anyone with a control environment to answer for.
The operating model
We draft the decision boundary, escalation path and transfer plan, and we will push back if the boundary drawn is too tight for the seniority being hired.
The timeline was never twelve months of work. It was three months of work with nine months of waiting distributed through it.
Frequently asked questions
Is 90 days realistic, or is it a marketing number?
Three to four months from decision to first productive output is realistic for a small senior team, and we hold ourselves to it. What makes it achievable is parallelism rather than speed: no individual step is rushed, they simply stop waiting for each other.
What is the single biggest cause of delay?
Starting the senior search late. The pod lead is the critical path, every later hire depends on that decision, and no amount of parallelism elsewhere compensates for opening the search in week six instead of week one.
Can entity formation really run alongside hiring?
Yes. The two have almost no genuine dependency until the point of making an offer. Treating them as sequential is the single largest source of unnecessary elapsed time in the traditional timeline.
What if we cannot find the right pod lead quickly?
Wait. This hire sets the ceiling for everyone hired after them and shapes the whole team. A two to six week delay here is far cheaper than a year spent working around a lead who was available rather than right.
When should we expect real delivery?
First production changes around week ten to sixteen, and ownership of a named system between month four and six. Expecting delivery metrics before week ten produces activity theatre and teaches the team to optimise for looking busy.
Do we need office space from day one?
Rarely. Workspace is a decision that can follow the team rather than precede it, and treating it as a precondition is one of the assumptions that made the old timeline long. It should never be on the critical path.
What happens in the first 30 days after the team starts?
Readiness, not output: every engineer able to build, run and test the system, first production change shipped, product context delivered, and the escalation path explained. Measuring delivery in this window is counterproductive.
How do we know it is working?
Escalation rate, tracked monthly from the first month of operation. It should begin falling by the end of the second quarter. If it is flat at six months, the approval gates were never actually removed, whatever the plan says.
Related reading
Get a launch plan with real dates on it
Tell us what you want owned and by when. We will come back with a week by week plan, the four parallel tracks, a fully loaded cost model and the date the team would be shipping.