Almost every software project that goes wrong looked fine on the day it was signed. There was a well-presented proposal, a reasonable price and a date. Six months later the date has moved twice, the budget has grown and the plant is still running on the spreadsheet.
It is not bad luck. A University of Oxford study of 1,471 technology projects found an average cost overrun of 27%. The serious part was in the tail: one in six projects ran over budget by 200% on average, and over schedule by almost 70%. Nobody signs thinking theirs will be that one.
The good news is that almost everything that leads a project to end that way can be seen before you sign. Not in the vendor’s presentation, which always goes well, but in what they agree to put in writing.
What costs the most is not in the quote
There are three traps that keep coming back, and none of them shows up in the price.
Paying a lot before seeing anything. If the first thing you can touch arrives in month four, you have spent four months paying for an idea. And when you finally see it, any misunderstanding costs four months of work, not a week.
Changes without a price. Every project changes, because once the plant floor sees the system, people discover what they really need. If the contract does not say how a change is quoted, every change is a negotiation, and you negotiate it when you can no longer walk away.
Code that is not yours. In Mexico, Article 83 of the Federal Copyright Law says that, unless agreed otherwise, whoever commissions and pays for a work holds the economic rights to it. That sounds like you are covered. But Article 83 bis adds that, for a work to count as commissioned, the terms of the contract must be clear and precise, and that in case of doubt the interpretation most favorable to the author prevails. The author, here, is the vendor. A vague contract does not protect you: it protects whoever wrote the code.
In practice you find this out the day you want to change vendors, or the day the vendor disappears: you have a system that works and that nobody else can touch. We have already written about what happens when you inherit software nobody documented. It almost always starts with a contract that did not say who owned the code.
Seven things to get in writing
1. Something you can test before the big payment
There is one question: what will I be able to open and use, with my own data, and in how many days? Not a presentation or a design in pictures. A screen that works with your part numbers, your customers and the way you operate.
If the vendor cannot show you anything concrete in the first weeks, they will not be able to later either. And by then you have paid.
2. Short deliveries you can review
Ask for deliveries every two or three weeks, each with something that works, not a progress percentage on a chart. A project’s risk grows with the time that passes without anyone from your plant seeing the system. With short deliveries, a misunderstanding costs two weeks, not six months.
And tie payments to those deliveries, not to the calendar.
3. A price by scope and a rule for changes
A fixed price per module or per stage tells you how much you will pay and for what. An hourly rate with no cap tells you what an hour costs. Both can make sense, but only one lets you budget.
The most important part is the rule for changes: how one is requested, how it is quoted, and that it is not done until you approve it in writing, with its price and its effect on the date. Changes are not the problem. Changes without a price are.
4. The code is yours, and the contract says so
Given what the law says, this cannot be left implicit. The contract should state in plain words that the economic rights to the source code and its documentation are yours, or that the vendor assigns them to you, as each delivery is paid. And you should have access to the repository from day one, not “at the end of the project”.
Watch for a common variant: “the system is yours, but the code is ours and we grant you a license to use it”. Sometimes that is reasonable, when the vendor has a product it adapts for each client. But then you are not buying custom software, you are renting one, and it is worth knowing that before you sign.
5. The names of the people who will do the work
“A team of experts” is not an answer. Ask who will design, who will write the code, who will answer you when something breaks and who makes the technical decisions. And have the contract say what happens if that person leaves the project.
Much of what convinces you in the sales meeting lives in people who are not always the ones who later do the work.
6. The exit door
Ask what you get if the relationship ends, for whatever reason: code, database, documentation and access, and within how many days. And make sure the cloud accounts, the domain and third-party services are in your company’s name, not the vendor’s. If everything lives in the vendor’s account, your exit depends on their goodwill.
A vendor who trusts their work has no problem signing this. The one who gets uncomfortable is telling you something.
7. What happens the day after
Before you sign, get three answers: how long they fix bugs at no cost after delivery, what support costs after that and how fast they respond, and how much you will pay each month for servers, database and services to keep the system running.
That last number is almost never in the quote, and it is the one you will pay every month for as long as the system exists.
Five signs to get up from the table
- They cannot show you anything working until the end.
- The largest payment comes first.
- “The code is ours”, or “we will figure that out later”.
- They will not commit to dates, not even for the first delivery.
- Nobody talks about what happens once the system is in production.
This is not legal advice: a software contract is reviewed by your lawyer. What we can tell you is what to ask before it reaches their desk.
How we do it
It is fair for you to ask us the same questions. At Nori.mx the first step is a twenty-minute video call. Then there is a prototype you open on your phone and test with your own data, and if it does not convince you, it stays there. After that we deliver something you can review every two weeks, we quote by module, changes are approved in writing and the code is yours from the contract.
If you have a proposal on the table, compare it against this list, ours included. You can book the call whenever you like. And if you are not yet sure what system you need, Chira asks about your operation and tells you, in writing, what comes first.
References
- Ley Federal del Derecho de Autor (Mexican Federal Copyright Law), Chamber of Deputies — the current text, last amended on May 14, 2026. Articles 83 and 83 bis cover commissioned works; Articles 101 to 103 cover computer programs and their documentation (in Spanish).
- Why Your IT Project Might Be Riskier Than You Think, Flyvbjerg and Budzier, University of Oxford — the analysis of 1,471 technology projects: an average cost overrun of 27%, and one in six with a 200% cost overrun and an almost 70% schedule overrun. It is the open-access version of the article published by Harvard Business Review.