Key takeaways
- A small internal tool can come in under $40,000, while a multi-tenant platform with a handful of integrations can pass $500,000 before launch.
- Cost is hours multiplied by rate, and the hours depend on scope, integrations, user roles, compliance, platforms and data migration.
- Blended rates run from roughly $120–$250 per hour at US onshore firms to roughly $20–$55 in India and South or Southeast Asia.
- A fixed-price discovery phase of 2–4 weeks, then time and materials with a budget cap, gives you a real number and room to change course.
- Budget 15–25% of the original build cost per year for maintenance, plus hosting, third-party services and your own team's time.
The honest answer to “how much does custom software development cost” is a range so wide it sounds evasive. A small internal tool can come in under $40,000. A multi-tenant platform with a handful of integrations can pass $500,000 before it launches. That range isn't a dodge. “Software” covers everything from a spreadsheet replacement to the system that runs your whole company, and the price follows the work. This guide breaks down where the money goes, what common project types cost in 2026, and how to spend less without buying something you'll need to rebuild in three years.
The numbers below are market ranges based on how projects are commonly scoped and priced by North American, nearshore and offshore vendors. They aren't quotes. Your project will land on a specific number once someone looks at your actual requirements.
What actually drives the cost
Almost every software budget reduces to one formula: hours multiplied by rate. The rate depends on who you hire and where they are. The hours depend on six things.
1. Scope, measured in workflows
Count the jobs the software has to do, not the screens. A customer portal where clients log in, see invoices and pay them is one workflow with a few steps. Add quoting, approvals, document uploads and a support inbox and you have five workflows, each with its own edge cases. The edge cases are where the hours hide. What happens when a payment fails halfway through? When one user belongs to two customer accounts? When the approver is on vacation for two weeks? Every one of those needs a decision, some code and a test.
2. Integrations
Connecting to other systems is the line item we see underestimated most often. A clean, well-documented API like Stripe's might take a few days. An older ERP with a SOAP interface, inconsistent data and no test environment can take weeks. If your project touches QuickBooks, Salesforce, Dynamics 365, a payroll provider and a shipping carrier, estimate each one separately and ask the vendor which of them they've actually connected to before.
3. Users, roles and permissions
A tool used by eight people in one department is much simpler than one used by customers, staff and partners who each see a different slice of the same data. Every role multiplies the testing. Multi-tenancy (one application serving many separate client organizations) adds design work that's expensive to bolt on later, so decide early whether you need it.
4. Compliance and security
HIPAA, PCI DSS, SOC 2 readiness and state privacy laws like the CCPA all add real work: audit logs, encryption decisions, access reviews, data retention rules and usually an outside penetration test. Expect a regulated project to cost noticeably more than the same features built without those constraints. That money is well spent. Retrofitting compliance after launch costs more.
5. Platforms
A responsive web app runs on phones, tablets and desktops from one codebase. Native iOS and Android apps used to mean two codebases. Cross-platform frameworks like React Native and Flutter close most of that gap, but you still pay for app store releases, device testing and push notifications. If a mobile-friendly web app would do the job for your first release, it's usually the cheaper place to start.
6. Data migration
Moving fifteen years of records out of an Access database or an old ERP is a project of its own. Removing duplicates, mapping fields and running practice migrations takes longer than people expect, and it has to be finished before go-live, not after. If you have messy legacy data, give migration its own line in the budget.
Typical price ranges by project type
The table shows ranges commonly seen for projects built by experienced North American or nearshore teams. Offshore-only teams can come in lower. Large consultancies often come in higher.
| Project type | Typical scope | Common cost range (USD) | Typical timeline |
|---|---|---|---|
| Internal tool or workflow app | One department, 1–3 workflows, a couple of integrations | $25,000–$80,000 | 6–12 weeks |
| Customer portal or web app MVP | Logins, one core workflow, payments or documents, admin panel | $60,000–$180,000 | 3–5 months |
| Mobile app (iOS and Android) | Cross-platform app, backend API, admin panel | $80,000–$250,000 | 4–7 months |
| SaaS product, first release | Multi-tenant, subscriptions, onboarding, reporting | $150,000–$450,000 | 5–9 months |
| Enterprise system or integration hub | Many roles, several system integrations, compliance | $250,000–$1,000,000+ | 8–18 months |
| Legacy system modernization | Rebuild or re-platform an existing system, including data migration | $100,000–$750,000+ | 4–18 months |
If a vendor gives you a firm price after one 30-minute call, treat it as a guess. A number you can plan around needs at least a short discovery phase where someone maps your workflows, integrations and data.
Hourly rates: onshore, nearshore and offshore
Rates vary more by geography than by skill, which is why the sourcing decision has such a large effect on your budget. These are rough 2026 market ranges for blended team rates at established firms, not freelancers.
- US onshore agencies and consultancies: roughly $120–$250 per hour, higher at large firms and for specialist work.
- Canada: roughly $80–$160 USD per hour, with the same time zones as US clients and a similar business and legal culture.
- Latin America: roughly $45–$95 per hour, with good time-zone overlap for most US teams.
- Eastern Europe: roughly $40–$90 per hour, overlapping mostly with US mornings.
- India and South or Southeast Asia: roughly $20–$55 per hour, usually with little same-day overlap unless the team works shifted hours.
A low rate isn't the same as a low cost. A team billing $35 an hour that needs twice the hours, a round of rework and a US project manager to translate requirements can cost more than a team at $90 that asks the right questions the first time. What you're really buying is working software per dollar, and communication overhead eats into that quickly.
Time zones matter more than most buyers expect. When your developers are asleep during your workday, every clarifying question costs a day. Over a six-month project those days add up to weeks. Our offices work local hours in the time zones they serve, so we have an obvious interest in this point, but it holds no matter who you hire.
Fixed price vs time and materials
Two pricing models cover most development contracts. Each one puts the risk on a different side of the table.
Fixed price
You agree on a scope and a price, and the vendor carries the risk of going over. For small, well-defined projects that works well. The catch is that vendors price the risk in, often with a sizable buffer, and every change becomes a change order. If your requirements shift once people see the first demo (and in most real projects they do), fixed price turns into an argument about what was “in scope”.
Time and materials
You pay for the hours actually worked, usually billed every two weeks or monthly against an estimate. You carry more of the risk, but you get flexibility: you can reprioritize after a demo without renegotiating a contract. This model only works when the vendor is transparent. You should see timesheets, a shared backlog and working software every sprint.
What we recommend for most projects
Use both. Pay a fixed price for a short discovery phase, usually 2–4 weeks, that produces a clickable prototype, an architecture outline and an estimated backlog. Then build on time and materials with a budget cap and a regular check against it. You get a real number before committing to the build, and you keep the freedom to change your mind once you see the software working.
Hidden costs that show up after launch
The build is only part of the total cost of ownership. Plan for these from the start:
- Hosting and cloud services. A small business app on AWS or Azure might cost $100–$1,000 a month. A busy SaaS product with heavy data processing can cost several thousand. Managed databases, file storage, backups and monitoring each add a line.
- Third-party services. Maps, SMS, transactional email, payment processing fees, AI model usage and authentication services all bill monthly or per use, and they grow with your user count.
- Maintenance. A common rule of thumb is 15–25% of the original build cost per year for bug fixes, security patches, framework upgrades and small improvements. Skip it and your new app slowly becomes your next legacy system.
- Security and compliance upkeep. Annual penetration tests, access reviews and app store policy changes all take time.
- Your own team's time. Someone on your side has to answer questions, review demos and test releases. Budget a few hours a week from a product owner at minimum, more during launch.
- Training and rollout. Internal tools especially need an adoption plan. Software nobody uses is the most expensive software there is.
How to cut cost without cutting corners
Some savings are real. Others just push the bill into next year. These are the ones that work.
- Ship the smallest version that proves value. Pick the workflow that causes the most pain or earns the most money, build that first, and let real usage tell you what comes next. Most first-release feature lists can lose a third of their items without anyone missing them.
- Buy the commodity parts. Don't build your own login system, payment handling or email delivery. Use services like Microsoft Entra ID, Auth0 or Stripe, and spend your budget on the parts that make your business different.
- Check whether existing software gets you most of the way. If a SaaS product, Dynamics 365 or Power Apps covers 80% of your needs, configuring it and building small extensions is often far cheaper than writing everything from scratch.
- Pick a mainstream tech stack. React, .NET, Node.js, Python and PostgreSQL are easy to hire for and cheap to maintain, and they keep you from being stranded if you ever change vendors.
- Pay for automated tests and a deployment pipeline from day one. It feels like overhead in month one. By month six it's the reason a release takes an hour instead of a stressful weekend.
- Make decisions quickly. Developers waiting on feedback bill the same as developers writing code. A product owner who answers questions the same day saves real money.
The corners you shouldn't cut: security basics, automated tests on the critical paths, written notes on how the system is deployed, and ownership of your own code and cloud accounts. Saving money on any of those tends to cost more later.
How to get an estimate you can trust
Before you contact vendors, write a two-page brief. Cover who uses the system, the five most important things they need to do, the systems it must connect to, any compliance requirements, and your target launch date and budget range. Sharing a budget range doesn't weaken your position. It lets a vendor tell you what's realistic at that number instead of guessing.
Then compare proposals on equal terms. Look at how each vendor broke down the work, what they assumed and what they left out. A lower quote that excludes testing, project management or deployment isn't cheaper. It's incomplete.
If you'd like a second opinion on a quote you already have, or a ballpark for your own project, we're glad to take a look. Email sales@tag4tech.com or use our contact page and tell us what you're trying to build.