Decision Guide · Checklist · Prompt ·
Building Is Cheap. Owning Isn't.

Build Or Buy?

AI has made it ridiculously cheap to build software. It hasn't made it cheap to own. The moment 30 people depend on the app you vibe coded, you're running a software company. Here are ten reasons to build, ten reasons to buy, and not one of them is "it's cheaper." Then 25 checks to run before you build anything your company can't live without.

How To Use This Page

Deciding on one tool right now? Find its kind in Three Kinds, then paste The Prompt into Claude. Already built it? Go straight to The Checklist and see how you score.

20
Reasons, 10 Each Way
3
Kinds Of Software
25
Checks Before You Build
Building Instead Of Selling?

Your Own CRM Won't Find You Customers.

Building internal tools with AI is fun, and it gets addictive. But a founder rebuilding their CRM instead of calling the people in it is doing Building Theater. It feels productive and it makes $0.

The Solo Founder Lab · Opening Soon

I'm building a place where you learn to build products that work like a real company's on your own, and get them in front of people who pay, with a CTO who's built two seven-figure software companies in your corner.

Lab.exeWaitlist Open

Build What Sells.

  • Live product teardowns. Your app, your landing page and your pricing, reviewed in front of everyone.
  • Weekly CTO office hours. Live, hot-seat style. Bring the build-or-buy call you can't make.
  • Launch Pad. When you launch, the room shows up.
  • The 30-Day Launch Plan. Validate, plan, build and launch, one week at a time. Members only.

Free to join the waitlist. Opens at $49/mo, and the price goes up as seats fill, so first in pays the least.

The Real Question

Building It And Owning It Are Different Jobs

Five years ago this was easy: just buy it. Now I can build a useful internal tool in a weekend, and I think companies should build way more of them. But the weekend is the cheap part. Before you build, ask who's going to own it for the next five years.

  • Who fixes it when it breaks on a Monday morning?
  • Who updates it when Salesforce changes its API?
  • Who makes sure people can't see what they shouldn't?
  • Who has checked the backups actually restore? Having backups and restoring them are different things.
Janet.app · Get Info✣

Every company has that one critical spreadsheet only Janet understands, and God forbid Janet ever quits. AI just gave Janet's spreadsheet a React front end, a database and a login screen. Same problem. Now it has a dashboard.

Was
Janet.xlsx
Built in
One weekend
Users
30, and growing
Owner
Janet
Backup
Nobody
Docs
In Janet's head
Last restore
Never

AI has made building software almost free. It hasn't made running software free.

Three Kinds

Three Different Bets

Build or buy is the wrong first question. First work out which kind of software it is. That decides most of the answer.

Kind 1 · Small Tools✣
Build. Lots.

Internal tools, automations, dashboards, one-off workflows.

AI changed the math here completely. If it breaks, someone's annoyed for an afternoon and does it by hand. Build as many of these as you can.

A quote calculator · a dashboard over your Stripe data · a script that cleans the weekly export

Kind 2 · Your Edge✣
Lean Build

The workflows that make you different.

Off-the-shelf software is built for the average customer. If this is part of why customers pick you, the average won't fit, and you'll fight the tool forever.

Your pricing engine · your onboarding flow · how you schedule the work

Kind 3 · Systems Of Record✣
Lean Buy

The software the company can't run without.

Buy it, unless you'll commit to owning it for years: someone on call, tests, backups you've restored, audits. That's a team, not a weekend.

Accounting · payroll · HR · your main CRM · anything that moves money

The kind isn't about how hard it is to build. It's about what happens when it's down. Tools also move between kinds without anyone deciding: the dashboard becomes the place orders get approved, and now it's a system of record.

10 Reasons To Build

When Building Wins

Skip "it saves on licenses." Everybody knows that one, and it's usually wrong once you count the time. These are the reasons that actually matter.

Build 01

Seat pricing decides who sees the data.

Per-seat pricing quietly decides who gets access. The warehouse lead who needs one report a month doesn't get a login, so they ask someone, or a login gets shared. Build it, and everyone who should see the numbers can.

Ask: Who goes without access today because a seat costs too much?

Build 02

You stop running on someone else's defaults.

Every tool ships with opinions: pipeline stages, field names, the approval flow. Six months in, those defaults are your process. If how you work is part of why customers pick you, don't let a vendor flatten it into the industry average.

Ask: Is this workflow part of why customers choose you?

Build 03

Your AI agents can read it.

An agent is only as useful as the data it can reach. In your own database, it can query anything. In a bought tool, it goes through a rate-limited API, a higher plan or the vendor's own AI add-on, if the vendor lets it in at all.

Ask: Will you want an agent working on this data next year?

Build 04

Nobody can sell it to private equity.

