Scaling Support Through Growth
Tollgate Foods doubled in eighteen months and its help desk did not. The desk had been one person with a spreadsheet when the company had sixty staff. It was still one person with a spreadsheet, plus a second person hired in a panic, when the company had a hundred and forty. By then the company also had a second warehouse, a night shift and a finance system that nobody had trained anyone on. Every month something that had worked at sixty stopped working. Every month the desk learned, from the breakage, what it should have added the month before. Growth does not break a help desk all at once. It breaks it one threshold at a time, in a predictable order, which is the only good news.
This series is about the order. It covers what changes between fifty and five hundred employees, as a line with the thresholds marked and what breaks before each. It covers when to add heads, by reading capacity honestly rather than by a ratio someone read somewhere. It covers when to add tools, and when the spreadsheet is still enough. Then comes when to add process, and how much. That is always less than the framework says and more than the desk has. The series covers the second site and the remote half, where the one queue must stay one queue. And it covers planning a year ahead from HR's growth forecast, so the next threshold is met before it is hit. The company will grow whether the desk plans or not. Planning is cheaper.
Articles in This Series
- What Changes Between Fifty and Five Hundred Employees
The thresholds (the solo admin, the second person, the first process, the first tool, the first manager, the second site), what breaks before each, and the growth stage card. - When to Add Heads: Reading Capacity Honestly
The capacity arithmetic, the signals (backlog age, after-hours activity, leave untaken), the technician-to-staff question answered only as fictional worked examples in ranges, and the capacity check. - When to Add Tools, and When the Spreadsheet Is Still Enough
The spreadsheet that was enough, the point at which a ticket system is needed, and the migration. Covers remote tools, the tool that will not fix a process, and the tool trigger list. - When to Add Process, and How Much of It Your Desk Needs
The process that arrives too late and the one too early, lightweight first, intake then prioritisation then service levels then change, and the process ladder by stage. - The Second Site and the Remote Half: Still One Desk
Coverage across sites, spares in two places, remote-first design, the local champion idea, the catalogue per site, the queue that stays one queue, and the multi-site plan. - Planning a Year Ahead: The Support Capacity Plan
The hiring plan from HR's growth forecast, the onboarding volume it implies, the budget conversation in hours, the quarterly review, and the annual capacity plan.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.