"How much does custom software cost?" is the most common first question, and the least answerable without more information. That is not evasion. Two projects that sound identical can differ by an order of magnitude once you look underneath. Understanding why helps you brief better, compare quotes fairly, and spend where it counts.
Why quotes vary so much
Different companies make different assumptions. One quote includes data migration and user training, another does not. One assumes ten users, another a thousand. One includes support for a year, another stops at launch. When quotes disagree, the useful conversation is about assumptions, not about who is cheapest.
The seven things that drive cost
1. Scope. The number of distinct features, screens and rules. Fewer, better-chosen features cost less and tend to be used more.
2. Users and roles. A system for one team with one permission level is simpler than one with customers, staff, managers and partners who each see different things.
3. Integrations. Every connection to another system, such as accounting, payments or a CRM, adds design, building and testing work, and ongoing maintenance.
4. Data migration. Moving existing information into a new system is often underestimated. Clean data is quick. Years of inconsistent spreadsheets are not.
5. Design depth. A functional internal tool needs less design effort than a polished public-facing product.
6. Security and compliance. Handling personal data, financial records or regulated information increases the care, documentation and testing involved. (See our GDPR checklist for the data side.)
7. Hosting and support. The system has to live somewhere and be looked after. Costs continue after launch.
What matters less than you think
The choice of programming language or framework rarely changes the cost dramatically for a business system. What changes it is how well the problem is understood before building starts. Uncertainty is expensive, which is why a discovery phase tends to pay for itself.
Getting comparable quotes
- Give every company the same written brief.
- Ask each to list assumptions: users, integrations, migration, testing, support.
- Ask what is not included.
- Ask how changes are handled and priced.
Reducing cost without cutting quality
- Start smaller. Release the part that delivers most value first, and learn from real use.
- Decide early. Changing your mind late is far more expensive than changing it early.
- Reuse proven components for common needs like sign-in and payments rather than inventing them.
- Be clear about "must have" versus "nice to have".
Budget for the long term
Software is not a one-off purchase. Plan for hosting, maintenance, security updates and a modest ongoing improvement budget. A system you cannot afford to maintain becomes a liability.
Questions to ask about any proposal
What is included and excluded? How many users does it assume? What does support cost after launch? Who owns the code? How are changes handled?
If you would like a scoped proposal rather than a vague estimate, tell us about the problem and we will talk it through.