One working system
The routine of IT, with the decisions left to people.
We have no IT person, so accounts and laptops fall to the office manager.
IT operations desk
A starter, leaver or access request is checked against the company's written policy and carried out step by step on a sample directory, risky access waits for the person the policy names, and a morning check lists what needs fixing.
What it does
What waits, what is answered, what is checked, in four steps.
Finance access waits for the person the policy names
A new starter asked for the finance system. The desk opened everything else and left that one step waiting, because the written policy says the finance director decides.
Staff questions get the runbook, word for word
A question about a paper jam is answered with the runbook entry, quoted exactly. A question about changing a supplier's bank details is not answered at all; it is handed to a person.
Each morning the weak points are listed
Backups that did not run, licences about to renew and laptops behind on updates appear on one screen, each with the fix beside it.
The owner gets one page a week
The page names who started, who left, what is waiting on whom, and what is overdue. It is written for the managing partner, in plain words.
Ownership
You own it. All of it.
The policy the desk follows is your policy, written in sentences a manager can read and change. The log of every account opened and closed is yours as well, which is the record an auditor or an insurer asks for.
Hire or own
What the hire costs, and what this costs
If the role in your post is mostly keeping accounts, devices and renewals in order, that routine can be built once at a fixed fee. The person you then hire, or the outside provider you already use, is left with strategy, vendors and security.
What this role is paid, and what that comes to with benefits, is on the IT manager salary page.
When the hire is the right call
Hire the IT manager when you have a team to lead, a budget to defend, or systems that the business cannot be without for an afternoon. Leadership, vendor negotiation and security judgment are a person's work.
Read this first
What you are looking at, said plainly
Demonstration system, sample data
The architecture studio, its staff and its laptops are invented, and the directory is a sample one inside the demonstration. No real account is opened or closed, a backup run again returns the outcome written in the sample data, and questions are matched to the runbook by shared words, with no language model.
What it costs
Three public prices. Nothing per user.
Jim Glaser Law takes reference calls.Ask in your note and we set it up.
One step
Send me a version customized for my company
Questions buyers ask
Before you ask for your version
Does this do an IT manager's job?
It does a core part: the routine requests, the morning check and the weekly report. Setting direction, managing people and suppliers, and owning security are not in it.
What does it hold back for a person?
Access to finance systems, admin rights and any licence that would have to be bought wait for the person the policy names. Physical tasks, such as a door fob, are created as tasks for a person and never marked done by the desk.
How does it answer staff questions?
From the company's own runbook, quoted word for word. Questions that touch money, security or someone else's access are handed to a person even when an entry matches.
We use an outside IT provider. Is this still relevant?
It can sit beside one. The desk handles the routine and the record, and your provider handles what needs an engineer.
What would be customized for us?
Your roles, your standard accounts and your policy lines, on an invented staff list. We need no access to your directory to build it.