Business Systems Integration: The Run Book Is the Deliverable.
An integration is finished when a person who did not build it can run it. A run book proves that, and a replay test checks the run book.
A per-user figure is only a starting point. What you pay is set by the renewal letter, applied to a base negotiated years ago, across users nobody removed and modules nobody opens.

The NetSuite price is set by the renewal letter, not the list. The bill has four parts, the uplift moves all of them, and four questions turn the signature into a choice.
Each chapter starts the video at that point.
Search for the price of NetSuite and you will find a number per user per month, with a note that it is only a starting point. Both are true, and neither is what you pay. What you pay is set by the renewal letter that arrives every year with a percentage on it, applied to a base that someone negotiated years ago, who may no longer work for you. This video reads that letter in four parts and ends with four questions to answer before you sign it. Everything on screen is a mock demo with invented figures.
We quote no prices, because the letter is the only honest price sheet there is. The bill has four parts, and the renewal moves all of them. The first is the platform base: a licence for the core, with a discount negotiated at the original sale, and that discount decays at renewal, which is where much of the increase lives. The second is the users: a per-user charge multiplied by a count that only goes up, because nobody removes a user at renewal and the system does not remind you.
The third is the modules: inventory, revenue, multiple entities, planning, each priced separately and each bought for a reason that may no longer hold. The fourth is the uplift: a percentage written into the original contract and applied to the whole total, every year, compounding. Put together, a company that started five years ago at a figure it thought reasonable is paying a multiple of it for the same product. Be fair to the increase. It buys continuity: the system keeps running, the finance team keeps its close, the customisations keep working and the auditor sees what they saw last year.
It buys the release twice a year, and support at whatever tier is on the contract. And it buys the absence of a migration, which is real, because a migration is a project with a cost of its own. What it does not buy is capability. The functions that were missing last year are missing this year at a higher price. It does not buy back the modules you stopped using; they renew. It does not buy a better price next year, because the uplift compounds and every reflex renewal raises the base that an exit will later be priced against.
And it does not answer whether this is still the right system. The letter does not ask. Its date is the only deadline that ever does. Question one: what do we actually use. Take the module list on the letter and, for each module, name the process that would stop if it were removed. Some will have no answer. Those rows are the negotiation. Do the same with the user list, and mark the seats nobody has used. An account manager expects you not to have done either. Question two: what has the business added since the last renewal that the system does not fit.
A second company consolidated by spreadsheet. An online shop connected by re-keying. A product line costed by hand. Each one is a place where the increase pays for a system that no longer covers the business, and each is a line on the exit side of the ledger. Question three: what would the same money buy elsewhere. Not the price sheet of an alternative, but its three-year cost with the migration included. For some companies the answer is a set of connected applications with joins they own. For some it is another suite.
For some it is the same system, negotiated harder. Question four: what does leaving cost, and when would it pay back. The exit has four numbers: the licence you would save, the migration, the decision about the data, and the modules you would not replace one for one. Two of the four can be known before any vendor is in the room. Know them before the letter's date, and the renewal becomes a choice between two priced options. The most useful thing about the renewal letter is the date printed on it.
Treat the date as the deadline for having the four answers, and start ninety days before. Thirty days is enough to build the usage list and the fit list. Thirty more is enough to price the exit and the alternatives. The last thirty are the negotiation, which goes very differently when the account manager knows that the exit has a number. If the answers say stay, negotiate the increase and the unused modules with the exit number in hand, sign, and put next year's date in the calendar with the same ninety days in front of it.
If they say leave, the letter's date becomes the cutover target. Either way, the decision was made on numbers, once, and not put off at a compounding rate. To sum up. The renewal letter is the price sheet: four parts, an uplift that compounds, and an increase that buys continuity and not capability. Before you sign, list what you use, list what the business has added, price what the same money buys elsewhere, and price the exit. We are CodeStringers, a Zoho authorised consulting partner. We run the four questions as a readiness review that ends in a written recommendation, which is sometimes to stay, and we say so.
The renewal article and the one on what leaving costs are linked 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.