Short answer
Custom software development cost depends mostly on the shape of the project. A focused marketing site costs the least, a mobile MVP typically costs in the tens of thousands, and SaaS products and enterprise platforms are priced in phases. The gap between the cheapest and priciest shapes is roughly five to ten times, driven by integrations, compliance and data migration.
Here's the direct answer, before the explanation: a focused marketing site can launch within a few weeks and is the least expensive of these project shapes. A mobile MVP usually lands in the tens of thousands depending on feature count and integrations. A SaaS MVP or custom CRM can also launch within a few weeks, with the full build delivered in phases as features are added. A full enterprise platform or ERP migration is priced in phases, not as a single number. The gap between the cheapest and most expensive of these shapes is roughly five to ten times, and it's driven almost entirely by three factors, not by which vendor you pick. For a quick range on your own project, try our app development cost calculator.
'It depends' is a true answer to 'how much does custom software cost,' but it's an unhelpful one on its own. What it actually depends on is knowable in advance, and this is a breakdown of exactly what, using the project shapes and timelines we scope against every day.
Custom software development cost by project shape
These are the shapes most custom software requests actually fall into, with how we usually schedule each one:
| Project shape | Typical timeline | What mainly drives the cost |
|---|---|---|
| Focused marketing site | A few weeks | Design and content volume, with the least integration complexity of any shape here |
| Web application with accounts and data | MVP in a few weeks, then staged by feature | Data model complexity and number of distinct user roles |
| Mobile MVP | Tens of thousands, scoped in discovery | Feature count and native integrations: payments, push, camera, background location |
| SaaS MVP | A few weeks, then phased releases | Multi-tenant data model design and billing/subscription integration |
| Custom CRM | MVP in a few weeks, then phased by module | How far your actual process diverges from a generic sales or ops pipeline |
| Enterprise platform or ERP migration | Multi-month, phased | Compliance mapping, integration count, and data migration volume |
Key takeaway
The timeline is the honest proxy for cost. A project that's a 4-to-6-week shape doesn't become an 8-to-14-week one just because a vendor prices it that way.
The three factors that move software development cost
Almost every cost overrun we've seen on a custom software project (ours or one we've inherited) traces back to one of three factors, not to the base build itself:
- 1
Integration complexity
The number, age, and protocol of systems you need to connect. Bridging two decades-old systems that only speak SOAP with three newer REST APIs is a materially different scope than connecting to a single modern API.
- 2
Compliance requirements
HIPAA, SOC 2, or industry-specific audit needs change the data model, logging, and third-party vendor list, and cost far less when scoped from day one than when retrofitted after a finding.
- 3
Data migration volume and quality
Moving from a legacy system means schema mapping and validation before a single feature ships, and a messy, undocumented legacy data set costs more to migrate than to build against fresh.
Key takeaway
Ask about these three specifically before comparing quotes. They explain most of the spread between a low bid and a realistic one.
The fully-loaded cost of the alternative
The comparison that actually matters isn't 'agency vs. cheaper agency.' It's a scoped engagement against the fully-loaded cost of doing it another way. A single in-house senior engineering hire costs salary, benefits, recruiting time, and management overhead before they write a line of product code, plus a real ramp-up period, and still doesn't cover design, product management, or QA on its own. Those are usually separate hires or a gap the engineer absorbs.
An offshore-only team often looks meaningfully cheaper on an hourly basis, and for well-specified, low-ambiguity work it can be a good option. Where it tends to cost more than it appears is oversight and rework: requirements that cross a time zone gap and a language gap without someone with local context and product ownership catching drift early, which shows up later as a feature built to the letter of a spec that didn't match the actual intent.
How we scope a firm number during discovery
Every service page on this site says some version of the same thing, because it's how we actually work: we give a firm number after discovery, not a range that grows later. Discovery maps your real workflow, surfaces which of the three cost-driving factors above actually apply to your project, and identifies the smallest version of the build that solves the real problem, rather than a maximal scope priced to hedge against uncertainty we could have resolved by asking.
If you're comparing quotes from a custom software development company and want a concrete number instead of a range, talk to us about what you're building, and we'll tell you which of these project shapes you're actually in before quoting anything.