Take back the hours your techs spend on things that aren’t the fix. At most MSPs, 30 to 70% of a tech’s day is repetitive work and switching between about eight systems: reading the ticket, finding the device, finding the docs, doing the same request again, then writing the note and the time entry from memory. Put the context for every ticket on one screen, run repeat requests as workflows, triage and route tickets on arrival, and write notes and time as the work happens. That returns 10 to 15 hours per tech per week, 30 to 40% more capacity, worth $6,000 to $8,000 or more of billing capacity per tech per month. For a 10-tech shop, that is the capacity of three more techs.
Why is hiring the default, and why is it expensive?
About 65 cents of every MSP revenue dollar is the cost of delivering the service, and most of that is tech labor. When the ticket count goes up, the usual answer is another tech. A good tech takes months to find and months more to learn your clients, and the new hire adds cost before adding capacity. Growth ends up capped by hiring.
When we were buying MSPs, the thing that separated a great one from an average one was rarely the stack. It was how many endpoints each tech could look after well. Capacity per tech is what an MSP’s margin is made of.
Where do the hours actually go?
A typical tech solves 5 to 8 tickets a day. For each one, the time splits roughly like this:
- Finding context. Opening the PSA, the RMM, the documentation, Microsoft 365 and past tickets to work out who this is and what is wrong.
- Repeat work. Password resets, MFA, new hires, leavers, mailbox access and license changes, done by hand with the same clicks every time.
- Waiting on the wrong owner. Tickets that sit in a queue, or bounce between techs, before the right person picks them up.
- Admin after the fix. Writing the note, the reply and the time entry, often at the end of the day, when billable minutes get rounded down or forgotten.
Only the fix itself is work the client pays for. The rest is where the capacity is.
Five ways to take the hours back
- One screen per ticket. Bring the ticket, the user’s history, the device, the client’s docs and the Microsoft 365 actions together, so a tech stops hunting across tabs. This is the largest single saving.
- Workflows for repeat requests. Turn your top ten requests into workflows a tech runs from the ticket. New-employee setup goes from about 25 minutes to about 90 seconds. In Toolqit, building one is magic made by your voice: describe the job and Toolqit Build lays out the steps.
- Triage and routing on arrival. Give every new ticket a clear title, a summary and the right owner from your own assignment history, with your routing rules first.
- Notes and time as you go. Write the internal note, the client reply and the time entry while the work happens, and push them to the PSA. Billable minutes stop slipping.
- Fewer tools. Each tool you retire is one less login, one less screen and one less place for context to hide.
How do I measure it?
Before you change anything, write down four numbers for the last 90 days:
| Measure | Where to find it |
|---|---|
| Tickets per tech per day | PSA ticket reports |
| Median time to resolve, by ticket type | PSA ticket reports |
| Billable hours logged per tech per week | PSA time entries |
| Endpoints per tech | RMM device count divided by techs |
Check them again after 30 and 90 days. If the tickets per tech and billable hours go up while the headcount stays flat, the capacity is real.
What is it worth?
Take a tech who gets 12 hours back a week. That is about 52 hours a month. At an effective rate of $125 to $150 an hour, it is $6,500 to $7,800 of billing capacity per tech per month. Across a 10-tech team, it is the same as adding three techs, without the recruiting, the ramp-up or the payroll.
Where does Toolqit fit?
Toolqit is the place where your techs can do all their work. It sits on top of your PSA, RMM and Microsoft 365 and puts every ticket’s context on one screen. Ask Toolqit answers inside any ticket and then does the work once a tech approves it, Suggested Workflows turn your repeat tickets into one-click runs, Toolqit Routing assigns new tickets from your own history, and notes and time entries are written as the work happens and synced to the PSA. The Performance board in Team Performance shows the work each tech is getting through.
FAQ
How many hours can an MSP tech realistically get back?
Techs on Toolqit typically get 10 to 15 hours back per week. It depends on how much of the day is repeat work and tool switching today.
Does more capacity mean fewer techs?
It doesn’t have to. Most MSPs use the hours to take on more clients and endpoints with the same team, or to move techs onto projects and higher-value work.
What should I automate first?
Start with the requests every client sends: new hires, leavers, password and MFA resets, and mailbox access. They are frequent, predictable and easy to measure.
Do I need to replace my PSA to get these hours?
No. Toolqit syncs two ways with ConnectWise PSA, HaloPSA, Autotask and SyncroMSP. The PSA stays the system of record and techs work in Toolqit.
How fast will I see the change?
Onboarding takes 30 to 45 minutes. Techs can work tickets in Toolqit the same day, and the hours show up in your time entries over the first few weeks.
About Toolqit
Toolqit is the AI-native platform where managed service provider (MSP) technicians can do all their work. It sits on top of an MSP’s PSA, RMM and Microsoft 365, syncs two ways with ConnectWise PSA, HaloPSA, Autotask and SyncroMSP, and gives technicians and operators one screen for triage, workflows, documentation, remote sessions and profitability. Toolqit, Inc. is based in San Francisco.

#73291