Here’s the honest small-business number most cost guides bury under enterprise figures: a focused custom build starts around $25K for a tight MVP and lands at $75K to $100K for a typical production solution. Enterprise systems do pass $1M, but that headline isn’t your headline. If you run a 20-person company and someone quotes you “$200K to $2M,” they’re pricing a problem you don’t have.
So why is the range so wide? Because “custom software” describes a $20K internal tool and a $2M platform with equal accuracy. The price isn’t set by what you call it. It’s set by scope, the rates of the people building it, and how many other systems your software has to talk to. Get specific about those three and the number stops being a mystery.
We’re gmware, a custom software development firm with our US office in Austin, TX and engineering centers in Bangalore and Mohali, India. We quote builds in this exact range every week. Below: the real cost tiers, the formula that explains your quote, the maintenance line nobody budgets, and the five scope decisions that can halve the number.
The small-business numbers that matter
What custom software actually costs in 2026
Custom software for a small business clusters into three honest tiers, and most SMBs live in the first two. A focused MVP (one core workflow, minimal admin, a clean interface) runs $25K to $45K. A typical production build with multiple user roles, real integrations, and an admin panel lands at $75K to $100K. Past that you’re into territory where the question changes from “what does it cost” to “should we even build this in-house.”
| Tier | What you get | Typical range | Timeline |
|---|---|---|---|
| Focused MVP | One core workflow, single user type, basic admin | $25K to $45K | 6 to 12 weeks |
| Typical small-business build | Multiple roles, 2 to 3 integrations, admin panel, reporting | $75K to $100K | 3 to 6 months |
| Complex / multi-system | Heavy integrations, compliance, custom workflows | $120K to $250K+ | 6 to 12 months |
| Enterprise portfolio | Multi-app, legacy migration, large user base | $1M+ | 12+ months |
Cost tiers on one scale
The tier boundaries aren’t about ambition. They’re about surface area. A clinic scheduling tool and a multi-tenant SaaS platform might both be “small business software,” but one talks to a calendar and the other talks to a payment processor, an email service, and a billing system. The second one costs three times as much because every one of those connections is its own little build.
The formula behind a custom software quote
Every legitimate quote reduces to the same three variables: scope × rate × team model. Scope is how much there is to build. Rate is what each engineer-hour costs. Team model is who’s doing the building and how they’re managed. Change any one and the total moves predictably, which is exactly why a vendor who won’t break their number into those parts is a vendor to be careful with.
Rate is the lever most buyers fixate on, and it’s real: US senior developers bill $125 to $250+ per hour, while offshore India teams quote $20 to $45/hr, averaging around $32. That spread is the whole reason offshore exists. But the quoted rate isn’t your delivered cost. The true loaded cost of offshore work lands at 1.4x to 1.8x the sticker rate once you price in ramp-up, management, and the occasional re-do. A $32 rate that behaves like $50 is normal. Plan around it.
Where the rate spread comes from
Scope is the lever you actually control, and it’s the one we’ll come back to, because it’s where a $120K quote becomes an $80K quote without anyone cutting quality.
Integrations and user roles cost more than screens
Because screens are the cheap part. A button is a button. What’s expensive is everything the button connects to, and that’s where small-business quotes quietly inflate. Each user role you add isn’t just a login. It’s a separate set of permissions, a separate view of the data, and a separate path to test. Three roles isn’t 3x one role, but it’s a lot more than 1x.
Integrations are worse, in the honest sense. Every external system your software talks to, whether that’s a payment processor, an EHR, a shipping API, or your accounting tool, needs its own connection code, its own error handling for when that system goes down, and its own test coverage. We’ve watched the integration line surprise people more than any other. The first time we scoped one of these, we under-counted the data-cleanup work that comes before the integration even starts, and we’ve never made that mistake twice. If your software needs to talk to four systems, four is doing most of the pricing, not the number of pages.
This is also why AI features add roughly 10% to 20% to a mid-or-large project. They’re an integration plus a data problem, not a screen.
What ongoing maintenance costs after launch
Software is never “done,” and the maintenance line is the one small businesses forget until the invoice arrives. Budget 15% to 25% of the original build cost per year. On a $90K build, that’s roughly $13K to $22K annually, and it’s not optional padding. It covers hosting, security patches, library updates, browser changes, and the small fixes that keep a live system live.
| Build cost | Annual maintenance (15% to 25%) | What it covers |
|---|---|---|
| $40K | $6K to $10K | Hosting, patches, minor fixes |
| $90K | $13.5K to $22.5K | Above + dependency upgrades, monitoring |
| $150K | $22.5K to $37.5K | Above + scaling, periodic security review |
Skip maintenance and you don’t avoid the cost. You defer it into something worse. Dependencies rot, a security patch goes unapplied, and eighteen months later you’re paying for an emergency fix at emergency rates instead of a steady retainer. Your CFO will ask why the project “costs money after it’s finished.” The answer is that a car costs money after you buy it, too.
How a US-managed, India-delivery model changes the math
It changes the rate without changing the accountability, and for a small business, that’s the difference between affordable and reckless. A hybrid model can cut the blended rate 40% to 60% compared to a US-only team, because the engineering happens at India economics. What it keeps is the part that usually breaks in pure offshore: a US-side technical owner, US-law IP assignment, and working-hours overlap.
Three delivery models compared
The trap with rock-bottom offshore isn’t the rate. It’s the hidden multiplier. We’ve audited rescue projects where the original vendor rotated developers through the codebase and the client paid for the same learning curve three times over. The savings looked great in the contract and evaporated in delivery. Clutch’s own guidance is blunt: an agency’s higher rate typically saves 20% to 30% over a project’s life through avoided rework. The cheapest quote and the cheapest delivered software are rarely the same vendor. We unpack the full rate picture in our offshore software development rates guide, and the build-versus-hire question in our in-house vs outsourcing cost math.
The scope decisions that actually halve a quote
Five, and they’re all about shipping less now rather than building worse. None of them cut quality. They cut surface area, which is the thing that drives the price.
- Ship one workflow, not five. Pick the one that proves the business case and defer the rest. You can’t validate five workflows at once anyway.
- Defer the admin dashboard. For the first months, a database tool and a spreadsheet export do the job. Custom admin UI is real money you don’t need on day one.
- Use hosted checkout, not custom payments. A payment processor’s drop-in flow saves weeks of build plus the compliance burden of handling card data yourself.
- Start with one integration. Add the second and third after launch, when you know which ones users actually touch. Most teams over-integrate at the start.
- Skip the native mobile app until the web app earns it. A responsive web build covers most early needs at a fraction of two-platform native cost.
Five cuts that halve a quote
Run those five and a $120K quote routinely becomes $70K to $80K. If your backlog is a wish list rather than a launch list, stop and re-scope before you sign anything. That’s the cheapest decision on this page.
What we’d recommend
For most small businesses, the right first build is smaller than the one they walk in describing. We’d rather ship a tight $40K MVP that proves the workflow than a $120K everything-machine that takes nine months to find out the workflow was wrong. Our product development engagements start with a fixed-scope discovery so the number is real before you commit, and our digital transformation work handles the cases where custom software is replacing a tangle of manual processes.
The structure we run: an Austin-side architect who owns scope and code review, delivery from Bangalore and Mohali at India rates, three to four hours of daily overlap, and IP assigned to you under a US master services agreement. The rate gets you the engineers. The overlap and review gates get you software that works. If you’re weighing vendors, our 22-question vendor scorecard is the same checklist we’d hand a friend.
Tell us what you’re building and we’ll give you a straight answer on scope, cost, and timeline within 48 hours, with a real range in the first conversation, not the third. Talk to us.