I'm not even sure exactly what I'm asking here, bu...
# general
v
I'm not even sure exactly what I'm asking here, but does anyone have any insight or personal anecdotes on what the ratio of netsuite/it workers they have based on the number of employees or general size of the company? We have 1 full time admin and 1 part time admin who are responsible for all the customizations/reporting/maintenance/etc for a company of around 250~ employees with 5+ different sales channels. Starting to feel a bit of the pain of being spread too thin, but I don't know if we're just doing it wrong or are generally inefficient as admins.
j
How many admins you need is highly situational, affected by: • Number of users (you mentioned 250 employees, but are all those NetSuite users?) • What things your company is doing, i.e. what modules your company is using, integrations you have to deal with, other software you have to manage, etc., etc. • What the expectations/purview of the admins are (This is pretty huge, TBH. Sometimes you're basically running parts of the company, even when you're just supposed to be keeping the systems running.) • The competency/tech fluency of the end users and especially any accounting staff • Level of autonomy to actually make changes (e.g. highly restrictive SOX controls, technical debt, brittle systems integrations) • I'm sure a whole bunch of things I'm not thinking of here. So all that to say that at a very high level 1.5 admins for 250 employees sounds pretty reasonable and probably even a bit light if all those are NetSuite users, but really I have no idea, because there's so many details that are relevant. And of course, budget is always the ultimate decider; it doesn't matter how many people you actually need if you can't get someone to fork over the money for a position. Personally, I've found that I rarely need more than 3 highly competent folks total (read on the expensive end) to manage a finance stack regardless of company size. If I find myself needing a bigger team than that, I typically find it more fruitful to find ways to trim the scope of responsibilities because that usually means we're actively involved in performing business activities rather than supporting the end users to do so more effectively (which is where we we're providing the most leverage/value). Not much of a definitive answer, but hope that helps a little bit.
👍 1
v
Thanks for the detailed reply, it gave me a lot to think about. I assumed every business would be too unique to give a one size fits all answer here. We have over 250 employees, but 250 is a fair estimate of how many are actively using netsuite daily. You make a good point with the budget being the ultimate decider. I was mostly looking for a sanity/reality check to see if anything I said immediately set off alarm bells for anyone else. I'll think more about what you said since I think it is fair to say that technical debt and the amount of systems we have to interact with is probably our biggest bottleneck atm.
j
Yeah, I think the best way to get budget is to say: either you need start handling X under another team or we need Y resources to handle X. That usually results in them giving X to another team, then that team totally blowing it up and making it worse, then them coming crawling back offering you the Y resources. Of course now you have a bigger mess on your hands than originally anticipated, but that's just sorta the way the cookie crumbles and why you ask for about 20% more for Y than you really need 😉
r
what modules your company is using, integrations you have to deal with
To add onto Jimbo's point, this is the big one. If you're using just a few modules and they're simple ones without much customization or scripting needed, 1.5 Admins is probably more than enough. If you're running ARM, taxes, Fixed Assets and half your system is heavily scripted, then that might be a little light.
e
2 admins at the bare minimum to allow for coverage when either one goes on PTO or calls in sick.