Build vs Buy — Location Strategy Brief

When to reach for this

The moment leadership poses a location question

A VP of Engineering wants to know if they can stand up an inference team in Bangalore. A Chief People Officer is weighing whether to acqui-hire a stealth chiplet startup or grow the capability in-house. A site leader asks whether to relocate from a saturated Bay Area office or seed a new hub in Penang.

Each of these is a build-vs-buy decision wearing a location costume. This brief gives you a defensible recommendation - one that names the pathways, scores them against the location, and lands on a verdict leadership can act on.

The core reframe

It's a time-and-control question, not a talent question

The instinct is to answer "is there talent in [location]?" and stop there. But supply density is only one input. Two locations with identical talent pools can call for completely different pathways depending on how fast you need capability and how much control you need over it.

The tension to surface

Speed and control pull in opposite directions. The fastest pathways give you the least control; the highest-control pathways take the longest to pay off.

Your job in the brief is not to pretend this tension away. It's to tell leadership which side of it their situation actually sits on - and to make the tradeoff explicit so the decision is theirs, made with eyes open.

The four pathways

Every location decision collapses to one of these

Leadership tends to frame the question as binary - build or buy. There are really four pathways, and naming all four is half the value of the brief. It shows you considered the full space, not just the two options already on the table.

Pathway 1

Build (Greenfield)

Stand up a new site or team, hire net-new, develop capability organically over time.

Time12-24 months to real capability

ControlHighest - full IP and culture ownership

Wins whenSkill is core to differentiation, density is high, horizon is long

Pathway 2

Buy (Acqui-hire / M&A)

Acquire a company or intact team to absorb capability and IP fast.

Time3-9 months, plus integration drag

ControlHigh, but integration-dependent

Wins whenCapability is rare and clustered, you need an intact team now

Pathway 3

Partner (GCC / Vendor / Contract)

Access capability through a global capability center, vendor, or contractors.

Time1-4 months to spin up

ControlLowest - flexibility traded for ownership

Wins whenSkill is non-differentiating, you're testing a market, sovereignty blocks direct presence

Pathway 4

Relocate (Internal mobility)

Move existing talent to a new or consolidating location to seed capability.

Time2-6 months, gated by acceptance rates

ControlHigh - they're already your people

Wins whenYou have the talent but current site is saturated; you want culture-carriers in a new hub

Pathway recommender

Start with a directional read

Three questions get you to a starting pathway. This is a directional read to anchor the conversation - not a verdict. The brief still needs the full Five-Lens scoring below before you commit a recommendation to leadership.

Interactive · directional only

What does your situation call for?

Answer all three to see a recommended starting pathway.

1. How fast do you need real capability?

2. How core is this skill to your differentiation?

3. Do you already have this talent elsewhere in the org?

Starting pathway

Directional only. Run the Five-Lens scoring before this becomes a recommendation.

Pathway comparison

The tradeoffs, side by side

This is the table leadership will look at longest. Keep it honest - every pathway has a column where it loses. Showing the losses is what makes the recommendation credible.

Pathway	Time to capability	Control & IP	Cost profile	Flexibility
Build	Slowest (12-24mo)	Highest	High fixed, low marginal	Low - hard to unwind
Buy	Fast (3-9mo)	High, integration risk	Highest upfront	Low - it's permanent
Partner	Fastest (1-4mo)	Lowest	Variable, opex	Highest - scale up or down
Relocate	Fast (2-6mo)	High - your people	Moderate, relo cost	Moderate

The Five-Lens overlay

Score each pathway against the actual location

The pathways are generic. The location is not. Run the location through Draup's Five-Lens Framework, and each lens will tip the recommendation toward or away from specific pathways. This is the analytical core of the brief.

Lens 1

Policy Friction

Visa regimes, hiring law, IP transfer rules, export controls. High friction slows Build and complicates Buy.

High friction → favors Partner or Relocate

Lens 2

Economic Gravity

Cost of talent, incentives, infrastructure maturity, currency stability. Strong gravity rewards long-term Build.

Strong gravity → favors Build

Lens 3

Capability Density

How much of the specific skill actually exists locally. Thin density makes Build slow and Buy expensive.

Thin density → favors Buy or Relocate

Lens 4

Sovereignty Constraints

Data residency, national security review, local-ownership mandates. Hard constraints can rule out direct presence entirely.

Hard constraints → favors Partner (GCC)

Lens 5

Execution Reality

Can your org actually run a site here? Management bandwidth, time-zone overlap, prior track record. The lens most often skipped.

Low readiness → favors Partner or Relocate first

Synthesis

No lens decides alone

The recommendation comes from the pattern across all five - not the loudest single signal. Name which lenses are decisive for this location and say why.

On portfolio thinking

