The $129 Renewal: What a NetSuite Price Rise Buys You, and What It Does Not.
Updated: 3 days ago
Search for NetSuite pricing and you will find a number per user per month, and a note that the number is a starting point. Both are true and neither is what you pay. What you pay is set by the renewal letter, which arrives every year with a percentage on it, and the percentage applies to a base that was negotiated years ago by someone who may no longer work for you, across modules some of which you may no longer use.
The renewal letter is the only honest NetSuite price sheet you will ever see. This post is about how to read it: what the increase buys, what it does not, and the four questions to answer before signing it because the alternative seemed like too much work. It is not a price list. Vendors publish those, and they are not the number.
How the number is actually built.
A NetSuite bill has four parts, and the renewal moves all of them.
The platform base. A licence for the core, priced at the edition you started on, at a discount negotiated at the original sale. That discount decays at renewal, which is where much of the increase lives.
The users. A per-user figure, on the price sheet somewhere in the range everyone quotes, multiplied by a count that only goes up, because nobody removes users at renewal and NetSuite does not remind you to.
The modules. Advanced inventory, revenue management, OneWorld, planning, the industry editions. Each one priced separately, each one subject to the uplift, and each one bought for a reason that may or may not still hold.
The uplift. A percentage applied to the total at each renewal, agreed in the original contract, and in the contracts we have seen for mid-market companies, higher than inflation and compounding.
Put those together and a company that started five years ago at a figure it thought reasonable is paying a multiple of it, for the same product, with more users than it needs and modules it has stopped using. That is not a scandal; it is how enterprise software is priced. It is also why the renewal letter, and not the price sheet, is the number to reason about.
What the increase buys.
Be fair to it. The uplift buys continuity: the system keeps running, the finance team keeps its close, the customisations keep working, the auditor keeps seeing what they saw last year. It buys the twice-yearly release, which for most customers is neutral and occasionally useful. It buys support at whatever tier is on the contract. And it buys the absence of a migration, which is a real thing to buy, because a migration is a project with a cost of its own; we wrote what leaving actually costs and it is not small.
For a company whose business has not changed and whose NetSuite instance still fits it, that is a fair trade, and the honest advice is to negotiate the percentage and sign.
What the increase does not buy.
It does not buy capability. The functions that were missing last year are missing this year at a higher price. If the business has grown a second entity, a new channel, a new product line or a new way of working since the last renewal, the system fits it less well than it did, and the uplift does nothing about that.
It does not buy the modules you stopped using back. They renew. A module nobody has opened for two years is on the letter at this year's percentage, and removing it is a negotiation, not a checkbox.
It does not buy a better price next year. The uplift compounds, so every year of signing by reflex raises the base that the exit, if it ever comes, will be priced against. This is the quiet cost of the reflex renewal: the longer the decision is deferred, the more expensive both staying and leaving become.
And it does not buy the answer to whether the system is still the right one. That is a question the letter does not ask, and the letter's date is the only deadline that ever forces it.
The four questions to answer before signing.
One: what do we actually use.
Take the module list on the letter and, for each one, name the process that would stop if it were removed. Some will have no answer. Those are the negotiation. Take the user list and do the same. Both lists are the first thing a NetSuite account manager expects you not to have done.
Two: what has the business added since the last renewal that the system does not fit.
A second entity that is consolidated by spreadsheet. A shop that is connected by re-keying. A product line costed by hand. Each is a place where the uplift is paying for a system that no longer covers the business, and each is a line on the exit side of the ledger.
Three: what would the same money buy elsewhere.
Not the price sheet of an alternative; the three-year cost of one, with the migration included. We wrote an honest comparison of the alternatives for exactly this question, and the answer depends more on question two than on any licence figure. For some companies the alternative is a set of connected applications at a fraction of the licence with joins they own; for some it is another suite; for some it is NetSuite, negotiated harder.
Four: what does leaving cost, and when would it pay back.
A companion post, What Leaving NetSuite Actually Costs, walks the four numbers: the licence you save, the migration, the data decision and the modules you will 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 decision between two priced options rather than a signature under time pressure.
Using the letter's date.
The most useful thing about the renewal letter is that it has a date on it. Treat the date as the deadline for having the four answers, and start ninety days before it. Thirty days is enough to build the usage list and the fit list. Thirty more is enough for an ERP Readiness Review to price the exit and the alternatives. The last thirty are the negotiation, which goes very differently when the account manager knows the exit has a number.
If the answers say stay, negotiate the uplift and the unused modules with the exit number in hand, sign, and put the next letter's date in the calendar with the same ninety days in front of it. If the answers say leave, the letter's date becomes the cutover target, or the last renewal at a reduced scope while the move happens. Either way the decision was made on numbers, once, rather than deferred at a compounding rate.
How we approach it.
We run the four questions as an ERP Readiness Review, a few days that end with a written recommendation: stay and negotiate, stay for one more term while the move is built, or leave now. The recommendation is sometimes to stay, and we say so. Where it involves building anything, it comes with a guaranteed estimate. We do not own your renewal decision; you do. We are accountable for the numbers on both sides being right before the letter's date.
The short version.
NetSuite pricing is the renewal letter, not the price sheet: a compounding uplift on a base set years ago, across users nobody removed and modules nobody opens. The increase buys continuity and not capability. Before signing, list what you use, list what the business has added that the system does not fit, price what the same money buys elsewhere, and price the exit. Use the letter's date as the deadline. Sign on numbers, or leave on numbers, and never renew by reflex.
Know whether your business is ready for an ERP before you sign for one.
The ERP Readiness Review is a 90-minute working session plus a written scorecard across master data quality, documented exceptions, integration scope and data ownership. Fixed scope, no obligation. Or see how we approach it.
More on the same problem:
Comments