Custom software costs whatever the team costs per week, multiplied by the number of weeks it takes to build. Everything else, from features to integrations to design, matters only because it changes one of those two numbers. That's why published price ranges run from five figures to seven: they describe different teams working for different lengths of time.
This guide won't give you another range. It shows you how to work out a realistic budget for your own project, which pricing model protects you, and where budgets usually go wrong.
The formula behind every quote
Every quote you receive, whatever it looks like, comes from:
Team size × hourly or weekly rate × duration + ongoing costs after launch
A team of three developers working 16 weeks is 1,920 developer hours (3 people × 40 hours × 16 weeks). Add part-time design, project management and testing, and multiply by the rate. That's your build cost.
Once you see quotes this way, comparing vendors gets easier. A low quote either has a smaller team, a lower rate, fewer weeks, or less included. Ask which.
What a developer really costs in the US
It helps to know the in-house benchmark, because it's what you are comparing any agency against.
The US Bureau of Labor Statistics puts the median software developer salary at $135,980 (May 2025). Salary isn't the full cost to an employer. Across US private industry, wages make up 70% of employer compensation costs, with benefits making up the rest.
On that basis, a developer on the median salary costs an employer roughly $194,000 a year, or about $93 an hour across a standard 2,080-hour year. That's before recruitment, equipment, software licenses, management time and the months it takes to hire.
This is the number an outsourced or offshore team has to beat on total cost, not just on hourly rate.
Five things that change the number most
1. How clear the scope is before work starts
This is the biggest driver, and it's in your control. A project that starts with "we need a portal for our customers" will cost more than one that starts with a list of the screens, the user types and what each can do. Every open question gets answered during the build, at build rates.
2. Integrations with other systems
Connecting to a payment provider, a CRM, an accounting system or an old internal database takes longer than most buyers expect. Each one has its own documentation quality, test environment and quirks. If your software needs to talk to five other systems, budget for each one as its own small project.
3. User types and permissions
An app with one kind of user is simpler than one where admins, managers, staff and customers each see different things. Every role multiplies the screens, the rules and the testing.
4. Compliance and security requirements
Health data, payment data and personal data all bring rules about storage, access and audit trails. These add design, build and testing time. They are not optional, so they belong in the estimate from day one.
5. Where the team is
Rates vary widely by country. The same project can be quoted at very different prices by a team in Dallas, London or Karachi. Lower rates are real savings when the team communicates well and works in overlapping hours. They stop being savings when time zones and handoffs slow every decision down.
Fixed price, time and materials, or a dedicated team
How you pay changes your risk more than it changes your cost.
| Model | How it works | Good for | Watch out for |
|---|---|---|---|
| Fixed price | One price for an agreed scope | Small, well-defined projects | Vendors add a buffer for risk. Every change becomes a change request. |
| Time and materials | You pay for hours worked | Projects where scope will evolve | Needs weekly visibility into hours and progress |
| Dedicated team | A monthly fee for a set team | Long-running products and ongoing development | You manage priorities, so you need someone who can |
Fixed price feels safest, but it only protects you if the scope really is fixed. Most software projects learn things in the first month that change the plan. On a fixed contract, that learning either costs extra or gets ignored.
A practical middle path: fix the price of a short discovery phase that produces a detailed scope, then build on time and materials or with a dedicated team, with a weekly report of hours against plan.
Costs that come after launch
Build cost is the number everyone asks about. It's not the whole cost. Budget for:
- Hosting and infrastructure. Monthly, and it grows with your users.
- Third-party services. Maps, email sending, SMS, payment processing and AI APIs often charge per use.
- Maintenance. Security updates, library upgrades and fixes as operating systems and browsers change.
- New features. Once people use the software, they ask for more. That's a good sign, and it isn't free.
Ask every vendor what they expect these to cost per month for your project. A vendor who can't answer hasn't thought about your software running for more than a week.
Should you build at all?
Custom software makes sense when your process is a genuine advantage, or when off-the-shelf tools force you into workarounds that cost more than building. It doesn't make sense when a subscription tool does most of what you need for a monthly fee.
We compared both options for one common case in custom CRM development vs buying off the shelf. The same thinking applies to most business software.
How to get a quote you can trust
Before you ask for prices, prepare:
- A list of the user types and what each needs to do
- The systems the software must connect to
- Any compliance rules that apply to your data
- Your deadline, and whether it's real or preferred
- Your budget range, even if rough
Send the same brief to every vendor. Then compare team size, rate and weeks, not just the total. If one quote is far lower than the others, find out which of those three numbers is different and why.
Who we are
Diggit builds and runs its own software products, including the Kordic CRM, the GACS AI customer service agent and the Authentify product authentication platform. We also offer custom software development for clients, with a US company in Dallas and an engineering team in Karachi.
If you have a project in mind, book a scoping call and we'll help you turn it into a brief you can take to any vendor, including us.
Related questions
It depends on scope and team size. A focused first version with a clear scope is usually measured in weeks to a few months. Large platforms with many integrations take much longer. Ask vendors for an estimate in weeks alongside the price.
Hourly rates are usually lower. Total cost is lower only when communication, time zone overlap and quality control are handled well.
Because vendors assume different team sizes, rates and durations, and include different things. Ask each one to break the quote into those parts.