How much does custom software cost? What drives the price

It's one of the first questions before starting a project, and the honest answer is that it depends. That's not a dodge: two systems that sound alike can cost very different amounts. Here are the factors that move the number, so you can ask for a clear proposal and compare it with good judgment.

By Alejo García Bosio, SAFIA Solutions · 4 min read

Why there's no list price

Custom software is built around your process. That's why it isn't priced like a catalog product, but according to the work involved: which screens, which rules, which connections and which data.

Saying "I want a CRM" isn't enough to quote. A CRM for three reps who sell in a single payment is one job. One with installments, commissions on collection, role-based permissions and a WhatsApp connection is another job, even if both are called the same thing.

That's why any serious agency will want to understand your process before giving you a number. If someone gives you a fixed price without asking anything, they're most likely quoting something else.

The factors that move the cost the most

Scope: how many processes are included. Organizing only sales is not the same as adding collections, operations and finance to the same system.
Users and roles: if each person sees only their own data, permissions have to be designed, and every new role adds screens and testing.
Business rules: installments, conditional commissions, priorities or alerts. The more exceptions a process has, the more work it takes for the system to respect them.
Integrations: every connection to WhatsApp, calendars, payment providers, ads or other tools adds development and testing. It also depends on how well documented the tool on the other side is.
Data migration: moving years of spreadsheets into a new system takes time, especially with duplicate, incomplete or inconsistently entered data.
Artificial intelligence: an agent or assistant needs design, its own sources, rules so it doesn't make things up and testing with real conversations. It also has a separate monthly usage cost.
Design and user experience: a simple internal tool doesn't need the same as one your customers will use.
Testing and auditing: reviewing the system flow by flow, with data loaded and role by role, takes time. It's time well spent, but it has to be counted.

What you pay once and what you pay every month

Development is paid once, ideally in stages. But a running system has costs that continue after delivery, and it's worth knowing them from the start.

The server and database the system runs on.
Licenses for third-party tools the system uses.
AI usage, if there are agents or assistants, which grows with use.
WhatsApp Business messages, charged by country and message type.
Maintenance: fixing bugs, updating dependencies and adding improvements as the team uses it.

A good proposal separates these costs from development and tells you which ones are on your side. That way there are no surprises on the first bill.

How to lower the cost without lowering quality

Start with the most urgent problem. A small, well-executed first stage is worth more than a huge half-finished system.
Come with your process written down: who does what, in what order and with what data. It saves hours of discovery.
Clean your data before migrating it, or at least identify what can be left out.
Use existing tools for what isn't unique to your business, like the calendar or payment provider, and build custom only what sets you apart.
Decide who on your team signs off on each delivery. Quick answers avoid rework.

What to ask for in a proposal so you can compare

To compare two proposals, the total isn't enough. Ask each one to state what's included and what isn't, how it's split into stages and what gets delivered in each, which monthly costs you'll pay yourself and how a change mid-project is handled.

Also ask them to make clear who owns the code, the data and the accounts. If everything is in your company's name, the investment is yours even if you switch providers later.

If one proposal is much cheaper than another, look for what it left out: often it's testing, data migration or support after delivery.

How long it takes, and why time costs money too

Timeline and cost go together, but they're not the same thing. A project can take longer for reasons that don't depend on the agency: slow answers, data that arrives late or decisions that change halfway through.

Name one person on your side who can answer questions and make decisions.
Set aside some time each week to review what was delivered and give feedback.
Have the access credentials and the data to be migrated ready before work starts.

With that in place, each stage moves at the planned pace and the budget doesn't stretch because of waiting.

Frequently asked questions

Can you give me a rough price without a meeting?

A very wide range is possible, but it's not very useful. After a short conversation about your process, your users and the tools you use, the estimate becomes much more useful.

Is it more expensive to do it in stages?

Not necessarily. Working in stages lets you see progress often, correct course in time and pay for what's already working. What usually gets expensive is discovering at the end that something wasn't what you needed.

Does AI-assisted development make it cheaper?

It can speed up parts of the work, like writing repetitive code. But discovery, design, review and testing are still done by people, and they're a big part of the cost.