Build it or buy it: when a venture should own its tech layer

Every venture faces the same fork on its core stack: build it or buy it. Get the call wrong in either direction and you pay for years. There is a cleaner way to make it.

Disclosure: the worked example here uses ventures in our own portfolio and our shared infrastructure. We name that up front. The framework is general.

Every venture hits the same fork, usually in month two. Build the core stack, or buy it. Get it wrong in one direction and you've sunk a year reinventing something you could have licensed for a few hundred dollars a month. Get it wrong in the other and you've rented your own moat from a vendor who can raise the price or walk away. Both mistakes are common. Both are expensive. Neither is obvious in the moment.

So here is the framework we actually use, and the worked example from our own portfolio.

The wrong question

"Should we build or buy?" asked in the abstract has no answer, which is why teams argue about it in circles. The honest version is two questions, asked component by component.

Is this component a source of durable advantage, something that gets more valuable the more we own and operate it over time? Or is it undifferentiated plumbing that every venture needs and nobody wins on?

Ask it that way and most of the fog clears. The fork isn't build-versus-buy as a philosophy. It's a sorting exercise, run one piece at a time.

Build the moat, buy the plumbing

The rule that falls out is short.

Build what compounds into advantage. If owning and operating a component makes it more valuable over time, and if it's close to why the venture wins, build it. A proprietary data layer is the clearest case: the intelligence a venture accumulates on its own activity gets better with use and can't be quickly copied, so owning it is the moat (a point worth its own field note). Anything that is genuinely the product, or genuinely the edge, you build.

Buy what's undifferentiated. If a component is necessary but identical across every venture in the category, and nobody is going to win on it, buy it or rent it. Payments processing. Email infrastructure. Basic identity verification. Generic cloud. Building these from scratch is rarely a moat; it's usually just expensive not-invented-here, and the months you spend on it are months you didn't spend on the part that actually differentiates you.

Build what's the moat. Buy what's the plumbing. Most ventures get this backwards: they rent the thing that should be theirs and hand-build the thing they should have rented.

The failure mode runs both ways, and it's almost always a mis-sort, not a bad philosophy.

The studio's twist: shared infrastructure

A studio adds a third option most standalone ventures don't have, and it changes the math on the "buy" side.

When a studio has already built common infrastructure (operating tooling, an issuance rail, identity and reporting plumbing), a new venture doesn't face a clean build-versus-buy choice. It faces build, buy, or inherit. Inheriting shared infrastructure gives a venture something that behaves like "build" (owned within the group, tunable, not at the mercy of an external vendor's roadmap) at something closer to the cost and speed of "buy."

Take the real-asset venture we back. Its core differentiation, the platform experience and the proprietary data layer, gets built, because that's the moat. But its back-office plumbing, the fund-operations and reporting machinery, can run on infrastructure the studio already operates rather than being rebuilt from scratch or rented from a third party. Moat built. Plumbing inherited. The venture spends its scarce build time on the part that's actually differentiating.

Why this is an operator's call, not a slide

Build-versus-buy gets framed as a strategy decision. It's really an operator's decision, made component by component, by people who've felt the cost of getting it wrong in both directions. The discipline isn't picking a side. It's sorting honestly: this piece is the moat, build it; this piece is plumbing, don't.

A studio's edge is that it's run this sort enough times to have a fast, opinionated answer, and enough shared infrastructure that "inherit" is on the menu. For a venture, that can be the difference between shipping the moat this quarter and spending the quarter rebuilding plumbing nobody will ever credit it for.

Build what's the moat. Buy, or inherit, the rest.

Read next: The Layer-1 model: financing the tech under a real asset

Nothing here is an offer to sell a security or investment advice. The worked example references ventures and shared infrastructure in our own portfolio, several of which are in active development; descriptions reflect design intent and general approach, not a representation that every capability is live.