Build vs. buy — adjacent market expansion

Question → Opening positions → Rebuttals → Concessions → Neutral synthesis

The question

Your business is looking to expand into a new market adjacent to the core business. It is not your core business but the knowledge can translate: do you acquire a company operating in that market, or build your own product & expertise internally?

The panel

Risk Analyst · Financial Modeler · Strategist

Azrivo convened the panel and set them against each other; a neutral synthesis made the call.

Opening positions

Financial Modeler: Acquire, not build — the numbers are unambiguous where you lack existing product and expertise; time kills value.
Risk Analyst: Buy, not build — when the market is knowable and your knowledge partially transfers, acquisition is the lower-risk path.
Strategist: Build first to learn; acquire only once a wedge has told you something worth paying a premium for.

A rebuttal — the “double-pay” against building first

Financial Modeler → Strategist: “…if the wedge validates the thesis, you still acquire — now you're paying the acquisition premium plus the sunk wedge cost. You've paid twice for the same market entry.” The Strategist pushed back that an acquisition prices a “known” distribution that integration reshuffles: “you're modeling a known past distribution as if it holds under new management. It doesn't.”

A concession — the panel revised, it didn't just restate

Strategist, closing: “Both opponents made valid points. The Risk Analyst is right that the wedge consumes time you can't get back, and the Financial Modeler correctly flags the double-pay. Their arguments force me to sharpen, not abandon, my position.” Financial Modeler: “Risk Analyst is right that integration costs can balloon … I should have modeled that as a range, not a point estimate. Fair.”

The decision memo (neutral synthesis)

Recommendation. Acquire a small, focused tuck-in target, but don't integrate on day one — operate it autonomously for 6–12 months to test the knowledge-translation thesis, then integrate once it's validated.
Decision boundary. The call flips to building a wedge first if you cannot retain the target's key talent for at least 24 months post-close.
Key trade-off. Immediate market presence (acquisition) versus the risk of losing the acquired team's knowledge through integration failure.
What would make it fail. The load-bearing assumption is retention. If key talent leaves, the acquisition loses the knowledge you paid for. A second risk is timing: a competitor could pivot into the same market while you are still testing the autonomous unit.
The strongest case for the other side. An adjacent market's invisible differences can make a diligent acquisition price catastrophically wrong; a focused customer trial can surface that cheaply first.

A reviewable first draft — not a production guarantee. Every element is AI-generated and can be wrong; verify anything before you ship it.