Why the same request can cost five times more.

You asked three places to quote the same thing and got back three numbers that look nothing alike. One said three thousand dollars, another eight, another twenty. The natural reaction is to assume someone is taking you for a ride.

It almost never is. What happens is that when the request isn't defined, everyone quotes the project they pictured. And since nobody pictures the same thing, the numbers can't match.

The good news is that price isn't a mystery. It comes down to four concrete things, and three of them depend on you, not on the supplier.

1. How much is decided before starting

This is the heaviest factor by far.

If you can walk through the whole process — what comes in, who checks it, where it's recorded, how it ends — the supplier quotes work. If you can't, they quote work plus the uncertainty of discovering it along the way. Nobody will tell you "I added forty per cent because I'm not sure what you want", but it's in there.

And the one who quoted lowest often wasn't more efficient, just more optimistic. You'll pay the difference later, when what nobody discussed shows up.

2. How many exceptions your process has

A system that does one thing the same way every time is cheap. Exceptions are what make it expensive.

"Orders come in here" is simple. "Orders come in here, except the three big accounts that email them, and the ones from out of province with a different price list, and the end-of-month ones that get invoiced differently" is four systems in one.

Every exception sounds small when you say it out loud. In the project, each one is another branch to build, test and maintain forever.

3. What it has to connect to

Connecting to something that already exists can be trivial or it can be half the project, and from the outside they look the same.

If the other system is well known and has a supported way in, it's days. If it's old, or custom-built by someone who's long gone, or if the only way to get the data out is exporting a spreadsheet by hand, that's where the quote jumps. Not out of greed: because there's a problem nobody documented.

When you ask for a quote, always say what it has to integrate with. It's the detail that moves the number most and the one people most often forget to mention.

4. Who decides on your side

This appears in no quote and it sets the real cost of the project.

If one person decides and is available, questions get resolved same-day. If every definition needs a meeting with three people whose calendars never align, the project stretches — and time is exactly what you're paying for.

It doesn't have to be the owner. It has to be someone with the authority to say "do it this way" without checking first.

What the numbers mean

For reference: in Argentina, development hours run between 20 and 60 dollars depending on experience, and custom software for a small business lands in a wide band, one to twenty thousand dollars, by size.

That band is enormous for the same reason we've been discussing. There's no price for "a system" any more than there's a price for "a house".

What you can do is read quotes differently. The number on its own says nothing. What says something is what each supplier assumed to reach it. If a quote doesn't spell out what's included and what isn't, you aren't comparing — you're guessing.

How to actually pay less

This is the most useful thing I can tell you and it doesn't help me: the project gets cheaper before it starts.

Write down how it's done today. List the exceptions, including the ones that feel obvious. Name the person who decides. Say what it has to connect to.

Do that and three things change on their own. Quotes become comparable, because everyone is pricing the same thing. They come down, because nobody has to hedge against the unknown. And you can start with the part that hurts most instead of buying everything at once.

Whoever shows up with the process written down pays less. Every time.

If you'd like, we can have that conversation at no cost. Sometimes it ends in a quote, and sometimes in "you don't need this yet."