Somewhere in your inbox is a SYSPRO renewal notice that looks like routine paperwork. It isn't.
SYSPRO's formal notice retires the Initial and Annual License Fee model entirely and moves every customer to named-user subscription pricing -- by 31 October 2026 outside the US, 31 December 2026 in the US. If you run a shift-based manufacturing operation, the number on that renewal is not the number you're actually going to pay. And the gap between the two is exactly the kind of cost that gets signed off on because nobody stopped to model it.
Avoid the Tech Tax
Here's the mechanic that makes this renewal different from every other software price increase you've absorbed without much drama.
SYSPRO has historically licensed concurrent users -- a shared pool of seats, checked out and released as people log in and out across shifts. A 100-seat concurrent pool doesn't mean 100 employees; it routinely serves 400-800 distinct identities, because a two- or three-shift plant has multiple people rotating through the same seat over a 24-hour cycle. The new model prices per named user instead -- one license per person, whether they're on shift or not -- at roughly $75-150 per user per month.
Do the arithmetic on that gap and the "price increase" framing stops making sense. It's not a percentage bump on what you already pay. It's a change in what's being counted. A plant that priced 100 concurrent seats could be pricing 400-800 named seats under the new model -- a multiplier, not a markup.
Call it what it is: a tech tax. Not because SYSPRO is doing anything unusual for the industry -- named-user pricing is the standard model across most enterprise software today -- but because a tax is exactly what you pay for not renegotiating your position when the terms of the relationship change underneath you. Renew on autopilot, at the vendor's default terms, on the vendor's timeline, and you've paid the tax. Model your actual exposure first, and the same renewal becomes a negotiation.
The number that actually matters isn't on the notice
The instinct here is to ask SYSPRO or your reseller for "the number." Resist it until you've built your own. Two things determine your real exposure, and neither shows up on a list-price quote:
- Your true named-user count -- not your concurrent license count, and not a headcount estimate. The actual number of distinct logins touching the system across all shifts, including the accounts everyone forgets about: quality, maintenance, warehouse leads who log in twice a week.
- Your module usage -- named-user subscription pricing is frequently tiered by module access. Paying full price for a named seat that only ever touches inventory lookup is a second, quieter version of the same tax.
A SYSPRO Renewal Exposure Calculator gets you a fast, list-rate estimate in seconds. It's a starting point, not a negotiating position -- the number that actually holds up in a vendor conversation has to come from your own database, not a rule-of-thumb multiplier.
Use the Opportunity to Tool for AI
Here's the part most renewal advice misses entirely, because it treats the renewal as a defensive exercise: get the number down, sign, move on.
That's half the opportunity. The other half is that you will never have more leverage with SYSPRO, or more internal budget attention, than you have right now, during a renewal that's already forcing a conversation about cost and value. Once you've renewed quietly and the line item disappears back into the IT budget, that leverage is gone for another contract cycle -- and any AI tooling you want on top of your ERP data has to be justified as a brand-new spend, competing against everything else on next year's list.
Flip the order instead. Before you sign, ask what the renewal conversation can buy you beyond a lower number:
- Data access terms. Named-user pricing conversations are also API-access and reporting-rights conversations. If you're going to negotiate anyway, negotiate the terms that determine whether you can actually build on top of your ERP data later, not just what you pay to log into it.
- A module rationalization, not just a seat rationalization. If you're already auditing who touches what, you're one step from knowing which processes -- late-delivery attribution, inventory variance, quality holds -- are sitting in your SYSPRO data untouched by anything smarter than a scheduled report.
- A negotiated multi-year term that funds the AI layer instead of the seat count. A vendor that's already at the table to discuss a multi-year subscription is more willing to flex on structure than a vendor you're calling cold in month eleven of a twelve-month term.
None of this requires replacing SYSPRO. It requires treating the renewal as the one moment your ERP relationship is actually up for discussion, and using it to fund the layer that turns your existing SYSPRO data into something that flags a cost overrun, a late-delivery pattern, or a margin drift on its own -- instead of waiting for someone to run a report.
Is switching actually worth it?
Some plants searching their way into this renewal are really asking a different question: should we just replace SYSPRO. It's a fair question to ask honestly, not just to use as negotiating leverage with your current vendor.
The honest answer is that it depends on a comparison almost nobody actually runs: a real 5-year stay-vs-go number, built from your own usage data, not a vendor's pitch deck or a generic ERP-alternatives listicle. Migration cost, data-conversion risk, and retraining time are real and usually underestimated on the "go" side; the compounding named-user tax is real and usually underestimated on the "stay" side. Whichever way that comparison lands, it should be the thing that decides -- not renewal-notice anxiety, and not switching for its own sake.
What You Can Do Now
Two things you can do this week, before the renewal deadline forces the decision for you.
Run your seat count through the SYSPRO Renewal Exposure Calculator to get a fast, list-rate read on where you land under named-user pricing. Then decide whether you want the real number: a read-only connection to your own SYSPRO environment gets you an actual named-vs-concurrent exposure figure, a module usage breakdown, and a 5-year stay-vs-go comparison -- free, delivered in days, no sign-up required to start.
Request your free Renewal Exposure Report and go into the renewal conversation with your own number, not SYSPRO's.
More on the operations side of what your ERP data can already tell you: see our guide on on-time delivery root-cause attribution, or browse the full Business Solutions library.