Custom software development cost comes down to how many people work for how long, at what rate. As a typical 2026 market range, a focused internal tool or integration often lands between $10,000 and $50,000, a business application with several user roles between $40,000 and $150,000, and a customer-facing platform or SaaS product well above that. Those ranges vary widely with where the team is based and exactly what is being built, which is why the pricing model matters as much as the headline number.
What is the typical custom software development cost in 2026?
There is no single price, but most projects fall into recognizable bands. The table below shows typical market ranges, not quotes; treat them as a starting point for a conversation, not a budget.
| Project type | Typical scope | Typical market range (varies) | Typical duration |
|---|---|---|---|
| Integration or automation | Connect two systems or replace a spreadsheet process; one or two user roles | $10,000-$50,000 | 4-10 weeks |
| Internal business application | Workflows, approvals, reporting, three to five roles, a few integrations | $40,000-$150,000 | 3-6 months |
| Customer portal or marketplace | Public sign-up, payments, notifications, admin panel | $75,000-$250,000 | 4-9 months |
| SaaS platform | Multi-tenancy, billing, onboarding, permissions, audit trail | $150,000-$500,000+ | 6-12+ months |
A team in the US, UK or Australia will usually sit at the top of these bands or above them; an offshore team often sits lower. The same application can move up a band because of a single compliance requirement or a difficult integration. If you are a US company weighing an offshore team, our US page covers time zones, contracts and payment.
How is a software estimate calculated?
An estimate is effort multiplied by a blended rate, plus contingency. If you understand the effort, you can challenge any quote.
Take a customer portal that needs a designer for 4 weeks, two developers for 16 weeks each, a QA engineer for 8 weeks and a project manager at a quarter of their time across 16 weeks. That is 4 + 32 + 8 + 4 = 48 person-weeks. Multiply by the team's weekly rate, then add 10-20% contingency for the unknowns every project has.
Rates vary more than anything else in the equation. As a very rough guide that differs by firm and seniority, onshore agencies in the US, UK and Australia often bill $100-$200 or more per hour, while teams in South Asia often bill a fraction of that; see our guide to outsourcing software development to Nepal for what the lower rate does and does not buy.
Development is usually the largest line, but design, QA and project management together commonly make up a third or more of a realistic estimate. A quote that is almost entirely "development" has usually left the testing to you.
What drives the cost to build software?
Complexity of rules and connections, not the number of screens. These are the items that most often move a project from one band to the next:
- User roles and permissions. Each role multiplies screens, business rules and tests.
- Integrations. Every third-party system (ERP, accounting, CRM, payment gateway) adds build work, error handling and future maintenance. Poorly documented APIs cost the most.
- Data migration. Moving years of records from an old system means cleaning, mapping and reconciling them.
- Compliance. HIPAA, PCI DSS, SOC 2 or GDPR obligations add audit logs, encryption, access reviews and documentation.
- Non-functional requirements. Uptime targets, response times, peak load and offline use.
- Reporting. "Just a dashboard" often hides the hardest queries in the project.
- Design depth. A component library with sensible defaults costs less than a fully custom product design.
- Testing depth. Automated test coverage, a device matrix and load testing are real work, and worth paying for.
Fixed price vs time and materials vs milestone-based: which is best?
Fixed price suits small, well-defined work; time and materials suits products whose requirements will change; milestone-based pricing suits larger projects where both sides want checkpoints. Many good contracts combine them.
| Model | How it works | Good for | Watch out for |
|---|---|---|---|
| Fixed price | One price for an agreed scope | Small, well-specified projects and first phases | A risk premium in the price; change requests for anything outside the written scope |
| Time and materials | You pay for the hours or days worked, usually monthly | Evolving products, ongoing development | Needs visibility: a budget cap, weekly burn reports and working demos |
| Milestone-based | The price is split across deliverables, each paid on acceptance | Larger projects with clear phases | Vague acceptance criteria turn into disputes |
| Dedicated team or retainer | A monthly fee for a set team or set days | Long-running products and maintenance | Paying for capacity you do not use |
Fixed price is not automatically safer for the buyer. The vendor prices in risk, every unclear requirement becomes a change request, and a vendor under margin pressure may quietly cut testing. Time and materials with a "not to exceed" cap and a weekly report often gives you more control. A common hybrid is a fixed-price first phase, followed by time and materials in short, reviewable blocks.
What does software cost after launch?
Plan for running costs from the first budget conversation. Software that nobody maintains becomes a security risk within a year or two.
- Hosting and infrastructure: compute, managed database, backups, monitoring and logs.
- Third-party services: email sending, SMS, maps, authentication, error tracking, per-seat licenses.
- Security patches and dependency updates: frameworks and libraries publish fixes constantly, and someone has to apply and test them.
- Support and small changes: usually a retainer or a block of hours.
A common rule of thumb is to budget 15-20% of the original build cost per year for maintenance and small improvements, before hosting. Treat it as a starting point: a system with many integrations needs more, a stable internal tool may need less.
How can you reduce the cost of building software?
Reduce scope before you reduce the rate. A cheaper team building the wrong thing costs more in the end.
- Build only the workflow that makes your business different, and buy the rest: Stripe for payments, Auth0 or Clerk for login, Postmark or SendGrid for email, Metabase for internal reports.
- Launch with one or two user roles and add the others in phase two.
- Use an off-the-shelf admin tool for the first version instead of a custom admin panel.
- Write down what is out of scope, not only what is in.
- Make decisions quickly; on time-and-materials work, waiting for client feedback is a real cost.
- Check honestly whether an existing SaaS product covers most of the need if you adapt the process slightly.
If you are testing a new product idea rather than replacing an existing process, our MVP development guide goes further on cutting scope.
What should you ask a software development company before signing?
Ask questions that expose the assumptions, because two quotes are only comparable once their assumptions match. Our guide on how to compare development quotes has a fuller checklist.
- What assumptions is this estimate based on, and which would change it most?
- How is the effort split between design, development, QA and project management?
- What happens when we change our mind about a feature?
- Who owns the code, the repository, the cloud accounts and the domain, from the first day?
- How often will we see working software, and where?
- What is not included: hosting, licenses, data migration, content entry, app store fees?
- What does support cost after launch, and what response times are written into the agreement?
- Can we stop partway, and what do we keep if we do?
How Meritbyte Technologies prices software work
Meritbyte Technologies is a Nepal-based web and software development company that builds platforms, internal tools, APIs and integrations in TypeScript, Python, Go and .NET. Our pricing follows the hybrid described above, and we publish how it works rather than a price list.
- A free scoping conversation; you get back a scope, a timeline and a number, with no paid discovery phase in between.
- A fixed price for the first milestone, so your first commitment has a known cost.
- After that, two-week blocks with a demo at the end of each. You can stop at the end of any block.
- One project manager, a written update every week, and a staging URL you can open any time.
- Code, repositories and cloud accounts in your name, with documentation at handover.
More detail is on our custom software development and QA and testing pages.
Frequently asked questions
Why do software development quotes vary so much?
Vendors assume different scopes, team locations, seniority levels and amounts of risk. One quote may include design, automated testing and a staging environment, while another covers development only. Some add a large contingency to protect a fixed price. Ask each vendor to list its assumptions and effort by role, then compare like with like before you compare totals.
Is fixed price safer than time and materials?
Not necessarily. Fixed price caps spend on the agreed scope, but vendors add a risk premium and bill changes separately, and one under margin pressure may cut testing. Time and materials with a spending cap, weekly reporting and the right to stop often gives you more control. A fixed first milestone followed by short blocks combines the two.
How much does it cost to maintain custom software?
A common rule of thumb is 15-20% of the original build cost each year for maintenance and small improvements, plus hosting and third-party services. The real figure depends on how many integrations can break, how often your frameworks publish security updates, and how much you keep changing the product after launch.
Can I get an accurate estimate without paying for discovery?
You can get a useful estimate with a stated range from a well-run scoping conversation, provided you share your workflows, users, integrations and constraints. Precision improves once design is done. Be wary of anyone quoting an exact figure for a complex system after one call, and equally wary of an expensive discovery phase before any number at all.