A manufacturer we work with was paying for 11 NetSuite seats that nobody had logged into since spring. Paid in full, every month, the whole time.
Nobody was being careless. Nobody had missed a warning, because there wasn't one. The seats didn't flag themselves, the invoice didn't itemize them, and the renewal total looked close enough to last year's that it went through on the first approval.
The controller who eventually found it wasn't hunting for waste. She was pulling a user list for an unrelated access review and noticed the same four names she had removed from payroll the previous year.
That's the pattern worth understanding and it's why this article exists. Most NetSuite waste isn't buried somewhere complicated. It's sitting in plain view on a document you look at once a year, in a format that was never designed to show it to you.
There's a second thing going on too. Every one of these costs is somebody's job to notice, and in most companies that somebody is the person with the least time to look. The NetSuite admin is fielding tickets. The controller is closing the month. Procurement sees a renewal that matches last year's and approves it because a renewal matching last year's is exactly what a well-run system looks like from the outside.
Here are five of them, why each one stays invisible, and how to check for it yourself.
What the cost of bad NetSuite support actually looks like
The phrase sounds like it should describe a support desk that misses its SLA. In practice the cost of bad NetSuite support almost never shows up as a missed ticket. It shows up as an ERP system that quietly stops matching the business it was configured for and a bill that doesn't change to reflect it.
The mechanism is simple: good support notices drift. Nobody is tracking whether seat count still matches headcount, if the modules you bought are switched on, whether roles still map to real people, or if last year’s workaround has become this year’s procedure. Support that only answers tickets will never catch these things because nobody files a ticket for a problem they can’t see.
Comparisons of NetSuite support options tend to make the same point from the other direction: poor support introduces both direct financial costs and a set of hidden ones, and the hidden ones usually dominate. The costs inflate most when the level of support is misaligned with the operational complexity of the environment it's meant to cover. A twelve-user business on core ERP with three customizations needs very little. A company with multiple subsidiaries, multiple entities and a decade of advanced configuration needs someone whose job is to look. And when it doesn't have one, the gap turns up as downtime, rework, audit findings and emergency consulting rates.
That's the frame for everything below. None of these five is a support failure in the sense anyone would file a ticket about. All five are things that only get found when somebody looks and looking is the part nobody is contracted to do.
1. Seats nobody logs into
What it is. Licenses assigned to people who left, changed roles, or were provisioned for a project that ended. Every one bills at full rate until somebody removes it.
Why you don't see it. Offboarding usually means revoking access, which is a security task. Releasing the license is a procurement task. Those are two different jobs, often owned by two different people, and only one of them is urgent. The account gets disabled the day someone leaves, because leaving an active login for a departed employee is a real risk somebody will get blamed for. The seat keeps billing, because nobody gets blamed for that.
Growth makes it worse. Companies scaling through a busy year provision generously, because the cost of a blocked new hire on day one is obvious and the cost of an extra seat is not. Then hiring slows, or a team reorganizes, or a project wraps, and the provisioning never runs in reverse. License counts are a ratchet in most organizations. They only go one way, which is why a deliberate approach to optimizing your NetSuite environment without disrupting daily operations matters more than it seems.
The numbers make the ratchet expensive. Full user licenses are commonly quoted between $99 and $399 per user per month depending on edition and negotiation, so eleven dormant seats is a five-figure annual number that appears nowhere as a line item called "waste." Licensing costs are also the part of your bill with the least natural downward pressure, since nothing in the contract prompts a review.
How to find it. Run a saved search on employees with a last-login date older than 90 days, then compare it against your current license count. The gap is your answer, and it takes about ten minutes.
Two refinements make it more useful. First, split the results by role, because a dormant full user costs meaningfully more than a dormant employee-center login and the difference tells you where to start. Second, run it against your active employee list from HR rather than against NetSuite's own employee records, since the employee record is often the thing nobody updated in the first place.
Do this before renewal rather than after. Once you've signed, the seats are yours for another term regardless of what the search says. Contracts usually run one to five years with an annual uplift in the 3% to 10% range, which means a seat you don't catch this year gets slightly more expensive every year you keep not catching it.
2. Additional NetSuite modules you bought and never switched on
What it is. Functionality that was scoped during implementation, priced into the contract, and never configured. Advanced revenue management, demand planning, a warehouse module bought for a location that never opened.
Why you don't see it. It was justified once, in a business case that made sense at the time. Then implementation ran long, the module got pushed to phase two, and phase two got quietly folded into "later." The line item survived the schedule change.
What keeps it invisible after that is a kind of institutional politeness. Canceling it means saying out loud that a decision made by people still in the building didn't work out. Nobody circles back to a decision that was already approved, especially when the approver is in the room. So it renews, and each renewal makes it slightly harder to raise, because now you're also asking why nobody raised it last year.
There's a variant of this worth watching for: modules that are switched on and half-configured. Somebody enabled the feature, built two of the six workflows it needed, hit something hard, and stopped. The module is technically in use, so it never shows up as unused, but the team still does most of the work by hand. That one costs you twice, once on the invoice and once in the hours.
How to find it. Pull your subscription list and put it next to your enabled features. Anything you're paying for that isn't switched on is either a cost to cut or a project to actually finish. Both beat the current state, which is paying for the option and using neither.
For anything on the list that is switched on, ask the team that owns it a simpler question: are you using this, or are you exporting out of it? The answer takes ten seconds and it separates the modules that are working from the ones that are decorative, and it usually surfaces the areas where a structured NetSuite health check and configuration audit would have the biggest impact.
3. Hours that expired at quarter close
What it is. Support hours allocated quarterly under a contract that doesn't roll them over. Use them or lose them, and most quarters you lose some.
Why you don't see it. The loss never appears as a loss. There's no line reading "18 hours forfeited." The invoice is identical whether you used all of them or none, which means the money you wasted looks exactly like the money you spent well.
The rhythm of a quarter makes it worse. Hours go unused in January and February because nothing is on fire, then March arrives with a close, an audit request and a release all at once, and suddenly you need more hours than you have. The pattern repeats every quarter: a shortage at the end, a surplus at the start, and a reset in between that throws away the surplus rather than carrying it into the shortage.
Teams adapt to this in ways that cost them more. They hold small issues back to bundle them into a bigger request, so a two-hour problem sits open for six weeks. Or they burn hours in the last two weeks on work that wasn't a priority, purely to avoid forfeiting them, which converts wasted money into wasted money plus wasted attention — the opposite of what you get with consistent, reliable NetSuite support from a specialist team.
Worth noticing: This cost has an incentive attached. A quiet quarter is a profitable one for whoever wrote the contract. Nothing in that arrangement encourages anyone to help you need fewer hours.
How to find it. Ask your provider for hours consumed against hours allocated for the last four quarters. If they can't produce it quickly, that itself tells you something. Multiply the shortfall by your hourly rate and you have a number worth bringing to the renewal conversation, and a straightforward question to go with it: what would this contract look like if the hours carried over?
4. Roles and permissions built for people who left
What it is. Custom roles created for a specific person, cloned for the next person, then cloned again. Three years on you have a permissions structure nobody designed and nobody can explain.
Why you don't see it. This one doesn't cost you on the invoice at all, which is exactly why it survives. It costs you an audit, when somebody asks who can approve a journal entry and the honest answer takes two weeks to assemble. It costs you again every time a segregation-of-duties question turns into an investigation.
It also costs you in caution. When nobody's certain what a role touches, changing it feels dangerous, so requests for access get handled by cloning an existing role and adding to it. That's how you end up with a structure that only ever accumulates. Each clone is the safe choice at the moment and the expensive one over three years.
The bill usually arrives at the worst possible time. Nobody schedules the discovery that permissions are a mess. It surfaces during an audit, during diligence, or during the week a new CFO asks a reasonable question and gets an unreasonable answer. Configuration failures left unaddressed are a well-worn route to compliance penalties and inaccurate financial data, and the operational risk compounds the longer the structure goes unexamined.
How to find it. List your active roles against your active employees. Look for roles assigned to nobody, roles assigned to one person who inherited them from someone else, and any role with a name like "AP Clerk - Copy." Each one is a question you'd rather answer now than under audit conditions.
Then take your three most sensitive permissions, something like posting journal entries, approving vendor bills, and changing bank details, and list every role that can do each. If any name appears on more than one of those lists, you've found something worth fixing this quarter rather than next — the kind of issue a focused NetSuite health check for expensive problems is designed to catch before an auditor does.
5. Workarounds that became the process
What it is. A spreadsheet somebody built because a report wasn't right. A manual export that bridges two systems. A month-end step that exists because a script broke once and nobody fixed the script.
Why you don't see it. It stopped looking like a workaround the moment it started working. Now it's just how the team does that task, it's in the close checklist, and the new hire learned it as a procedure rather than as a patch. Nobody flags it, because from the inside it isn't a problem. It's the job.
The cost is hours, every month, forever, and those hours never touch the NetSuite invoice at all. They show up somewhere else instead: a close that takes nine days, a finance team that can't take leave in the first week of the month, an analyst spending a third of her time on assembly rather than analysis — all problems that respond well to NetSuite optimization strategies that cut month-end close time.
Manual workarounds are the standard symptom of automation that was never finished. Incomplete automation pushes people back into offline spreadsheets and manual data entry, and manual data entry is where errors and financial misstatements get introduced. Disconnected purchasing and payments modules produce the same effect on the other side of the ledger, where vendor payments drift out of step with what the system thinks it owes. That's especially true in billing and revenue, where the right NetSuite setup for software and technology companies removes a lot of the workaround work entirely.
There's a quieter cost underneath that one. Every manual bridge is a place where a number can be wrong and nobody will catch it. When the CFO says they don’t fully trust the dashboard, this is usually why. The data isn't wrong on purpose. It's wrong because it passed through four hands and a spreadsheet on the way there, or because nobody has run a serious NetSuite performance and reliability audit since go-live.
Basic support, premium support, and what each service tier actually buys
Most of the five above trace back to the same decision, usually made quickly during procurement: which NetSuite support options you signed up for and whether anybody has revisited that choice since.
Oracle's own support runs in tiers. Basic Support is included and reactive by design: you raise a case, it gets worked, response times reflect severity. NetSuite Premium Support buys faster response times and a more direct route to a human. Above that, Gold and Platinum are aimed at more demanding environments: Gold for companies with complex operations and multiple subsidiaries and Platinum for mission-critical operations where maximum uptime is the point. Advanced Customer Support, ACS, sits alongside these as a paid engagement with named resources.
The important thing to notice is that every support tier is built around restoring service. None of them are designed to notice that eleven seats are dormant, a module was never configured, your role structure has drifted, or the close still runs through a spreadsheet. Those aren't incidents, so reactive support won't catch them unless someone flags an issue.
That's why the support decision goes beyond how fast someone answers. The tier you pay for determines what gets watched, not just how quickly someone responds.
The failure mode runs in both directions. Under-buying means system health goes unmonitored until something breaks, and poorly optimized environments end up leaning on expensive emergency consultants, which is the costliest way to buy expertise. Over-buying means paying enterprise-tier rates on an instance that could be well-run at a fraction of the cost. Both are versions of the same mistake: matching the support contract to the size of the company rather than to the complexity of the NetSuite environment.
A useful test: ask who currently owns the question "is this instance still configured for how we operate today?" If the answer is a name, you're probably covered. If the answer is a tier, you're not.
Managed services, strategic support, and what proactive actually means
Managed services describe a different arrangement, not a higher tier of the same one. Where basic support is organized around tickets, managed services are organized around an environment, with the provider responsible for its ongoing condition rather than for its worst moments.
In practice that means someone whose remit includes the unglamorous review work: license utilization against headcount, enabled features against the subscription, role structure against the org chart, script and workflow errors against the log, and performance against how it behaved last quarter. Poorly managed environments tend to get slow at peak times and nobody escalates it because slowness on the last day of the month feels normal. That's the sort of drift a managed arrangement is supposed to catch, and it's precisely what a reactive contract cannot.
Three structures are common in the NetSuite ecosystem, and they suit different business needs:
- Hourly or block-hours support. Cheapest per hour, reactive by nature, and the model most prone to the expiring-hours problem in section three. Sensible for stable environments with a capable in-house NetSuite admin.
- Retainer-based support. A fixed monthly commitment with a defined scope. Better continuity, and the provider learns your instance, but the scope usually still centers on requests you raise.
- Managed support from a NetSuite implementation partner or solution provider partner. A team rather than an individual, with proactive review and continuous improvement built into the engagement. More expensive monthly, and the only model where finding waste is somebody's actual job.
What separates a good NetSuite partner from a competent one is whether the relationship includes strategic guidance at all, whether anyone is thinking about where your business operations are heading and what the system needs to do next, rather than only what it failed to do last week. Strategic support of that kind is what keeps an instance matched to a business as it changes. Growing companies change fastest and get the least of it, because the same growth that creates the drift also eats the time that would be spent noticing it.
Businesses that never get expert help simply don't use most of what they're paying for, which is its own quiet loss: a full-featured platform run as a general ledger.
The cost of NetSuite before support enters the picture
It helps to see where support sits in the total cost, because the support line is rarely the biggest number and is almost always the one that determines whether the others were worth spending.
NetSuite pricing is typically structured as an annual license with three components: the base edition, the user licenses, and any additional NetSuite modules. The edition tracks company size and complexity, which is why growing companies with multiple entities end up paying materially more than a single-entity business with the same headcount.
On top of that sits implementation. Figures commonly cited for a first year land between roughly $25,000 and $300,000 all in. The key factors are the ones you'd expect: user count, which modules, how much data migration, how much custom development, and overall implementation complexity.
Two things follow from those numbers. First, the implementation budget dwarfs the support budget, and support is what protects it. Spending six figures implementing NetSuite and then buying the cheapest possible ongoing support is a strange allocation of resources, and an extremely common one. Effective support is what maintains system stability after go-live; without it the configuration you paid for degrades while the license keeps renewing.
Second, the cost of NetSuite is fixed by contract. The value is not, and the gap between the two is almost entirely a support and configuration question.
The invoice was never built to tell you
Read those five back and the common thread is straightforward. None of them show up as a line item. Some don't show up as a cost at all until an auditor asks a question or a close runs three days long, which is why building a habit of a structured NetSuite health check with an outside team matters more than it looks on paper.
Your renewal invoice reports what you're subscribed to. It doesn't report what you're using, what expired, what was never switched on, or what your team is doing manually to work around the parts that don't fit. It reads clean every year because reading clean is all it was designed to do.
That's worth saying plainly, because the usual reaction to a list like this is to assume somebody dropped the ball. Nobody did. Each of these is a sensible local decision, made by somebody with better things to do that week, and the cost only becomes visible when you add twelve months of sensible local decisions together and look at the total.
So the check has to come from somewhere else. Some of it you can do yourself with the searches above, and an afternoon spent on them is an afternoon well spent.
The rest needs somebody who's seen enough NetSuite environments to know where these things settle, and who has no stake in the answer being reassuring — the kind of choice that sits at the center of any serious NetSuite partners vs. independent consultants decision framework.
Talk To A NetSuite Support Expert At Stockton10
The harder question is what somebody who looks at NetSuite environments full time would find in yours. There are more free NetSuite tools and checklists if you'd rather keep going on your own first.
- Free NODA Questionnaire: 60 seconds to quantify your optimization debt and put a number on what the invoice doesn't show.
- Live Audit: see on-screen exactly where dormant licenses, unconfigured modules, broken workflows, and orphaned roles are slowing your business operations down.
- 20 hours with a senior consultant on your real account, looking for exactly this. No rotating juniors. No ramp-up period. No explaining your history twice. You get what we find in writing whether you carry on with us or not.
Book a call with Stockton10 to get a tailored NetSuite support plan that complements your existing Oracle support and stops the cycle of post-go-live firefighting.
