When should you build custom software instead of buying it?

A glowing blue holographic balance scale compares buying software, represented by a shopping cart, with building custom software, represented by a code icon, in a small business workspace.

Key takeaways

  • A custom build's payback period in months equals its upfront cost divided by net monthly savings: canceled subscription costs plus the value of time saved, minus ongoing operating costs.

  • Per-seat SaaS pricing can turn a tool that looks affordable at five users into a five-figure annual cost at 20 employees.

  • Bolt.new, through Bolt Cloud, bundles database, authentication, and hosting into the build itself, which can shorten the payback window for a custom tool.

  • Real businesses have already replaced paid subscriptions with custom-built tools, cutting annual software costs by tens of thousands of dollars.

  • Count the hours a custom build saves, including through partial automation, and distinguish the value of freed staff time from cash savings.

Add up the monthly bills: customer relationship management (CRM), scheduling tool, invoicing platform, maybe a separate form builder and a project tracker on top. 

For many small business owners and ops leads, that stack adds up fast and still doesn't quite match how the business runs. Someone is always exporting a CSV to bridge two tools or maintaining a spreadsheet that should have been automated a year ago.

Building custom software is the fix for that mismatch. It means designing and developing a working application around one business's exact workflow instead of adapting the workflow to an off-the-shelf tool built for a broad market of buyers.

Whether that trade makes financial sense depends on arithmetic. This piece gives you a payback-period formula to run with your own numbers:

  • what you’re spending now

  • what a build would cost

  • how long before the savings cover it

If the math works, you'll know. If it doesn't, you'll know that too.

Bolt.new as one build option

Bolt.new turns a text description into a working, deployable application, which can cut the setup labor you'd otherwise include in a custom build estimate. The development environment runs in your browser tab through WebContainers, so there's no local setup or remote development environment to provision.

Bolt Agent writes the app, WebContainers run it in the browser, and Bolt Cloud publishes it; a simple first version can come together in one sitting. You can try a first version for $0.

To estimate your builder costs, consider the plan price and included usage. Bolt.new measures AI usage in tokens; the amount your build needs affects which plan or additional usage you’ll pay for.

  • Free: $0 with one million tokens per month and a 300,000 daily cap

  • Pro: $25 per month, starting at ten million tokens per month with no daily cap

Visual edits, available on every plan, let you change text and styling by clicking an element instead of re-prompting.

Agencies, freelancers, and other AI builders are all valid paths to the same outcome. A later section compares those options on upfront cost and time to first savings.

The payback-period formula for your build

Your payback period is your upfront build and transition costs divided by your net monthly savings. Net monthly savings is what you stop paying in subscriptions plus the dollar value of staff hours you recover, minus what the tool costs to run each month.

Three inputs drive that number, and each gets its own section below:

  • the subscriptions you cancel

  • the manual work you eliminate

  • what the build costs upfront and ongoing

If you want to go deeper on whether a custom tool makes sense before running the math, our breakdown of internal tool builders versus custom dev work offers a starting point.

The subscription cost you kill

Your subscription-savings input is the exact monthly total of every tool and paid seat you can cancel once the replacement works.

Start by listing every subscription the custom build will replace. CRM, scheduling, invoicing, and reporting tools often stack without anyone adding them up. Pull the actual charge for each, including per-seat costs multiplied by the seats you hold. If a subscription bills annually, divide by 12 to get the monthly equivalent. 

A tool at $50 per seat per month costs $3,000 a year for five people and $12,000 for 20.

Then total them. That number is your savings input for the payback formula.

Software as a service (SaaS) is subscription software accessed online. Zylo's 2025 SaaS Management Index found average SaaS spending reached $4,830 per employee per year, up 21.9%.

If you're not sure which tools overlap or which charges are redundant, our breakdown of the small business software problem can help you sort that out first.

The hours you get back

Your time-savings input is the monthly value of the staff hours the custom build removes from documented manual work. Before you estimate anything, log the weekly hours your team spends on the workarounds the build will change:

  • duplicate data entry

  • spreadsheet reconciliation

  • exporting between tools

