Use cases · 20–300 staff
20–300 staffProfessional services & SMB
You do not have an IT department. You have a capable person who is also doing their own job.
How IT usually works in this setting
In a firm of 20 to 300 people, IT is usually someone's second or third responsibility. Requests arrive by email, in the kitchen and by phone, and nothing is written down until something goes wrong.
What it costs you today
- The same question is answered for the fifth time because nothing is written down.
- New starters wait days for access while someone finds time to set them up.
- Nobody knows how many laptops, licences or subscriptions the firm is paying for.
- When the person who does IT is away, the work simply waits.
What the desk does about it
- One queue, every channel — Email, a short form, or a message to the assistant — it all lands in one place with a status, an owner and a due time.
- Answers before a ticket is needed — The assistant answers the repeat questions from your own knowledge base, so the password resets stop consuming the day.
- A joiner and leaver process that runs — New starter and departing staff follow a checklist: access granted and revoked, assets allocated and returned, licences released.
- A register you can actually trust — Every device, licence and subscription in one place, with who has it and when it expires.
“Nobody knows when Sam started”
New starters to be productive on day one, without panic.
What we show you, in order
An office manager at a 60-person professional firm
- Build one onboarding request that fans out into the tasks: accounts, device, software, building access, introduction.
- Attach the standard knowledge articles so each task is done the same way every time.
- Track the licence freed when a laptop is returned, and reallocate it.
- Send the new starter a portal link on their first morning.
- Watch the checklist close itself.
Why it lands
Day one starts on time, and the office manager gets their afternoon back.
What we can stand behind
- Unlimited end users and no per-ticket charges, so asking for help is never a cost decision.
- The desk works without a technician on staff — we can run it for you.
- Priced per organisation by seat, site and service level, quoted in writing before you commit.
- No lock-in contract, and your data exports in full whenever you want it.
What we would need from you
- A list of who does what when something breaks today.
- Your software subscriptions and how many seats each one has.
- The joiner/leaver steps as you do them now.
- Thirty minutes with the person who currently holds the queue.
What every one of these has in common.
The configuration changes by sector. The platform underneath it does not: one record per request, service levels per team, and tenancy enforced on the server.
One request, everything attached to it
The same data model behind all eight situations — which is why a sector change is a configuration change rather than a new product.