You don't need to build a brewery to drink a pint of beer

The most expensive software decision a founder makes is often the very first one: the decision to build. Standing up a team and a custom product is the default instinct, and for a lot of companies it is the wrong one. You don't need to build a brewery to drink a pint of beer. The right opening question is not "how do we build this" but "should we build this at all", and in 2026 that question has a different answer than it did even two years ago. Here is how to decide between building, buying, no-code, and an agency.

The one question that decides it

Almost everything turns on a single question: is this technology core to your business? Build an internal team when the technology is genuinely yours, proprietary inventions or data, regulated or security-critical, highly complex, or part of a long-term product you will keep extending. In those cases the control, independence, and compounding value of an in-house team are worth the cost and the time.

If what you need is a one-off, a run-of-the-mill capability, or something every business has, do not recruit a permanent team to build it. That is the brewery. You will spend a fortune and a year producing something you could have bought, configured, or assembled in a fraction of the time.

What changed in 2026

The line between "build it" and "don't" has moved, because AI now writes a great deal of the code, and no-code platforms have matured. A non-technical founder today can stand up a working first version, with AI assistance or no-code, that would have needed a small team and a budget in 2023.

That is real, and it is liberating. But mind the trap. AI lowers the cost of the easy 80%, the demos and the standard functions. It does not lower the cost of the hard 20%, the quality you can't see: scale, security, and maintainability. And it does not change the core-or-regulated rule. The right tool still depends on the problem, because AI is not one thing and an LLM is not always the answer.

Your four options

Build an internal team. Best when the technology is core, proprietary, regulated, or long-term. Most control, often cheaper over time, but slow to assemble and demanding to lead.
Use a software agency. Fast, a ready-made team, good for non-core work or overflow. But agencies carry a conflict of interest: they steer you toward the stack they staff, and the A-players in the pitch are not always the people who do your work. Name the individuals in the contract.
Use contractors. Flexible, quick, good as a stop-gap. But low loyalty, weak cultural fit, high cost, and resentment from permanent staff paid less for the same work.
Use no-code or AI tools. Excellent for prototypes, MVPs, and assembling standard functions. The catch is the ceiling: they may not scale, may lock you into a walled garden, and can get expensive as usage grows.

Start with the cheapest thing that proves the point

For most new ideas, the smart first move is the cheapest version that tests whether the idea works at all, a no-code or AI-assisted MVP, not a build. Validate the demand, then graduate to building only the parts that are core and proven. Building first and validating later is how founders lose a year and a budget on something nobody wanted.

You still can't skip the judgement

Whichever option you choose, the decision itself and the quality of what gets built need impartial technical judgement, ideally from someone with no stake in the answer. That is the one thing AI has not changed, and the one place a little outside expertise pays for itself many times over. It is also why building an AI strategy without a CTO in the room is mostly about who you trust to pressure-test the call.

If you are weighing up whether to build, buy, or assemble your way to a product, and want an independent read before you commit, that is exactly the kind of decision I help founders make. Let's talk.

Frequently asked questions

Should I build or buy software for my startup?

Build when the technology is core to your business: proprietary, regulated, complex, or part of a long-term product. Buy, use no-code, or use an agency when it is a one-off or run-of-the-mill capability. You don't need to build a brewery to drink a pint of beer.

Has AI changed the build-vs-buy decision?

Yes. AI now writes much of the code and no-code tools have matured, so a non-technical founder can stand up a viable first version far more cheaply than in 2023. But AI lowers the cost of the easy 80%, not the hard 20% (scale, security, maintainability), and the core-or-regulated rule for building still holds.

What are my options for building software without a team?

No-code and AI-assisted tools for prototypes and MVPs, freelancers or contractors for flexible capacity, or a software agency for speed and a ready-made team. Each has trade-offs; the right one depends on whether the technology is core to your business.

When should I use a no-code tool instead of hiring developers?

Use no-code for prototypes, MVPs, and combining standard functions, when speed and low cost matter more than scale. Hire developers or build a team when the solution is complex, performance-critical, proprietary, or needs to scale and be maintained over the long term.

Do I need a CTO to make the build-vs-buy decision?

Not necessarily a full-time one, but you need impartial technical judgement, ideally from someone with no stake in the answer, because the build-vs-buy call and the quality of execution are where the most expensive mistakes are made.