How much does a custom management system cost in 2026?

A custom management system has no list price: it costs the hours of work it takes to build, plus what it costs to keep running afterwards. Those hours depend on how many different tasks it has to handle, how many people use it with different permissions, which other programs it has to connect to and how much data has to come over from today's spreadsheets. As a reference for what those hours are worth: in 2026, the median gross salary of a mid-level developer employed full time in Argentina is ARS 2,850,000 a month, according to the sysarmy survey.

"It depends on the scope" is true and useless when you're trying to find out whether this fits your budget. So let's take it apart: what pushes the number up, what an hour of development is worth today, and why the cheapest quote often ends up being the most expensive.

What does the price of a custom system depend on?

Almost every software quote is hours times the hourly rate. The rate varies little between similar vendors; the hours vary enormously with what you ask for. These are the six things that move them most:

What	Why it adds hours	The question to ask yourself
Different tasks	Each workflow (orders, stock, collections, purchasing) is a new part of the system	Which workflow hurts most today?
Types of user	Each role sees and does different things, and that has to be built and tested	Who enters data, who approves and who only looks?
Connections to other programs	Invoicing, the bank, an online store: each has its own rules and failures	What does it have to talk to from day one?
Data to migrate	Old spreadsheets have duplicates, mixed formats and gaps	How many years of history do you need inside?
Reports	Each new report is a query that has to be designed and checked	Which numbers do you look at every week?
Use from a phone or outside the office	Screens that adapt, secure access from anywhere	Will anyone use it on the road or in the warehouse?

If you show up with those six answers written down, you already have half of a serious request for a quote.

What does a developer earn in Argentina today?

The most solid reference is the sysarmy salary survey↗ (opens in a new tab), published in March 2026 with 4,939 valid responses. From its public dataset, counting only people who work as developers, full time and on payroll, the median gross monthly salary comes out like this:

Experience	Gross monthly salary (median, ARS)	Responses
Junior	1,692,500	114
Mid-level	2,850,000	423
Senior	3,900,000	524

It's my own calculation on the 2026.1 dataset. It's useful for two things.

First, it's the floor of what an hour of good work costs. An outside vendor charges that plus taxes, tools, unbilled time and margin. If a quote is far below what it would cost to have that person on your own payroll, ask what isn't included.

Second, it lets you compare with hiring someone yourself. On top of the salary come payroll taxes, the time it takes to find the person and the risk that they leave with everything about the system in their head. And a management system is rarely handled by a single person with a single skill set.

Why does the cheapest quote often end up the most expensive?

For a long time I thought technical difficulty set the price. What sets it is whatever isn't clear.

The Standish Group's CHAOS report↗ (opens in a new tab), the reference measurement of software projects since 1994, found in its first edition that only 16.2% of projects were delivered on time and on budget, that 31.1% were cancelled before completion, and that the ones delivered with problems cost on average 189% of the original estimate: nearly double.

That overrun is almost never because someone lied. It shows up because a request that wasn't defined got quoted, and what was missing is discovered halfway through, when there's no cheap way left to solve it. The same report lists as the top success factors the involvement of the people who will use the system (15.9% of responses), support from management (13.9%) and clear requirements (13.0%). None of the three is technical.

The lowest of three quotes is sometimes just the one that asked the fewest questions.

Fixed price or paying by the hour?

It depends on how much you know about what you want. The three most common arrangements, compared:

Arrangement	When it fits	The risk
Fixed price for the whole project	The request is written in detail and won't change	Whatever wasn't written gets billed separately, or done badly to avoid losing money
By the hour	Scope changes often and you want full flexibility	You don't know what you'll spend until the end
Fixed price per stage	You know what you want first and the rest will become clearer	You have to decide at the end of each stage, and that takes your time

I work with a fixed price per stage because it spreads the risk: each stage delivers something you use, and when it ends you decide whether to continue, change course or stop. It's what the CHAOS report calls smaller project milestones, and it's no accident that it shows up among its success factors.

What does a system cost after it's delivered?

The build quote isn't the total cost. Once the system is running, some costs keep coming:

• Where the system lives: the service it runs on is paid every month, and grows with data and users.
• Adjustments: the business changes, new requests appear, and something that doesn't matter today will tomorrow.
• Support: someone has to respond when something fails or a new person joins the team.
• Security updates: a system nobody touches for two years becomes fragile.

Always ask what it costs per month to keep it running and who handles each of these. Also ask where the code lives: if it sits in an account of yours, you can change vendors without starting over.

How do I ask for quotes I can compare?

Send everyone the same request, in writing, and ask for answers that cover these seven points:

1. What each stage includes and what you'll be able to use when it ends.
2. How many hours they estimate per stage and at what rate.
3. Whether migrating your current data is included, and how far.
4. Whether training your team is included.
5. What it costs per month to keep it running, and who pays.
6. How changes you ask for midway are priced.
7. Where the code lives and in whose name.

If an answer is missing one of those points, don't discard it: ask them to complete it. How they answer also tells you how they'll work.

If a quote arrives as a single total, ask for it to be split into stages that each deliver something usable. If no stage can be used before the two-month mark, the project is split wrong and you're the one paying for the risk.

What were you quoted last time, and what was left out of the quote? Reply with the details and I'll tell you what I'd ask the vendor.