The short answer
Custom software for a small business can cost anywhere from a few tens of thousands of dollars to several hundred thousand, and the build is only part of what you pay. The published numbers vary widely because "custom software" covers everything from a single internal form to a multi-location operating system for a medical group.
This guide walks through what actually drives the price, what reputable published sources report, what it costs to keep software running after launch, and how a one-time build compares with a subscription over three years. Every figure below links to its source. Where we use examples, they are clearly marked as illustrative.
If you would rather plug in your own numbers as you read, the software cost calculator runs the same comparison for your business.
What drives the cost of custom software
Five factors account for most of the difference between a modest quote and a large one.
Scope. The number of workflows, screens, roles, and rules is the single biggest driver. A scheduling tool for one front desk is a different project from a platform that handles intake, scheduling, billing, staff management, and reporting. SOLTECH's cost guide lists software size and complexity as the first two of its seven cost factors, alongside design, integrations, data migration, developer location, and AI-assisted development.
Integrations. Every system the software has to talk to, such as a payment processor, an EHR, an accounting package, or a payroll provider, adds design, build, and testing work. Keyhole Software's 2026 benchmarks note that connecting to legacy systems, ERPs, or third-party APIs often requires additional testing cycles.
Data migration. Years of customer records, job histories, invoices, or patient files rarely move cleanly. They have to be mapped, cleaned, and checked. SOLTECH treats data migration as its own cost factor because it typically requires custom scripts.
Compliance. If you handle protected health information, the software and the people who build and host it take on specific obligations. The HIPAA Security Rule requires an "accurate and thorough assessment" of risks to electronic health information, and requires covered entities to obtain satisfactory assurances before a business associate handles that information on their behalf (45 CFR § 164.308, via Cornell LII). Keyhole estimates that HIPAA, GDPR, SOC 2, and PCI-DSS requirements add 2 to 6 weeks for audit preparation and certification. That time is billed like any other.
Users and locations. More locations usually mean more permissions, more reporting views, more edge cases, and more data. A system that works for one office often needs real design work before it works for three.
A sixth factor sits underneath all of these: who builds it and where. Clutch's pricing data shows typical hourly rates of $50 to $99 in the United States and $100 to $149 in Canada and Australia, with lower brackets in other regions. SOLTECH cites $50 to $250+ per hour for US-based developers. Rate alone does not predict total cost. A cheaper team that needs more hours, or more rework, can end up costing more.
What published sources say a custom build costs
There is no single authoritative price list, so it helps to look at several sources side by side and pay attention to how each one gathers its data.
| Source | What it reports | Basis |
|---|---|---|
| Clutch | Most reviewed projects fall between $10,000 and $49,999; the average project cost is $132,480, with an average timeline of about 13 months | Verified client reviews on Clutch (updated September 2026) |
| Keyhole Software | Simple/MVP: $40,000–$120,000 (2–4 months). Medium: $120,000–$300,000 (4–8 months). High complexity: $300,000–$1,000,000+ (8–18+ months) | 200+ verified projects analyzed, October 2024–January 2026 |
| SOLTECH | Small business software: $75,000–$100,000 base estimate. Small apps: $100,000–$200,000. Medium: $200,000–$400,000 | The firm's own project experience; no published data model |
A few things are worth noticing.
First, the ranges overlap but do not agree. That is normal. Each source defines "small" and "medium" differently, and each draws on a different mix of clients and regions.
Second, Clutch's typical project and its average are far apart. Most reviewed projects land in the lowest bracket, but a smaller number of large, long engagements pull the average above $130,000. If a vendor quotes you "the average," ask which average.
Third, none of these figures includes what happens after launch. That is where many budgets go wrong.
Ongoing costs: maintenance and hosting
Software is not finished when it launches. Operating systems update, browsers change, third-party APIs are versioned and retired, security issues are found, and your business changes what it needs.
Maintenance. A commonly cited rule of thumb is that annual maintenance runs 15–20% of the original development cost. Keyhole's benchmarks put the range slightly wider, at 15–25% of initial development cost per year, which works out to $30,000 to $50,000 a year on a $200,000 project. Over a system's full life, maintenance often becomes the larger share of total cost: CodeStringers summarizes research that places maintenance at 67% to over 90% of lifecycle cost, depending on the study.
Maintenance is not only bug fixes. It typically includes corrective work (fixing defects), adaptive work (keeping up with platform, API, and regulatory changes), perfective work (improvements and new features), and preventive work (refactoring and hardening).
Hosting. For a small business application, hosting itself is usually modest. One 2026 breakdown puts a small AWS-hosted business app, meaning a small server, a small managed database, and minimal storage, at roughly $40–$150 a month, and says most small-to-medium business apps fall between $100 and $500 a month. Another places small applications at $50 to $500 a month. Compliance requirements, backups, monitoring, and higher availability push that number up.
The hosting bill is rarely the problem. The problem is that someone has to own the hosting: patching, monitoring, backups, and responding when something breaks at 7 a.m. on a Monday.
The subscription model: a different way to pay for the same thing
The traditional path is to pay a large project fee, launch, then either sign a separate maintenance contract or hire someone to keep the system running. You own the risk of the build and the cost of every change afterward.
A subscription bundles those pieces into one monthly price. At Localhost Labs, for example, one custom platform, including the build, hosting, maintenance, support, data migration, and onboarding, is billed month-to-month: Starter at $497 a month for one location, Growth at $1,497 a month for up to three locations, and Custom from $2,997 a month. The full breakdown is on the pricing page, and the custom software subscription page explains how the model works.
The trade-offs are real in both directions:
- A one-time build can make sense if you have capital available, an in-house technical owner, and a clear, stable scope. You pay more up front, and you carry maintenance separately.
- A subscription spreads the cost, keeps the same team responsible for the system after launch, and lets you stop paying if it stops earning its place. You pay for as long as you use it, so over a long enough horizon the cumulative cost keeps growing.
A three-year cost comparison
The table below compares a one-time build with a subscription over three years. Every input is an illustrative assumption, chosen to sit inside the published ranges above. It is not a quote, and your numbers will differ.
Assumptions for the one-time build:
- Build cost: $120,000, the boundary between Keyhole's simple and medium tiers and within SOLTECH's small-app range.
- Maintenance: 15% of build cost per year (low end of Keyhole's range) in a lower-cost scenario, and 25% (high end) in a higher-cost scenario, charged in years 2 and 3 after launch.
- Hosting: $300 a month ($3,600 a year), within the typical $100–$500 range, for all three years.
The math:
- Year 1: $120,000 build + $3,600 hosting = $123,600
- Years 2 and 3 at 15%: $18,000 maintenance + $3,600 hosting = $21,600 per year
- Years 2 and 3 at 25%: $30,000 maintenance + $3,600 hosting = $33,600 per year
For the subscription, the monthly price is multiplied by 36 months. Build, hosting, maintenance, and migration are included in the price.
| Illustrative scenario | Year 1 | Year 2 | Year 3 | 3-year total |
|---|---|---|---|---|
| One-time build, 15% maintenance | $123,600 | $21,600 | $21,600 | $166,800 |
| One-time build, 25% maintenance | $123,600 | $33,600 | $33,600 | $190,800 |
| Subscription: Starter ($497 × 12) | $5,964 | $5,964 | $5,964 | $17,892 |
| Subscription: Growth ($1,497 × 12) | $17,964 | $17,964 | $17,964 | $53,892 |
| Subscription: Custom (from $2,997 × 12) | $35,964 | $35,964 | $35,964 | from $107,892 |
Two honest caveats. A build you own outright has no monthly fee after year 3, while a subscription continues for as long as you use it, so the gap narrows over a longer horizon. And the scopes may not be identical: a $120,000 build and a Starter plan are not necessarily the same amount of software. The useful comparison is between options that solve the same problem for your business. That is what the cost calculator is for.
How to budget for custom software
A realistic budget has four lines, not one.
- Build or setup. The project fee for a one-time build, or the first months of a subscription.
- Migration and onboarding. Moving data out of your current tools and getting staff comfortable. Confirm whether this is included or billed separately.
- Ongoing maintenance and hosting. For a one-time build, plan on the 15–25% annual range cited above, plus hosting. For a subscription, confirm what the monthly fee covers.
- Change over time. Your business will change. New locations, new services, new regulations. Budget for the software to change with it.
It also helps to budget against what you already spend. Add up every tool subscription, every connector like Zapier, and a fair estimate of staff time spent re-entering data between systems. That number is your real starting point, and it is often higher than owners expect. If you are still deciding whether to build at all, our guide to custom software vs off-the-shelf SaaS covers when staying on existing tools is the better call.
Questions to ask any software vendor
Whether you hire an agency, a freelancer, or a subscription provider, these questions separate a considered proposal from a guess.
On price
- What exactly is included in the quote, and what is billed separately? Ask specifically about data migration, hosting, training, and post-launch fixes.
- How are changes priced after launch?
- What do you estimate annual maintenance will cost, and what does it cover?
On scope and timeline
- Which of our current tools will this replace, and which will stay?
- Which integrations are included, and how do you handle a third-party API change?
- What is the timeline to a working system our staff can use?
On compliance and security
- If we handle health information, will you sign a business associate agreement, and how do you support our risk analysis?
- Where is our data hosted, and how is it backed up?
On ownership and exit
- Who owns the code and the data? What does the contract say, specifically?
- If we stop working together, how do we get our data out, and in what format?
- Is there a minimum term or cancellation fee?
Ownership deserves a careful read. Under US copyright law, work commissioned from an outside party is a "work made for hire" only in nine listed categories and only with a signed written agreement, and custom software is not one of those categories (U.S. Copyright Office, Circular 30). In practice that means the contract language decides who owns what. Have an attorney review it.
The bottom line
Published guides put a small business custom build anywhere from tens of thousands to a few hundred thousand dollars, with maintenance commonly cited at 15–25% of that each year. Those numbers vary widely because projects do. The more useful question is what it costs to solve your specific problem over the next three years, including everything that happens after launch.
If you would like to see those numbers for your own business, start with the software cost calculator, or book a call and we will walk through your current tools and what a unified platform would replace.