How much does custom software cost? Typical ranges and timelines

Short answer: a simple custom tool usually costs tens of thousands of reais, a mid-size management system goes past R$ 100,000, and a broad platform with many integrations and user roles reaches several hundred thousand. A first, lean version takes about 2 to 4 months; larger systems take 6 months or more. Anyone quoting a fixed number without understanding your process is guessing.

A note on honesty. The ranges here are market estimates, the kind people use in first conversations, and they vary with scope. They are not a Wyber price list and not the result of a published study. All amounts are in Brazilian reais (R$), and rates vary a lot between markets. Use them to get the order of magnitude before you ask for quotes.

What you are actually paying for

You pay for the time of skilled people: understanding your process, designing, building, testing, and putting it live. Almost all the cost of custom software is working hours. Tool licenses and servers weigh very little next to that.

That is why price follows the size of the scope, not "how advanced the technology is". A system with 15 simple screens and one with 15 screens full of business rules are very different things, even though the screen count is the same.

Typical ranges by size

The table below collects what is commonly heard in the Brazilian market for small and mid-size companies. Typical ranges, they vary with scope.

Three honest readings of this table:

• The ranges are wide on purpose. Two "similar" projects can land at opposite ends because one involves tax rules and the other does not.
• Cost and time do not trade one-for-one. Doubling the team does not halve the timeline, because part of the work depends on your decisions, on data only you have, and on validation by the people who will use it.
• The first version is almost never the whole system. The safest path is to build the core, put it into use, and grow with what real operation teaches you.

What pushes the price up

If you can answer each of these before asking for a quote, the estimate you get will be far more accurate.

Number of roles and permissions

A system where everyone sees everything is cheap. When finance sees amounts, sales only sees their own customers, and a manager approves exceptions, every rule becomes a screen, a test, and something to maintain.

Integrations

Connecting the system to your bank, invoicing tool, WhatsApp, an ERP you already use, or your website is where most time gets lost, because it depends on third-party systems with uneven documentation and changes you do not control. Each significant integration is usually a separate line in the quote.

Business rules

Tiered commissions, late-fee calculations, discounts by contract, deadlines by customer type. A rule that takes one sentence to say can take days to build and test. The more exceptions, the more hours.

Data migration

Bringing ten years of spreadsheets and duplicated records into a new system is usually harder than it looks. Dirty data does not migrate itself: someone has to decide what is worth bringing over.

Reports and dashboards

A simple report is cheap. A dashboard with filters, comparisons, and export in the format your accountant wants is a small project. For each indicator, ask: who uses it, and which decision does it change?

Design and ease of use

Internal tools have users too, and users who hate the tool go back to the spreadsheet. Design time is not a luxury, but it can be sized to the project.

Security, audit, and data protection

If the system stores personal data, it needs to record who accessed what, allow data deletion, and have backups that are actually tested. This is standard, but it takes work.

Costs that remain after delivery

The build budget is only part of the bill. Once the system is live, you also have:

• Hosting and services: server, database, transactional email, domain, monitoring. For a small company this is typically a few hundred to a few thousand reais a month.
• Maintenance and evolution: fixes, security updates, and adjustments operations will ask for. A common rule of thumb is to set aside 15% to 20% of the build cost per year.
• Support: who answers when something breaks on a Monday morning.

Always ask the company quoting you what it costs to maintain and what happens if you want to switch vendors. It is one of the questions in our checklist for choosing a software house.

How the contract model changes the price

There are, broadly, two ways to charge: fixed scope (agreed price and deliverables) and time and materials (you pay for time, with priorities set along the way). Fixed scope gives predictability but requires a well-defined scope and usually includes a margin for the vendor's estimation risk. Time and materials is flexible but requires you to follow the work closely. As a market reference, the hourly rate of a Brazilian software house sits in a wide band, roughly R$ 120 to R$ 250 per hour depending on seniority.

A worked example (illustrative, not a client)

Picture a company with a team of 8 that tracks orders, deliveries, and payments across three spreadsheets. It wants a system with customer records, orders, delivery status, billing, and a monthly report. No tax integration in the first phase.

• A 1 to 2 week discovery defines the scope and screens.
• The first version covers orders, deliveries, and billing, with one payment integration.
• Left for phase two: advanced reports and a customer portal.

That falls into the first version (MVP) row of the table, with an expected timeline of 2 to 4 months and delivery every two weeks. This example was made up to illustrate the reasoning. It does not describe a real client and does not promise a price.

How not to blow the budget

1. Start with a discovery. A few weeks of investigation to define what is in and what is out cuts the risk of rework.
2. Cut scope, not quality. A system that does three things well beats one that does ten halfway.
3. Prioritize by pain. Start with the process that costs the most money or time today.
4. Have one owner on your side. Projects slip when nobody decides. One person who can say yes or no within two days is the best saving there is.
5. Ask for short deliveries. Seeing the system working every two weeks avoids the surprise of finding out at the end that it was not what you meant.
6. Ask for the three-year cost, not just the build cost.

Frequently asked questions

Why won't anyone give me a fixed price in the first conversation?

Because price depends on scope, and scope only appears once someone understands your process. A vendor quoting without asking anything is estimating blind and will adjust later, usually upward.

Is custom software always more expensive than off-the-shelf?

At the start, almost always. Over a few years it depends on the number of users, how much you have to bend the off-the-shelf tool, and how different your process is from the standard one. We run that math in custom software, SaaS, or ERP: how to decide.

Can I start smaller and grow?

Yes, and it is what we recommend. The first version covers the core of the process and grows as real use shows what is missing.

Do I own the code?

It should be agreed in the contract, in writing, before work starts. An evasive answer is a warning sign.

Next step

If you already have a process in mind, tell us what it does today and where it gets stuck. From that conversation we will tell you whether custom software makes sense, what the first version would be, and a range that fits your case.

Tell us what you need