Skip to content
← Back to Insights
AI Strategy

Build or Buy Software Now That Coding Agents Exist

Coding agents cut the cost of writing custom software. Running it costs the same. How to compare build and buy over two years, and what to ask first.

Build or Buy Software Now That Coding Agents Exist

Coding agents made the first version of custom software much cheaper to write. They did little for the cost of running it for two years. Before you build, compare the full two-year cost of both options and name the person who will own the tool in year two. If nobody can, buy.

Not long ago, the build option for a quoting tool, a customer portal, or an approval workflow often took months of developer time. Now a capable developer with an AI coding agent can often produce a working first version in days. That changes the math for some decisions and leaves most of the math where it was.

What changed: building got cheaper

Companies are acting on it. In McKinsey's 2026 State of AI survey, 32% of respondents said their organization had decided against buying "one or more software products or features because they could be built internally with agentic coding tools." Among the companies McKinsey counts as AI high performers, nearly half said so, compared with 31% of everyone else (McKinsey, The State of AI in 2026, 1,719 respondents, fielded May to June 2026). The figure is also on our mid-market AI statistics page.

For a mid-market company, that opens real options. A tool that fits your process exactly, with no per-seat fees and no features you don't use, is now within reach for jobs that used to justify only a subscription.

What didn't change: running it

The first version is the smallest part of a software tool's life. One experienced developer put it plainly in a forum thread about replacing an internal app with a SaaS product: "Remember that the majority of software cost comes from maintenance, not build." And: "Even if you think you're 80% there now, you've probably only put in 1/3 of the effort you'll need to run this thing over the next 2 years." (r/ExperiencedDevs, practitioner discussion)

Running a tool means:

  • Changes. Your process moves, a customer asks for a new field, finance wants a new report.
  • Security and dependency updates. The libraries underneath the tool need patching on their schedule, not yours.
  • Integrations. When your ERP, CRM, or email provider changes its API, the connection breaks until someone fixes it.
  • Hosting and accounts. Someone pays for them, watches them, and renews them.
  • Questions. People ask how it works, report problems, and need access.

Coding agents help with each of these, but someone still has to notice the problem, decide what to change, review the change, and ship it. That someone is the real cost.

The two-year comparison

Put both options on one page, line by line, over two years:

Cost line Build Buy
First version Development or a build partner, now faster with coding agents Setup and configuration
Licenses Hosting and AI usage, usually small Subscription, often per seat, with renewal increases
Changes Your developer or partner, every time the process moves Limited to what the product allows
Updates and security Your responsibility The vendor's
Integrations You fix them when connected systems change Covered if the vendor supports your systems, otherwise yours
Gaps None by design Workarounds, spreadsheets, and manual steps around what the product doesn't do
Ownership A named person inside the company An admin who manages the vendor

Illustrative example. Numbers are hypothetical. A built approval tool needs an owner for about 4 hours a week, two small changes a month at 6 hours each, and quarterly updates at 8 hours. That comes to roughly 380 hours a year. A purchased tool needs about 2 hours a week of administration, but three people each spend 20 minutes a day on a workaround for a step it doesn't support, across about 250 working days. That comes to roughly 350 hours a year, plus the subscription. Neither option is free to run. The comparison only works when both columns are counted.

The year-two test: name the owner

Before you build, write down the name of the person who will own the tool in year two. Owning it means they know how it works, decide what changes, and answer when it breaks. If that person exists and has the time, building is a real option. If the honest answer is "the developer who built it, if they're still here," buy, or plan for a partner to own it with you.

Without an owner, custom software follows a familiar pattern. The tool works on launch day, then the person who built it moves on, and a year later nobody can change it safely.

When buying wins, and when building wins

Buy when:

  • The process is standard across companies, such as accounting, payroll, or basic CRM
  • A product covers most of what you need without heavy workarounds
  • Nobody inside can own a custom tool

Build when:

  • The process is how you win, and a generic product would flatten it
  • You'd be paying for many seats of a large product to use a small part of it
  • The tool sits between your systems and needs to follow your rules exactly
  • You have, or can arrange, an owner for year two

Most companies end up with both. Buy the standard system, then build the thin layer around it: the integration, the approval step, the report the product doesn't produce. That keeps the custom part small enough to own.

A caution for AI tools specifically

AI tools are a special case. MIT's Project NANDA found that external partnerships with customized AI tools reached deployment about 67% of the time, compared with about 33% for tools built internally (MIT NANDA, The GenAI Divide, 2025). The authors flag the limits: the numbers are self-reported and come from interviews with 52 organizations. The direction is still worth taking seriously. AI tools fail on integration, data, and the supervision they need after launch, which our article on the oversight cost of AI agents covers. Those are exactly the parts a first version skips.

Questions to settle before you decide

  1. What does each option cost over two years, counting people's time on both sides?
  2. Who owns the tool in year two, and how many hours a week do they have?
  3. Which parts of the process are standard, and which are how you win?
  4. What happens to your data and your code if you change vendors or partners?
  5. What is the smallest custom piece that would close the gap around a product you already have?

For a broader view of the build, buy, or hire choice for AI projects, see Build vs. Buy AI.

How we approach it

When we build custom software, the work starts with a two-week Scoping Sprint that turns your requirements into an architecture and a phased, fixed-price proposal. Each build phase runs 6 weeks or less and ends with written acceptance tests on your data. The code lives in your repositories and your accounts, so you own it. We ask for a named internal owner with about 4 hours a week, which is the year-two test applied from the start. After 30 days of defect fixes per phase, Dooder Operate can run and improve what we ship. More on the custom software page.

Common questions

Can our IT person build internal tools with AI coding agents now? Often, yes, for a first version. The question is whether they have the time to own it for two years, including changes, updates, and integration fixes.

Is custom software cheaper than SaaS now? The first version is cheaper than it was. Over two years, it depends on how often the process changes and who owns the tool. Count both columns.

What should we build first? The thin layer around a system you already have, such as an integration, an approval step, or a report. It's small enough to own and delivers value quickly.

Next step

If you're weighing a build against a subscription, book a 30-minute call. We'll look at the process, the two-year cost on both sides, and who would own it. Work is a fixed price for a written scope, quoted after the call. How we work explains the steps.

Get new articles by email.

Practical notes on making AI pay off in mid-market operations. No spam. Reply to any email to stop.

Related reading