The short answer
Most companies running NetSuite with 20 to 150 users need between 10 and 40 hours of administration a month. The spread inside that range is wide, and it is not driven by headcount alone.
A 40-user company with heavy customization and an active integration estate can generate more work than a 120-user company running close to standard functionality. Sizing by user count alone is the most common way to get this wrong.
The four things that actually drive the number
User count matters, but only as one input. These four together predict the workload far better than any of them alone.
- Users: more people means more access changes, more requests, and more training questions.
- Transaction volume: high volume surfaces performance problems and reconciliation work that low volume never triggers.
- Customization depth: every script, workflow, and custom record is something that must be tested twice a year and maintained in between.
- Rate of change: a business reorganizing, adding subsidiaries, or changing process generates far more configuration work than a stable one.
A rough sizing guide
Treat this as a starting hypothesis to test against your own measurements, not as a quote.
Around 10 hours a month covers a stable account that mostly needs an owner: access management, saved searches and dashboards kept accurate, close support, and release testing twice a year. It does not cover building much that is new.
Around 20 hours a month suits an account that is still moving — workflows and custom fields being built as processes change, reporting developed as finance asks for it, and integrations monitored rather than just repaired after they fail.
Around 40 hours a month fits companies where NetSuite runs the business: development capacity every month, integration work, and a tight response commitment because a system outage stops the operation.
How to measure your real number
Run a one-month log. It is tedious and it is the only method that produces a defensible figure.
Capture every NetSuite request that reaches anyone in the business — including the ones people currently solve by asking a colleague or working around the system in a spreadsheet. Those hidden requests are usually where the surprise is.
- Log the request, who handled it, and roughly how long it took.
- Include the close: hours spent on period-end support count.
- Include time lost to workarounds, not just time spent inside NetSuite.
- Separate one-off project work so it does not inflate your recurring baseline.
Why over-buying is as bad as under-buying
Buying more hours than you need does not produce a better-run account; it produces unused hours and a monthly invoice that becomes hard to justify at the next budget review. Retainer hours that expire at month end make that waste visible rather than banking it into a balance nobody can plan around.
Under-buying is the more common failure and it is quieter. The recurring work — release testing, integration monitoring, the quarterly permission review — is what gets dropped first when the hours run short, because none of it has anyone chasing it. The right size is the one that covers the recurring work with a little room, and treats genuine projects as separate scoped pieces.
Shahin Zakizadeh
Founder & Principal NetSuite Consultant at SZnetsuite — SuiteScript development, automation, integrations, and billing for growing NetSuite teams.
About the practiceRelated services
Keep reading
NetSuite vs. QuickBooks: How to Know When It's Time to Upgrade
The signs that a growing company has outgrown QuickBooks, and what actually changes when you move to NetSuite.
Read articlePlanningWhat a NetSuite Administrator Costs in 2026: Salary, Contractor, or Retainer
Published salary data, contractor rates, and managed-service retainers compared — with the hours threshold where each option stops making sense.
Read article