How does the build-or-buy calculator work?

You answer a handful of questions about maintenance load, control needs, failure risk, integration complexity, and team dependency. The calculator scores your answers and returns one of six result profiles with a clear recommendation and next steps.

What factors should I consider when deciding to build or buy software?

Five factors matter most: how much ongoing maintenance the solution demands, how much control you need over its behavior, how severe the consequences are if it fails, how many integrations it touches, and whether your team can carry it long-term without a single point of failure.

Is this build-or-buy calculator free?

Yes. The calculator is completely free with no account required. You get a personalized result profile and actionable guidance at no cost.

What are the result profiles in the build-or-buy calculator?

There are six profiles: Build Freely, Build With Eyes Open, The Inflection Trap, Buy the Relief, Custom Necessity, and Either Way Hurts. Each profile explains what your score means and offers specific next steps for your situation.

When does it make more sense to build instead of buy?

Building makes sense when you need deep control over behavior, when off-the-shelf tools force painful workarounds, and when your team can absorb the maintenance burden without creating a single-person dependency. If those conditions are not met, buying usually wins on total cost.

Who is the build-or-buy calculator for?

Anyone facing a real build-or-buy decision: founders choosing infrastructure, product leads evaluating vendor tools, engineering managers scoping internal projects, and solo operators deciding where to spend limited time. If you are weighing custom work against an existing solution, this is for you.

Business Application

Build-or-Buy Calculator

Find a detailed explanation below this free calculator.

Build-or-Buy Calculator

Before you build that tool with AI, find out whether future maintenance will make you regret it, or whether buying is actually the expensive choice.

0 of 7 answered

01 What kind of problem is this?

Think about the core problem the tool would solve, not the tool itself.

02 What happens if this tool breaks on a busy day?

03 How many other systems does it need to talk to?

Tap or drag to select

04 How many people will depend on this daily?

Tap or drag to select

05 How much do you want to control exactly how it works?

06 How many other tools or systems are you already maintaining?

07 What's your honest reaction to "you'll need to handle edge cases at 2 AM"?

For general information only. Not professional advice; results are estimates. See the full Disclaimer.

See the thinking before it becomes work. See the work before it's public.

This free test is based on What Survives When Anyone Can Build Anything.

Try my other tools.

Why Most Build-or-Buy Decisions Go Wrong

The usual approach is a spreadsheet comparing license fees to estimated dev hours. That math ignores the expenses that compound quietly: maintenance load, team dependency, and integration brittleness. A year later, the "cheaper" choice is draining time you cannot recover.

This calculator forces you to weigh the factors that matter over the life of the decision, not just the first quarter. You get a result profile that names the tradeoff you are walking into, not a generic "it depends."

What the Calculator Measures

Maintenance load - How much ongoing work the solution creates after launch day.
Control needs - How much behavioral control you need that off-the-shelf tools cannot give you.
Failure risk - How severe the consequences are when the solution breaks or underperforms.
Integration complexity - How many systems the solution touches and how tightly they are coupled.
Team dependency - Whether your team can carry the solution without a bus-factor problem.

Six Profiles, Thousands of Honest Answers

Your answers map to one of six result profiles, but each profile's results are meticulously tailored to their specific answers. There are between 8,000 and 20,000 different results (depending on how you measure differences).

Who This Is For

Founders choosing whether to build core infrastructure or adopt a vendor. Product leads evaluating internal tools against third-party platforms. Engineering managers scoping projects where scope creep hides in maintenance. Solo operators deciding where limited hours go.

If you are staring at a build-or-buy decision and the answer is not obvious, this calculator exists for that moment.

The Thinking Behind the Tool

This calculator is grounded in the argument from What Survives When Anyone Can Build Anything. AI has made building cheap. That changes the math. But cheap to build does not mean cheap to maintain, and the real cost of ownership still sits in the recurring problems you carry after shipping day.

The calculator helps you see where that ongoing cost lands before you commit.

Related Tools

If you are rethinking your product strategy beyond build-or-buy, these free tools cover adjacent decisions:

AI Flywheel Test - Check whether your AI product has a real moat or just a head start.
Revenue Ceiling Audit - Find what is capping your growth and get focused next steps.
Pricing Unit Picker - Three questions to find the right pricing model, from flat subscription to pay-per-result.

Ready to Decide?

Scroll up and take the calculator now. A few clicks, one clear profile, and a next step you can act on today.

Browse Build-or-Buy Calculator result profiles

Each profile explains what a result means and what to do next.

Version: 1.0

Frequently asked questions

1

How does the build-or-buy calculator work?

You answer a handful of questions about maintenance load, control needs, failure risk, integration complexity, and team dependency. The calculator scores your answers and returns one of six result profiles with a clear recommendation and next steps.
2

What factors should I consider when deciding to build or buy software?

Five factors matter most: how much ongoing maintenance the solution demands, how much control you need over its behavior, how severe the consequences are if it fails, how many integrations it touches, and whether your team can carry it long-term without a single point of failure.
3

Is this build-or-buy calculator free?

Yes. The calculator is completely free with no account required. You get a personalized result profile and actionable guidance at no cost.
4

What are the result profiles in the build-or-buy calculator?

There are six profiles: Build Freely, Build With Eyes Open, The Inflection Trap, Buy the Relief, Custom Necessity, and Either Way Hurts. Each profile explains what your score means and offers specific next steps for your situation.
5

When does it make more sense to build instead of buy?

Building makes sense when you need deep control over behavior, when off-the-shelf tools force painful workarounds, and when your team can absorb the maintenance burden without creating a single-person dependency. If those conditions are not met, buying usually wins on total cost.
6

Who is the build-or-buy calculator for?

Anyone facing a real build-or-buy decision: founders choosing infrastructure, product leads evaluating vendor tools, engineering managers scoping internal projects, and solo operators deciding where to spend limited time. If you are weighing custom work against an existing solution, this is for you.