What are the price corridors for custom software, and what separates them?
Two corridors cover almost every small business custom software project, plus an hourly rate for anything smaller.
- $6,000 to $15,000, an internal tool or a connected system. A tool your staff uses daily, a handful of integrations between systems that do not talk to each other today, a private RAG search over your own documents, or infrastructure with CI/CD behind it. Most small business custom software lands here.
- From $15,000, a full custom build. Software with real logic behind it: a quoting or pricing engine, a multi-system build where several pieces of software have to agree with each other, a long project with multiple phases, or a complex RAG deployment across many document types.
- $150 to $200 an hour, for anything that does not justify a project. A one-off script, a single API integration, a bug fix in someone else's codebase. If the work is a few hours, not a few weeks, hourly is usually the honest quote, not a project.
What decides where a build lands inside a corridor, or whether it needs the corridor above, is the subject of the next section: it is not lines of code, it is what the software has to connect to and who is accountable for it once it ships.
What actually moves the price of custom software?
Four variables account for most of the spread between $6,000 and well past $15,000.
| Driver | Cheaper end | More expensive end | Effect on the quote |
|---|---|---|---|
| Integrations | Zero or one system to connect to (a spreadsheet, a single API) | Several systems that must stay in sync: CRM, calendar, accounting, a legacy database with no clean API | Usually moves you a tier up per system added |
| Number of users | A handful of internal staff, one role, one permission level | Multiple roles, external users (clients or vendors log in), audit trails required | Adds authentication, permissions and testing surface |
| Data migration | Starting clean, or a small, well-structured dataset to import | Years of data in a legacy system, inconsistent formats, no existing export | Adds a discrete phase of work before the build starts |
| Who maintains it after launch | You have technical staff, or the tool is simple enough to leave alone | Nobody in-house can read the code; every change has to go back through a vendor | Shapes ongoing cost more than build cost: see support tiers below |
Two of the four are not really about the software at all. Data migration is the one that turns a clean estimate into a moving target, because nobody knows exactly what is in an old system until someone opens it. Who maintains it is the one that determines whether $15,000 today becomes a fixed cost forever or a manageable one: a tool built on a standard, documented stack can be picked up by any competent developer; a tool built inside someone's proprietary platform cannot, and that is a cost you pay later, not now.
Support after launch runs $300 to $500 a month for monitoring, updates and small changes (Care), or $750 to $1,500 a month for continuous new work and DevOps (Active). Neither is mandatory. What each tier includes is on the pricing page, with more detail under custom software.
What do software agencies and freelancers actually charge, and why is the range so wide?
Three public sources put numbers on this, and they do not agree with each other, because they are not measuring the same thing.
| Source | What it measures | Reported range | Published |
|---|---|---|---|
| Clutch, Software Development Pricing Guide | Verified agency projects reviewed on Clutch | Average project $132,480; agencies typically charge $25 to $49/hour, U.S.-based agencies $50 to $99/hour | Updated Sept. 8, 2026 |
| GoodFirms, Custom Software Development Cost Survey (100+ software companies surveyed) | Agency project pricing by company size | Small to mid-sized projects $30,000 to $100,000 (65.7% of firms); hourly $20 to $50/hour for 56.3% of firms, $100 to $250/hour for North American and Western European firms on complex work | Updated May 29, 2026 |
| Upwork, Hourly Rate Benchmarks | Individual freelancer public rates | Full-stack developers $16 to $35/hour; back-end developers $20 to $40/hour; AI engineers $35 to $60/hour | Published Jun 20, 2025 |
Read together, the pattern is straightforward. Clutch and GoodFirms both survey agencies, and their average project sizes ($30,000 to $132,000+) reflect projects with discovery, project management, QA and a team, not just build hours. Upwork's numbers are individual freelancer rates, and the gap between $16 an hour and a $132,000 average project is the cost of coordination, not a scam on either end: a freelancer with no project manager and no continuity if they disappear is a different purchase than a firm that owns the outcome. Neither is automatically right. A well-scoped small tool is a reasonable freelance project; a system with real logic and several integrations that a business depends on is a reasonable agency project. The $6,000 to $15,000 corridor above sits between the two, because it assumes one contractor of record, a fixed number, and support after launch.
Why do most software quotes come back so differently for the same request?
Send the same one-paragraph description of an internal tool to five vendors and the quotes will not cluster. Here is why, and it is mostly not dishonesty.
Scope is rarely the same across quotes, even when the request sounds identical. "Build me a tool that tracks jobs" means something different to a vendor who assumes you will supply every field and workflow than to one who assumes discovery is part of the job. Data migration gets missed by whichever vendor did not ask what you are moving from, and turns into a change order once the real dataset shows up in month two. Maintenance philosophy differs too: a vendor pricing a tool to be handed off and abandoned quotes lower than one pricing a tool meant to be extended for years.
What to do with that: ask every vendor the same four questions from the driver table above before comparing numbers, not after. A quote that has not addressed integrations, users, migration and maintenance is not a quote yet, it is a placeholder.
In-house tool, agency build, or off-the-shelf software: how do you decide?
Before pricing a custom build at all, it is worth ruling out the alternative that costs nothing to build: software that already exists.
- Off-the-shelf fits when your workflow is common. Invoicing, basic CRM, scheduling and accounting are solved problems; a $30-a-month subscription usually beats a $10,000 build, and someone else maintains it.
- Custom fits when your workflow is specific to how you operate, and forcing it into someone else's software means working around the tool: a scheduling system built around a licensing rule specific to your trade, a quoting engine that reflects pricing logic no off-the-shelf tool encodes, or a bridge between two systems never meant to talk to each other.
- The test: if your team already has a manual workaround to make a generic tool fit, that workaround is usually the spec for the custom piece. Everything else can probably stay off-the-shelf.
If the answer is custom, the next decision is who builds it: in-house hire, agency, or offshore contractor. That comparison, with real wage and rate data rather than a rule of thumb, is covered in in-house vs. agency vs. offshore.
In Sacramento specifically, the same corridors apply locally: see custom software development in Sacramento.