Location strategy is no longer a single-site bet. The strongest organizations design a portfolio - scale hubs, resilience hubs, and micro-hubs - so no one decision carries the whole risk.

Paraphrased from The New Geography of Work (Draup, Jan 2026)

Building the brief

Six steps to a defensible recommendation

Step 1

Restate the decision in build-vs-buy terms

Translate leadership's location question into the underlying capability decision. "Should we open in Bangalore?" becomes "Should we build, buy, partner, or relocate to get inference capability, and is Bangalore the right place for the chosen pathway?"

Do this: Write the reframed question as the first line of the brief. It signals you understood the real ask.

Step 2

Name all four pathways explicitly

Even the ones you'll rule out. Listing Build / Buy / Partner / Relocate shows leadership you scoped the full space. Ruling options out with a one-line reason is more persuasive than silently omitting them.

Do this: For each pathway, write one sentence on why it's in or out before scoring.

Step 3

Score the location through all five lenses

Pull the real signal - capability density from a supply snapshot, policy friction from current visa and export-control status, economic gravity from comp benchmarks. Don't estimate what you can source.

Do this: Cite the source behind each lens score. A scored lens with no source is an opinion.

Step 4

Map lenses to pathways

Each lens tips toward or away from pathways. Lay out the pattern: which pathways survive all five lenses, which die on a single hard constraint, which are merely sub-optimal.

Do this: Flag any lens that is a hard gate (sovereignty, export control) versus a soft preference. Gates override preferences.

Step 5

Land a single recommendation with the tradeoff named

Leadership wants a verdict, not a menu. Give one recommended pathway, state the specific tradeoff they're accepting, and name the conditions under which you'd switch.

Do this: Write the recommendation as "Build, accepting an 18-month ramp, because density and economic gravity outweigh the speed penalty." Tradeoff in the sentence.

Step 6

Add the trigger to revisit

A location recommendation has a shelf life. Policy shifts, a competitor moves in, density thins. Name the signal that should reopen the decision so the brief stays a living document, not a one-time artifact.

Do this: End with "Revisit if: export controls tighten on this node, or a direct competitor announces a site within 50km." Concrete triggers, not "review annually."

Starter template

The one-page leadership brief

Copy this scaffold and fill it. It's built to fit on one page - leadership reads the recommendation first, then the evidence if they want it.

Leadership brief scaffold

BUILD VS BUY: [CAPABILITY] IN [LOCATION]
Prepared by: [name] · [date] · Revisit by: [trigger]

THE DECISION
We need [capability] and are evaluating how to get it in [location].
Underlying question: build, buy, partner, or relocate?

RECOMMENDATION
[Pathway], accepting [the specific tradeoff], because [the
decisive lenses] outweigh [the penalty].

PATHWAYS CONSIDERED
- Build:     [in / out] - [one-line reason]
- Buy:       [in / out] - [one-line reason]
- Partner:   [in / out] - [one-line reason]
- Relocate:  [in / out] - [one-line reason]

FIVE-LENS READ ON [LOCATION]
- Policy Friction:        [score] - [source]
- Economic Gravity:       [score] - [source]
- Capability Density:     [score] - [source]
- Sovereignty:            [score] - [source]
- Execution Reality:      [score] - [source]

THE TRADEOFF WE'RE ACCEPTING
[Plain statement of what we give up by choosing this pathway.]

REVISIT IF
- [Concrete signal 1]
- [Concrete signal 2]

What good looks like

The marks of a brief leadership trusts

The recommendation is one pathway, stated in a single sentence, with the tradeoff inside it.
All four pathways appear, even the ruled-out ones, each with a reason.
Every lens score has a source - a supply snapshot, a comp benchmark, a current policy citation.
Hard gates (sovereignty, export control) are visibly separated from soft preferences.
There's a concrete trigger to revisit, not a vague "review periodically."
It fits on one page. The evidence supports the verdict; it doesn't bury it.

Guardrails

Where AI helps, and where it can't

✓

Let AI draft the pathway comparison and first-pass lens scoring. It's good at structuring the tradeoff table and pulling public signal into a first read.

✓

Let AI surface the revisit triggers you might miss. Ask it what would change this recommendation - it often catches a policy or competitor signal you didn't list.

Never let AI set the final pathway on sovereignty or export-control questions. These are hard legal gates. A confident-sounding wrong answer here is a compliance risk, not a strategy miss. Verify against current regulation with a human.

Never present AI cost or timeline estimates as commitments. "12-24 months to build" is a planning range, not a promise. Mark estimates as estimates in the brief.

Don't let AI skip the Execution Reality lens. Models reliably over-weight density and cost and under-weight whether your org can actually run a site there. That's the lens a human has to own.

Related guides

Guide 04 · Feeds this brief

Build it, or buy it?