← Back to All Posts

Strategy

Buy vs Build in the AI Era: The Math Changed, Check Yours

January 28, 2026 2 min read

For fifteen years the advice was automatic: never build what you can rent. Custom software cost six figures and a year; a SaaS subscription cost $99 a month. Easy call.

That math has quietly broken, and most teams haven’t re-run it.

What actually changed

AI-assisted development didn’t make software free, but it collapsed the cost of a specific category: internal tools with well-understood requirements. The client portal, the quoting calculator, the inventory dashboard, the review-collection widget. The things where you’re paying a SaaS vendor $500 to $3,000 a month to use 20% of their feature set.

That category used to cost $80k to build. Today, built by a team that knows its way around modern tooling, it’s often $10–20k. Against a $1,500/month subscription stack, the payback window is under a year, and then you own the asset.

The new decision framework

Rent when:

  • The problem is genuinely hard. Payments infrastructure, email deliverability, video calls: Stripe and friends earn their fees. Don’t build these. Ever.
  • The tool is your system of record for compliance. Accounting and payroll stay rented.
  • You use most of what you pay for. If the fit is good, renting is fine.

Consider building when:

  • You’re paying for a fraction of the features and the fraction you use is simple CRUD with a workflow around it
  • The tool touches your differentiation. If your process is your edge, renting the generic version sands the edge off.
  • Per-seat pricing scales against you. The subscription grows with headcount; owned software doesn’t.
  • You’ve stacked three tools plus Zapier to approximate one workflow

The catch nobody mentions

Owned software needs an owner. Budget roughly 15–20% of build cost annually for upkeep, or have a partner on retainer. “We built it and nobody maintained it” is how you end up worse off than renting.

Run the numbers

Total your SaaS spend on tools where you use a fifth of the features. Multiply by three years. If that number is bigger than a build quote, and in 2026 it often is, the automatic answer isn’t automatic anymore.

Keep Reading

More from the workshop

✦ Strategy

Do You Need an AI Strategy, or Just an Automation?

Two purchases for two different buyers, and picking the wrong one is the expensive mistake. Here's the one-sentence test for telling them apart.

Aug 14, 2026 2 min read
✦ Architecture

Supabase vs Airtable: What to Use When, and Why Supabase Usually Wins

Airtable is a spreadsheet wearing a database costume. Supabase is a database with batteries included. Here's how we decide between them on real client projects.

Jun 18, 2026 2 min read
✦ MVP

The Anti-MVP: Why Modern Founders Should Stop Shipping Fragile Products

The MVP playbook was written when building software was slow and expensive. It isn't anymore. Here's the Anti-MVP approach, production-ready from day one.

May 27, 2026 2 min read

Ready to Move Fast?

Tell us what you need built. No fluff, no pitch decks, just a straight answer on what it takes.

Get in Touch