Then subtract the hours that will remain after the build. If a task currently takes five hours and drops to two, count three recovered hours. Partial automation counts, because the full task doesn't have to disappear for the time to have value.

Multiply those recovered weekly hours by the employee’s hourly cost, including wages, employer taxes, and benefits, or by a contractor rate you’ve paid. Then multiply by 4.33, the average number of weeks per month, to get a monthly value.

Label the result carefully. If reclaimed hours let you reduce overtime or contractor spend, that's a cash saving and goes directly into your formula alongside subscription cancellations. If the same salaried employee now applies those hours elsewhere, that's capacity value. It's worth counting, but it won't show up as cash. 

Both belong in your payback calculation, in separate rows so you can see what you're comparing.

The build cost you pay

Upfront build and transition costs go above the division line. Monthly operating costs reduce what you save each month. Keep them separate, or the math breaks. If you build with an AI builder like Bolt.new, the plan price goes in your monthly operating costs ($25 per month for Pro). Multiply the hours you and your team spend building, testing, launching, migrating data, and training by the appropriate hourly labor cost, then add that amount to your upfront total.

Your upfront total includes:

  • any one-time provider fees or builder costs

  • the hours you spend building, testing, and launching

  • migration and training time

Your monthly operating costs (hosting, maintenance, and any ongoing usage charges) come off the savings side. If the replacement costs $200 per month to run, that reduces your net monthly savings before you divide anything.

Example: $6,000 in upfront costs divided by ($400 in monthly subscription savings + $300 in monthly staff-time value − $200 in monthly operating costs) equals a 12-month payback period. 

Swap in your own quote or plan price to get your payback period. If net monthly savings land at zero or below, no payback period exists under those assumptions.

What custom dev used to cost

Up until the last couple of years, a small business without in-house engineering had to pay a dev shop or freelancer for every hour of work before the tool produced a single dollar of savings. 

Clutch’s review data puts the average custom software project at $132,480 and about 13 months, though most reviewed projects fall between $10,000 and $49,999. A single-workflow tool for a small team can come in well below that average, but the work still broke into billable phases:

  • discovery and scoping to define what the tool needed to do

  • authentication setup so the right people could access it

  • database and hosting configuration to store and serve data reliably

  • quality assurance (QA) to catch what the build broke before you went live

Each phase added time, and discovery alone could stretch across weeks. Backend setup and QA extended timelines further, often pushing the total build into months before your team touched a working tool.

That cost structure has changed.

What building it costs today

AI builders give you a subscription- or usage-based starting point, which lowers the financial commitment needed to begin. Where an agency or freelancer charges for development work, an AI builder lets you start building and pay as you go.

Bolt.new’s Pro plan starts at $25 per month. Your total cost also includes the value of your build time and any additional usage, hosting, or maintenance costs.

The structural change behind that lower floor is bundled infrastructure. Many AI builders now include the database, authentication, and hosting in the build itself, so you don’t pay for a separate backend phase before you see a working tool. Hosting and maintenance still cost money after launch, so carry them as monthly operating costs in your formula.

For examples of custom CRMs, client portals, and ops dashboards, see what small business owners are building.

Two businesses that built, not bought

ClickUp and Harmonic both removed a paid software cost by building a replacement in-house, according to Retool’s customer stories. Retool’s 2026 Build vs. Buy Shift Report found that 35% of surveyed teams had already replaced at least one SaaS subscription with a custom-built tool.

ClickUp's shift away from paid tools

ClickUp’s order form reviewer saves $200,000 per year in off-the-shelf automation software, according to Retool’s customer story on ClickUp. The order form reviewer was one of several tools ClickUp’s engineers and analysts built with Retool and connected to its existing systems.

In the payback-period formula, this example sits in the subscription-savings column. That saving is cash, so it’s predictable and easy to model. Once you cancel the contract, it repeats every month.

Harmonic's move to a built system

Harmonic removed a third-party tool that cost roughly $20,000 per year by building a replacement with Retool Workflows. The built system processed sales calls and helped generate tickets, covering a narrower but more targeted function than ClickUp’s broader collection of sales and customer support tools.