Vendors get acquired, reprice at renewal, retire the plan you're on or shut down. Your own tool can't triple its price or sunset the one feature your team depends on.

Ask: What happens if this vendor doubles its price next year?

Build 05

The buttons stay where they are.

Bought software changes when the vendor decides. A redesign lands on a Tuesday and twenty people can't find the export button. Yours only changes when you change it.

Ask: How much did the last vendor redesign cost your team?

Build 06

The workaround spreadsheet goes away.

Bought tools do 90% of the job. The other 10% lives in a spreadsheet next to it, and that 10% is usually the part that's specific to you. Build it, and the tool does the weird thing too.

Ask: Will there still be a spreadsheet next to the tool you'd buy?

Build 07

You stop upvoting a feature request from 2019.

Need a field, a report or a button? On a vendor's roadmap, that's a forum thread with 400 upvotes and no reply. On yours, it's an afternoon with Claude Code.

Ask: How often will this need to change?

Build 08

You're allowed to throw it away.

A tool for one launch, one audit or one migration can be built in a weekend and deleted in a month. No annual contract, no auto-renew, no 60-day cancellation window. Disposable software didn't make sense before AI. Now it does.

Ask: Do you need this for months, or for years?

Build 09

The second one is half the work.

Your first internal tool means setting up hosting, login, a database and deploys. The second one reuses all of it. Building is a skill your team gets better at. Buying never teaches it.

Ask: Is this your first internal tool, or your fifth?

Build 10

One less company holding your data.

Every tool you buy is another company storing your customer list, another security review to fill in, and another breach email you might get one day. Build it, and the data stays where the rest of your data already lives.

Ask: Would you rather trust this vendor's security, or your own?

10 Reasons To Buy

When Buying Wins

Not maintenance, scaling or "it might break." These are the costs that don't show up until year two, and they're the ones that hurt.

Buy 01

The builder leaves.

Your ops manager vibe codes a great tool, then takes a new job. Nobody knows how it works or how to change it, and the AI that wrote it doesn't remember either. A vendor's team doesn't hand in its notice.

Ask: If the builder left tomorrow, who could change it?

Buy 02

The builder can't leave.

The flip side: they stay, and they're stuck. They can't take the promotion, move teams or go off-grid for two weeks, because they're the only one who can fix it. You've handcuffed your best operator to a side project.

Ask: Could you promote the builder away from this tool?

Buy 03

You're the help desk now.

Someone can't log in. Someone deleted a row. Someone can't find last month's report. None of those are bugs, and all of them are yours. A vendor has a support team, help docs and a status page.

Ask: Who answers "it's not working" at 9am on a Monday?

Buy 04

Other companies break it on their schedule.

Salesforce retires an API version. Google changes a permission. Stripe changes a webhook. Your app breaks on a Tuesday because someone else shipped. Every integration is a relationship you now have to keep up.

Ask: How many outside systems does it connect to?

Buy 05

Nobody re-tests yesterday's features.

AI makes changes cheap, so you make lots of them. Who checks that this week's feature didn't quietly break last month's invoice export? It's worst anywhere money moves.

Ask: Does it touch money, payroll or anything a customer sees?

Buy 06

The vendor already hit everyone else's edge cases.

Time zones, partial refunds, a customer in two countries, a tax rule that changed in January. A mature vendor has been bitten by all of them, with thousands of customers paying for the fixes. Your tool meets each one for the first time, live.

Ask: Have a thousand other companies already solved this exact problem?

Buy 07

Offboarding becomes a security problem.

When someone leaves, a bought tool tied to your Google or Microsoft login shuts them out automatically. Yours has a users table someone has to remember. And the integrations often run on the builder's own account, so they die the day it's switched off.

Ask: When someone leaves, does their access leave with them?

Buy 08

Your biggest customer's security questionnaire now covers it.

Big customers and auditors ask about every system that touches their data: who has access, where the audit log is, how long you keep it, how you delete it. Your weekend project now needs answers to all of that.

Ask: Will customer data ever go into it?

Buy 09

Every department builds its own.

Once building is easy, sales builds a CRM, ops builds a CRM and customer success builds a CRM. Now there are three, none of them agree, and nobody knows which one is right.

Ask: Has someone in another team already built a version of this?

Buy 10

It shows up in due diligence.

When you raise money or sell the company, buyers ask what you run on, and a homegrown system of record goes on their risk list. And when you outgrow it, getting the data out in a shape another tool understands is all on you.

Ask: Could you move everything to another tool in a day?

The Third Option

Buy The Core. Build The Edges.

Most of the time the answer is both. Buy the system of record and keep the data in it. Then build the small tools around it with AI. When something you built breaks, nothing important is lost, because the data never lived there.

Money✣
BuyQuickBooks or XeroBuildThe cash dashboard your team actually reads

