From shared inbox and spreadsheets to your first ITSM tool: a 90-day plan for 50 to 300 person firms
Short answer
If IT requests arrive in a shared mailbox, chat messages and corridor conversations, and assets live in a spreadsheet, a first service desk tool will pay for itself mostly in visibility: you will finally know what is open, what is late and where time goes. For a 50 to 300 person company with 1 to 6 people doing IT work, keep the first tool simple. Freshservice is our default for a dedicated internal IT team: official pricing on Nov 7, 2026 was Starter $19 / £15, Growth $49 / £40 and Pro $99 / £79 per agent per month billed annually, and Growth is the tier most small IT teams need because it adds the service catalogue, asset management, approvals, business hours and employee onboarding. Jira Service Management is the better pick if your company already runs on Jira, and its Free plan covers up to 3 agents. Frappe Helpdesk is a free, open-source option for teams on ERPNext or with technical capacity. Scope the first 90 days tightly: email intake, a portal, 6 to 10 request types, one SLA, a starter knowledge base and an asset import. Leave change management, CMDB and integrations for phase two.
Contents
- Who this guide is for
- Signs you have outgrown the shared inbox
- Choosing the first tool
- Prices in USD and GBP (checked Nov 7, 2026)
- Setup scope: what is in and out of the first 90 days
- The 90-day plan, week by week
- Roles, rhythm and the five numbers to watch
- Adoption: getting people to stop emailing you directly
- Common pitfalls
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for the person who does IT at a company of roughly 50 to 300 employees: an IT manager, an operations lead who inherited IT, or a small IT team of 1 to 6 people. Requests arrive by email to a shared mailbox like it@ or help@, in Slack or Teams messages, and in person. Laptops, licences and SaaS admin accounts are tracked in a spreadsheet, if at all.
It covers three things: how to tell it is time to move, which first tool to choose, and a realistic 90-day plan to get live. Prices come only from official vendor pages, checked on Nov 7, 2026: the Freshservice pricing page (Freshworks publishes USD and GBP), the Atlassian Service Collection / Jira Service Management pricing page (USD only, so GBP is an indicative conversion) and the Frappe Helpdesk pricing page (USD only). Agent counts, timelines and opinions are ours from setting up first service desks, and are labelled as such.
Signs you have outgrown the shared inbox
| Signal | What it costs you |
|---|---|
| Two people answer the same email, or nobody does | Duplicate work and dropped requests; users chase in chat instead |
| You cannot say how many requests came in last month | No case for headcount, no view of recurring problems |
| New starters wait for laptops or accounts | First-day experience suffers; managers escalate to leadership |
| Leavers keep access because nobody had a checklist | Security and audit exposure |
| The asset spreadsheet disagrees with reality | Lost devices, over-bought licences, failed audits |
| Customer security questionnaires ask about incident and change processes | Sales cycles slow down because you have no evidence |
Two or more of these usually means it is time. A first ITSM tool will not fix process by itself, but it makes the work visible, which is the precondition for fixing anything.
Choosing the first tool
For a first tool at this size, we shortlist three options and rarely look further:
| Freshservice | Jira Service Management | Frappe Helpdesk | |
|---|---|---|---|
| Best fit | Dedicated internal IT team that wants ITSM features ready-made | Companies already using Jira for engineering or projects | Teams on ERPNext or with in-house technical capacity; tight budgets |
| Pricing model | Per agent; Starter, Growth, Pro, Enterprise | Per agent, progressive; Free for up to 3 agents | No per-agent fee; hosting on Frappe Cloud or self-host |
| Free option | No free plan; 14-day free trial | Free plan, up to 3 agents | Self-host free; 14-day Frappe Cloud trial |
| Requesters (employees) | Not charged as agents | Free and unlimited | Unlimited |
| Asset management | Growth includes asset management with 100 managed assets; Asset Units packs of 500 | Assets on Standard and above (5,000 free objects on Standard) | Basic; build or integrate |
| Teams and Slack | ServiceBot on Microsoft Teams and Slack from Starter | Requests via Microsoft Teams and Slack listed from Free | Not a headline feature |
| Admin effort | Low | Low to medium; easier if you know Jira | Medium; framework knowledge helps |
Feature placement is from each vendor's pricing page, checked Nov 7, 2026. Zendesk and similar customer-support tools can work for IT at this size too; our Zendesk vs Freshservice for internal IT guide explains where that works and where it does not.
Why not ServiceNow as a first tool?
ServiceNow is quote-only and built for large, multi-department platforms with dedicated administrators. For a first service desk at 50 to 300 people, the implementation and administration effort is almost never justified in our experience. Revisit it if you grow past a thousand people or join a group that standardises on it.
Prices in USD and GBP (checked Nov 7, 2026)
| Plan | USD | GBP | Billing and status |
|---|---|---|---|
| Freshservice Starter | $19 annual / $29 monthly | £15 annual / £25 monthly | Per agent per month; official USD and GBP prices |
| Freshservice Growth | $49 annual / $59 monthly | £40 annual / £45 monthly | Official |
| Freshservice Pro | $99 annual / $119 monthly | £79 annual / £95 monthly | Official |
| Freshservice Enterprise | Contact sales | Contact sales | Quote |
| JSM Free | $0, up to 3 agents | £0 | Official |
| JSM Standard | $21.50 per agent/month at the calculator's default 75 agents (monthly billing) | ≈ £15.95 (indicative) | Progressive pricing: small teams pay a different per-agent rate; use the calculator |
| Frappe Helpdesk on Frappe Cloud | Sites from $5/month; servers from $20/month | ≈ £3.71 / ≈ £14.84 (indicative) | Hosting, not per agent |
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3476 per £1 for 5 Nov 2026, the latest published when we checked on Nov 7, 2026. They are not official UK prices; the vendor does not publish a GBP list price, and your invoice currency, rate and VAT treatment may differ. Prices exclude VAT and other taxes. Freshservice day passes for occasional agents start from $3 per the pricing page FAQ, and new accounts get 3 free day passes.
What that means for a small IT team
| Scenario (list prices, annual billing) | USD per year | GBP per year |
|---|---|---|
| 3 agents on Freshservice Starter | $684 | £540 |
| 3 agents on Freshservice Growth | $1,764 | £1,440 |
| 5 agents on Freshservice Growth | $2,940 | £2,400 |
| 5 agents on Freshservice Pro | $5,940 | £4,740 |
| Up to 3 agents on JSM Free | $0 | £0 |
| Frappe Cloud site, any number of agents | $60 hosting | ≈ £44.52 hosting (indicative) |
We do not show a JSM Standard figure for 4 to 6 agents because the 75-agent calculator price above does not apply at that size; check Atlassian's calculator. Remember the tool is the smaller cost: the bigger one is the time to set it up well, which is what the plan below is for. For a fuller cost model see our Freshservice vs JSM vs ServiceNow pricing guide.
Setup scope: what is in and out of the first 90 days
| In scope for go-live | Deliberately later (phase two) |
|---|---|
| Email intake from your existing it@ or help@ address, with forwarding and correct reply-from | Change management and CAB |
| Self-service portal with 6 to 10 request types | Full CMDB and service mapping |
| Categories (keep to one or two levels) | Problem management as a formal process |
| One SLA policy with business hours and two or three priorities | Multiple SLAs by department |
| Teams or Slack intake if your staff live there | Integrations with HR, identity and monitoring tools |
| Starter knowledge base: the 15 to 20 answers you give most | AI agents and chatbots beyond the basics |
| Asset import from the spreadsheet: laptops, phones, key SaaS licences, owners | Software licence optimisation |
| Joiner and leaver checklists as request types or onboarding workflows | Automated provisioning |
| Basic reports: volume, open backlog, SLA breaches, top categories | Executive dashboards |
This scope is our standard for first service desks at this size. It is small on purpose: in our experience teams that try to launch with change, problem, CMDB and integrations at once often stall before go-live, while a simple launch gets adopted and improved.
The 90-day plan, week by week
Days 1 to 15: decide and prepare
Agree goals with leadership in one page: what "better" means (for example, every request tracked, joiners ready on day one, a monthly report). Pull three months of shared-inbox email and tag a sample of 200 to find your real categories. Shortlist tools, run trials with real requests, and choose. Clean the asset spreadsheet: one row per device, with owner, model, serial and purchase date.
Days 16 to 45: configure
Set up the account, agents, groups and business hours. Build 6 to 10 request types from your email sample (for example: laptop issue, access request, new starter, leaver, software request, password and MFA, printer and peripherals, other). Create categories and one SLA policy. Connect email intake and test threading. Write the first 15 to 20 knowledge articles. Import assets and link them to users. Build joiner and leaver checklists. Configure the Teams or Slack bot if relevant.
Days 46 to 60: pilot
Run a pilot with one or two departments, ideally including a demanding one. Agents work every request in the tool, even those that arrive by chat. Fix request types and forms based on what people actually submit. Check SLA timers and notifications. Tune email templates so replies read like a person wrote them.
Days 61 to 75: launch
Announce to the whole company with a short message: where to go, what to expect, what changes. Switch the shared mailbox to forward into the tool. Keep a polite auto-reply on direct emails to IT staff pointing to the portal. Agents log chat and corridor requests themselves for the first weeks so the data is complete.
Days 76 to 90: stabilise and report
Review the first month of data: volume by category, backlog, SLA performance, top knowledge gaps. Write five more articles for the most common requests. Present a one-page report to leadership and agree the phase-two list: change management, integrations, more SLAs or asset discovery.
Roles, rhythm and the five numbers to watch
A small IT team does not need ITIL job titles, but it does need clear ownership. The minimum we set up at go-live:
| Role | Who it usually is at this size | What they own |
|---|---|---|
| Service desk owner | IT manager or the most senior IT person | Tool configuration, request types, SLA policy, monthly report |
| Queue lead (rotating) | Each agent in turn, weekly | Triage of new requests, chasing breaches, assigning work fairly |
| Knowledge owner | One named agent | New and stale articles, monthly review of the top ten |
| Asset owner | Often the same person as the service desk owner | Asset records accurate through joiner, leaver and repair requests |
| Executive sponsor | COO, CFO or CTO | Backing the "use the portal" message and the phase-two budget |
Then a light rhythm: a 15-minute daily queue check, a weekly review of anything older than a week, and a monthly report to the sponsor. That is enough governance for a 50 to 300 person company.
Five numbers to track from day one
- Requests per month by category, to find what to automate or document next.
- Median first response time, the number users feel most.
- SLA breaches, by priority, to see whether targets are realistic.
- Backlog older than seven days, the early warning that the team is overloaded.
- Joiners ready on day one (yes or no per starter), which leadership cares about more than any ticket metric.
All three tools in this guide report on volume, backlog and SLA performance out of the box at the tiers we recommend; the joiner metric is easiest as a simple field on the new-starter request.
Adoption: getting people to stop emailing you directly
The tool is the easy part. Habits are hard. What works in our experience:
- Keep the email address. Forward the existing it@ address into the tool so nobody has to learn a new one.
- Make the portal short. Six to ten tiles, plain names, no IT jargon. "My laptop is broken" beats "Hardware incident".
- Reply from the tool, always, even to chat requests. People learn that the ticket is where answers come from.
- Show the benefit. A monthly note that says "we resolved 340 requests, median first response 45 minutes" builds trust quickly. Use your own real numbers.
- Have leadership use it. When the CEO raises a request through the portal, everybody notices.
Common pitfalls
Too many categories
Teams copy a 40-category list from a template and then nobody picks the right one. Start with fewer than ten, look at real data after a month and adjust.
No owner for the knowledge base
Articles go stale within months without an owner. Give one person the job and review the top ten articles every month.
Buying the top tier "to be safe"
Most first service desks at this size need Freshservice Growth or JSM Standard, not Pro or Premium. Upgrade when you have a process that needs the feature, for example formal change management.
Skipping the asset clean-up
Importing a messy spreadsheet just moves the mess. Spend the time to clean it once, then keep it current through joiner and leaver requests.
Best for, and wrong choice when
Freshservice: best for
A dedicated internal IT team that wants ITSM features ready-made, with Growth as the realistic starting tier.
Freshservice: wrong choice when
Your company already runs everything in Jira, or your budget is effectively zero and you have technical capacity for an open-source tool.
Jira Service Management: best for
Companies whose engineering or project teams already use Jira, and very small IT teams that fit in the 3-agent Free plan.
Jira Service Management: wrong choice when
Nobody on the team knows Jira and you want the simplest possible IT-focused admin experience.
Frappe Helpdesk: best for
ERPNext users and teams with in-house technical skills who want no per-agent fee.
Frappe Helpdesk: wrong choice when
You need ready-made ITSM features such as asset management, service catalogue and change management without building them.
Still deciding whether to run the desk yourself at all? Our in-house vs outsourced service desk cost guide gives a framework for 50 to 500 users.
Frequently asked questions
When should a company move IT support from email to a service desk?
When requests get lost or duplicated, you cannot report on volume, new starters wait for equipment, or customer audits ask about incident and change processes. For most companies this happens somewhere between 50 and 150 employees.
What is the best first ITSM tool for a 50 to 300 person company?
For a dedicated internal IT team we usually recommend Freshservice Growth. If the company already runs on Jira, Jira Service Management is a strong alternative with a free plan for up to 3 agents. Frappe Helpdesk is a free open-source option for teams with technical capacity.
How much does Freshservice cost in USD and GBP?
On Nov 7, 2026 the Freshservice pricing page listed Starter at $19 / £15, Growth at $49 / £40 and Pro at $99 / £79 per agent per month billed annually, or $29 / £25, $59 / £45 and $119 / £95 billed monthly. Enterprise is contact-sales. Taxes are extra.
Is Jira Service Management free for small IT teams?
Yes, for up to 3 agents. Atlassian's Free plan includes 3 agents, 2 GB storage and Community support. Paid plans use progressive per-agent pricing; Standard showed $21.50 per agent per month at 75 agents on Nov 7, 2026 (about £15.95 as an indicative conversion; Atlassian publishes USD only).
How long does it take to set up a first service desk?
Our standard plan is 90 days from decision to stable operation: about two weeks to decide and prepare, a month to configure, two weeks of pilot, two weeks to launch and two weeks to stabilise and report. A very small team can go faster with a tighter scope.
Should we set up change management in the first 90 days?
Usually not. Launch with intake, request types, one SLA, a knowledge base and assets. Add change management when you have a real need, for example customer audits or frequent production changes.
Do employees need licences to raise tickets?
Not on the tools in this guide. Freshservice and Jira Service Management charge for agents, not for employees raising requests, and Frappe Helpdesk has no per-user fee.