Both cases show subscription costs removed through a custom build, but the published figures don’t establish total build and ongoing costs, so they aren’t enough to calculate a break-even date.

If you’re paying for a tool that does one job, Harmonic’s example is the closer comparison. Its $20,000 a year works out to about $1,667 a month in savings. What you spend to build and maintain a replacement determines how long it takes to recover that cost.

Comparing agencies, freelancers, and AI builders

The path you pick (agency, freelancer, or AI builder) changes your upfront and monthly operating costs, plus the timeline for a working product. Those inputs change across build paths, while the subscriptions you cancel stay the same for an equivalent replacement.

The right path depends on how much technical work you want to take on and how fast you need a working tool. The table compares agencies, freelancers, and AI builders like Bolt.new on the factors that change your payback math.

Evaluation factor

Agencies

Freelancers

AI builders

Cost structure

Fixed project quotes, typically the highest total cost

Hourly or per-project rates, lower overhead than agencies

Subscription pricing or usage charges; no project quote or contract needed

Backend infrastructure

Sets up hosting, database, and authentication within project scope

Builds backend infrastructure individually; scope varies by contractor

Bolt Cloud bundles database and hosting; no separate vendor needed

Time to working product

Multi-week to multi-month, following a structured project timeline

Typically faster than agencies, dependent on individual availability

A simple first version can take one session; testing, integrations, and migration add time before switching.

Who can drive the build

Client directs scope; agency developers write the code

Client directs scope; freelancer writes the code

A non-technical owner or lead can build directly

Backend setup is where the paths diverge most. An agency or freelancer typically handles server configuration, database provisioning, and deployment as billable work, which adds to your upfront cost but leaves little for you to manage. 

With an AI builder, the platform handles infrastructure, but you're still responsible for the build itself: writing prompts, reviewing output, and iterating. That's work your team carries, and it belongs in your build-cost estimate alongside any subscription fee.

The formula gives you the number of months needed to recover your upfront costs once the replacement is in use and the savings begin. To estimate the recovery date from project start, add the build and transition period. A three-month build followed by a 12-month payback period means recovering your upfront costs about 15 months after the project starts.

Making the build-or-buy call

If your subscription and time savings would recover the build cost within a timeframe your business can accept, the calculation supports building. If they wouldn’t, staying on the subscription remains reasonable.

Agencies, freelancers, and AI builders like Bolt.new are different paths into the same calculation. The clearest next step is to pick one tool you’re paying for monthly and run the payback math against a realistic build cost. 

If the payback window works, start building on the Free plan and test the replacement against your own numbers before you cancel anything.

Start building today

FAQ

Frequently asked questions

Most SaaS tools let you export records as a CSV or through an API, which becomes the starting dataset for your new build's database. Budget time to clean and map that data before import, since mismatched fields can delay a migration. A tool built with a bundled database, like Bolt.new's, skips the step of provisioning separate storage before you can load your old records in.

Running both systems for a short overlap period, often one billing cycle, gives your team a fallback if the new build needs adjustments. This overlap adds a temporary cost, since you're paying for both at once, so keep it short and deliberate. Once the custom tool reliably handles the tasks your business needs, cancel the old subscription when its contract allows. Count subscription savings from the date those charges stop.

Yes. Use the subscriptions your business can cancel, the time it can save, and the upfront and ongoing costs of the replacement. A five-person team paying for three overlapping tools can still clear a build cost within a year if the workaround eats enough staff hours. The formula doesn't change with headcount, only the dollar inputs you plug into it.

If your payback math never crosses the build cost within a reasonable window, staying on the subscription remains a legitimate choice. That result usually means the tool you're paying for already fits your workflow closely enough that a custom version wouldn't save meaningful time or money. Run the formula again if your team grows or the subscription's per-seat price rises, since both shift the inputs toward building.

Ongoing maintenance, bug fixes, feature updates, and hosting still need an owner after a custom tool ships, so budget for that before you build. Owners can handle small updates with the same AI builder that created the tool. For larger changes, a freelancer or agency familiar with the build can take over specific fixes without owning the whole project.

You want more?
Build smarter, every week

The sharpest thinking on building with AI - product drops, engineering deep-dives, and tips that ship.