The accountant gets the system they know. You get the view you want.

Sales✣
BuyHubSpot or SalesforceBuildLead scoring tuned to your best customers

Your edge lives in the scoring, not in storing contacts.

People✣
BuyGusto or RipplingBuildThe onboarding bot that sets up a new hire's accounts

Payroll law is their problem. Your first-day checklist is yours.

The Checklist

25 Checks Before Anyone Depends On It

Run this before a small tool turns into something the company can't run without. Tick what's true today, not what you plan to do.

0 / 25

Not Ready To Own ItKeep it a small tool that nobody's job depends on, or buy something.

01 · Ownership5

Who owns it.

  • Two people are named as owners, and the second one has shipped a change on their own.
  • Someone has agreed to own it for the next few years, not just build it.
  • There's a one-page "how this works" a new hire could follow.
  • There's one place to report problems, and someone answers it.
  • Error alerts go to a channel people read, not the builder's inbox.
02 · Accounts5

Who it belongs to.

  • The code lives in the company's GitHub, not someone's personal account.
  • Hosting, domain and database are on company accounts, paid with a company card.
  • Every API token belongs to a shared service account, not the person who built it.
  • Login goes through your company Google or Microsoft account, so leaving removes access.
  • Hosting, API and AI costs have a monthly budget and an alert.
03 · Data5

Where the truth lives.

  • Each piece of data has one source of truth, and everyone knows where it is.
  • You've restored a backup into a fresh database, and the app ran on it.
  • You can export everything to CSV in one go.
  • You've logged in as a normal user and checked they only see what they should.
  • Anything touching money or customer data records who changed what, and when.
04 · Change5

How it changes safely.

  • Tests cover every path where money or customer data moves.
  • Changes go to a test copy before the real one.
  • Every outside system it connects to is written down, with who owns that account.
  • Someone gets the security alerts for the packages it uses, and acts on them.
  • If it's down for a day, the team knows the manual way to do the job.
05 · The Exit5

How you'd get out.

  • You know which of the three kinds it is, and you've written it down.
  • You've priced the buy option honestly, including the time to set it up.
  • You've written a tripwire: the point you'd switch to buying, like 50 users, payroll or a SOC 2 audit.
  • There's a review date six months out: keep it, rebuild it or replace it.
  • You know which tool you'd move to, and you've checked it can import your data.
The Prompt

Make The Call With Claude

Paste this into Claude, ChatGPT or whatever you use. It interviews you first, then gives you a verdict and, if you're building, an ownership plan.

Build.Or.Buy.Prompt
I'm deciding whether to build or buy [THE TOOL, e.g. a CRM for our sales team]. Interview me before you recommend anything.

Ask one question at a time and wait for my answer. Cover:
- What it does, who uses it, and how many people will depend on it
- What happens if it's down for an hour, a day, a week
- Whether it touches money, payroll, customer data or anything regulated
- Which outside systems it connects to
- Who would build it, who would own it, and what happens if they leave
- What we'd buy instead, what it costs, and what it can't do for us

Then give me:
1. The kind of software it is (a small tool, a workflow that's our edge, or a system of record) and why.
2. For each of these 20 points, one line on whether it pushes us toward build or buy:
   Build: seat pricing limits who sees the data; we'd run on a vendor's defaults; our AI agents need the data; the vendor could reprice, be sold or shut down; forced redesigns; the workaround spreadsheet; waiting on a vendor's roadmap; we only need it for a while; we've built tools before; one less company holding our data.
   Buy: the builder leaves; the builder can never move on; we become the help desk; outside APIs change; nobody re-tests old features; vendors have solved the edge cases; offboarding; customer security reviews and audits; other teams building their own; due diligence and getting the data out.
3. A recommendation: build, buy, or buy the core and build around it.
4. If it's build: a one-page ownership plan with two named owners, company accounts, backups we test, tests on anything touching money, a tripwire for when we'd switch to buying, and a review date.

Be blunt. If we should buy it, say so.
Pink Means Edit Me

Swap in the tool you're deciding on. Leave the rest alone.

Bring The Builder

Answer the questions with whoever would build it and whoever would use it most. They'll disagree, and that's the useful part.

Then Tick The Boxes

If it says build, work through The Checklist before more than a handful of people depend on it.

One More Thing

Tools Are The Easy Part.

Anybody can build software now. Not everybody can build a business.

The Solo Founder Lab

Reading about tools is a great way to feel busy. The Lab is for Founders who'd rather get customers: weekly office hours with a CTO who's built two seven-figure software companies, and a room of other Founders who care whether anybody buys what you're making.

Lab.exe✣

Less Theater. More Customers.

Want my 30-Day Launch Plan? It's for Lab members only: validate, plan, build and launch, one week at a time.

See The Solo Founder Lab ▶