What Actually Drives Custom Software Cost (and How to Lower It)

You asked two developers to quote for "the same app" and got two very different numbers. One looks too cheap, one looks too expensive, and you have no way to tell which is right.

The difference is rarely about the hourly rate. It's about what each developer thinks you're asking for. Once you understand the five things that drive most of the cost, you can compare quotes properly, and you can shape your project so it costs less without becoming worse.

Why "how much does an app cost?" has no single answer

Custom software is closer to building a house than buying a car. "A house" can be a small flat or a large villa. The price depends on rooms, materials, plumbing and how much is already there. Software works the same way: the price depends on how many people use it, what it connects to, what data it has to carry over, what it reports, and how polished it needs to be on day one.

The 5 things that drive most of the cost

1. User roles and screens

Every type of user adds work. An owner, a staff member and a customer each need their own screens, their own permissions and their own testing. A system with one role and ten screens is a very different project from one with four roles and forty screens.

Ask yourself: who will actually log in, and what does each of them need to do on day one?

2. Integrations

Connecting to payments, WhatsApp, accounting software, a website or a delivery service is often where the hidden work sits. Each integration needs setup, error handling (what happens when the other system is down?) and testing. Some services are simple to connect; others have strict rules and approval steps.

Ask yourself: which connections are essential now, and which can wait for version two?

3. Moving data from the old system

If you already have years of data in spreadsheets or an old system, it has to be mapped, cleaned and checked before it moves. Old data is rarely clean: duplicates, missing fields, different formats. This work is easy to underestimate in a quote.

Ask yourself: do you need all historical data on launch day, or only the active records?

4. Reports and dashboards

A simple list of sales is quick to build. A dashboard with filters, date ranges, exports, charts and per-branch totals takes much longer. Reports are also where requirements tend to grow during a project.

Ask yourself: which three reports do you actually check every week?

5. Mobile apps and design polish

A responsive web app works on phones, tablets and computers from one codebase. Separate iOS and Android apps, offline mode, push notifications and pixel-perfect custom design all add time. They can be worth it, but they're rarely needed in the first version.

How to compare two quotes fairly

When quotes differ a lot, ask each developer the same questions:

→ What exactly is included? List the roles, screens, integrations and reports they priced.

→ What's excluded? Data migration, hosting, training and support after launch are often left out.

→ How do they handle changes? Every project changes. You want to know how a change request is priced before it happens.

→ How will you see progress? Weekly updates and a demo at every milestone are a good sign. Silence for two months is not.

A cheaper quote that leaves out integrations and migration often ends up more expensive.

How to lower the cost without lowering the quality

The most reliable way to reduce cost is to start with a smaller first version. Build the part that saves the most time or brings in the most money, use it for real, then add the rest.

In practice that means:

→ One or two user roles at first.

→ The one integration you can't live without.

→ Active data only, archive the rest.

→ Three key reports, not thirty.

→ A responsive web app before native mobile apps.

This also lowers risk. You find out what your team really needs from using the system, not from guessing in a meeting.

Prepare before you ask for quotes

Developers can only quote what you describe. Before you contact anyone, answer the 7 questions before you build custom software. Clear answers give you clearer, more comparable quotes. You can also use my free quotation generator to see how a clean, itemised quote is laid out.

A worked example: two quotes for "a booking system"

A clinic asks two developers to quote for a booking system. Quote A is much lower than Quote B. On paper they're for the same thing. In detail:

→ Quote A covers one role (reception), online booking and a simple calendar.

→ Quote B covers three roles (reception, doctors, patients), online booking, WhatsApp reminders, card payments, a patient history import from the old system and monthly reports.

Neither developer is wrong. They priced different projects. The smart move is to decide the first version yourself: reception and doctor roles, booking and WhatsApp reminders on day one, payments and reports in phase two, and only active patient records migrated at launch. Now both developers can quote the same scope, and you can compare them fairly.

Frequently asked questions

Is a fixed price or hourly billing better?

A fixed price works well when the scope is clear and small. Hourly or milestone billing suits projects where you expect to learn and change things along the way. Either way, agree how changes are priced before work starts.

Why do some developers ask so many questions before quoting?

Because the answers decide the price. A developer who quotes without asking about roles, integrations, data and reports is guessing, and guesses usually come back as extra costs later.

Are there ongoing costs after launch?

Usually yes: hosting, domain, third-party services (like WhatsApp or payment fees), backups and support. Ask for these in writing so the total cost of ownership is clear.

Can I start small and add features later?

Yes, and it's usually the best way. A good first version is built so new features can be added without rewriting what already works.

Want a clear estimate?

I've built ERPs, POS systems, CRMs and automation for different industries, like this ERP for a luxury watch business. If you're planning custom software, send me a message with what you want to build. I'll tell you what drives the cost in your case and what a smart first version could look like. See all services.