Two estimates arrive for the same operations system, the kind most people call an enterprise resource planning system. One is for a hundred and forty thousand dollars.
An estimate for an operations system is read by its ratios, not its total: hours on process design and data against hours on configuration and licences. A quote whose largest line is the licence is a quote for a system nobody designed, and the ratios tell you which partner understood the business.
Each chapter starts the video at that point.
Two estimates arrive for the same operations system, the kind most people call an enterprise resource planning system. One is for a hundred and forty thousand dollars. The other is for two hundred and ten. Most buyers read the totals, feel the difference, and start negotiating with the cheaper one. That is the wrong first read. The total tells you what the partner wants to charge. The ratios inside it tell you what the partner thinks the work is, and that is the thing you are actually buying. This video reads two mock estimates by their ratios, so you can do it with the real ones on your desk.
Everything on screen is a mock demo with sample numbers; the partners and the quotes are invented. Six minutes. Every estimate for an operations system has the same five kinds of line, whatever it calls them. Licences, what the software costs per user per year. Configuration, the hours to set the software up. Data, the hours to clean, map and move what you have. Integration, the hours to connect it to the systems that stay. And process design, the hours spent deciding how the business will actually run inside it before anyone configures anything.
The first two are easy to estimate and easy to compare, which is why they are usually at the top and usually the biggest numbers. The last three are the ones that decide whether the system works. So the first thing to do with a quote is to sort its lines into those five buckets. Ten minutes with a highlighter. Then look at the shape, not the sum. Here is the first mock estimate, from a partner we will call Harbor Systems. A hundred and forty thousand. Sixty-two of it is licences.
Fifty is configuration. Data is eighteen. Integration is ten, one line, one system named. Process design is not on the quote. Read the ratios. Licences and configuration are eighty percent of the total. Data, integration and design together are twenty. This partner is quoting to install the software. They have assumed your processes fit the product's defaults, your data is clean, and the two other systems you run will connect themselves. It is not a dishonest quote. It is a quote for a company that does not exist, and the difference will arrive as change orders in month four.
The second estimate, from a partner we will call Meridian Works. Two hundred and ten thousand. Licences, sixty-two, the same software. Configuration, forty. Data, thirty-eight, with a line for a reconciliation of the customer and item lists before migration. Integration, thirty-five, three systems named with the direction of each connection. Process design, thirty-five, four workshops and a written exception list. The ratios flip. Licences and configuration are under half. Data, integration and design are the majority, and every one of them names a thing the partner found by looking at your business rather than at the product.
This quote is seventy thousand more. It is also the only one of the two that priced the work that fails when it is not done. Whether it is worth seventy thousand more is a real question. Whether it describes the real project is not. Once you can see the shape, three questions follow, and they are worth more than any negotiation on the total. To the cheaper partner: where is process design, and what happens when our order process does not match the default? If the answer is that it will be handled in configuration, the configuration line is about to double.
To the more expensive one: show me the exception list from the workshops, and tell me which of the three integrations you have built before. If they can show both, the premium is the cost of someone who has done this. If they cannot, the premium is a guess with better formatting. And to both: when the estimate turns out to be wrong, who tells us, when, and what does it cost to change course? That question is its own video, and it is the next one to watch. Across the implementations we have delivered and the ones we have been asked to rescue, the pattern is the same.
The projects that run over are not the ones with the highest totals. They are the ones where design and data were under a quarter of the estimate, because the missing work was still done, late, by the client, during the cutover. Zoho's own operations system is committed to the United States but not yet evaluable here, so for most operators this year the estimate on the desk is for something else, or for the interim architecture that gets ready for it. The ratios read the same way in either case.
A quote that spends its hours understanding your business before it configures the product is the quote that describes the project you will actually have. So read the ratios before you read the total. Sort the lines into the five buckets, see whether design and data are a fifth of the quote or half of it, and ask the three questions. Then, and only then, negotiate. If you would like a second pair of eyes on the estimates you have, the ERP Readiness Review is a ninety-minute working session and a written scorecard, and reading your quotes is part of it.
We are CodeStringers, a Zoho authorised consulting partner. The link is below.
We design, build, integrate and operate AI-driven, platform-agnostic integrated business solutions for operationally complex companies. Start with a conversation; we will tell you if we are a fit.
