Uncontracted seats surfaced
$2,200 / mo
Microsoft 365 licenses billed by the distributor but not invoiced to the customer. Flagged in the first sync and now re-billed.
Customer storyHalf Past Five Technologies
Three browser tabs, one customer view.
How a Minnesota MSP consolidated its PSA, RMM, Microsoft 365 backup, and billing into a single customer-centric workspace — and put a few hours a week back on the calendar.
Services
Managed security (24×7 SOC, MDR), Microsoft 365 management & backup, help desk, virtual CIO, physical security.
What changed
PSA, RMM, Microsoft 365 backup, and billing data consolidated into a per-customer workspace. Four cross-tool rules now running. A few hours a week back across the team.
The MSP
An owner-operated stack that punches above its size.
Half Past Five Technologies serves small and mid-sized businesses out of Glyndon, Minnesota. Owner Dillon Simmons runs a stack of managed services that would fit a much larger shop — 24×7 SOC monitoring, MDR, Microsoft 365 management and backup, help desk, virtual CIO, and physical security. The team is lean, owner-operated, and the operational surface is wide.
The pain
Context lived in four places.
Every customer call started with a tab-switching routine. Open HaloPSA for tickets, jump to NinjaOne for recent alerts, log into Keepit to check Microsoft 365 backup status, then cross-reference the billing tool for what was actually contracted. Nothing tied together.
“I had four tabs open just to answer one customer question. Half the time I'd find something in one tool that should have triggered a ticket in another but didn't.”
The catalyst
A backup that failed for five nights.
A 40-user customer’s Microsoft 365 backup job had been failing for five consecutive nights before anyone noticed. The backup tool surfaced the failure in its own console. The PSA had no ticket. Nobody was looking in the right place at the right time. By the time the team caught it, the recovery window had shifted from “easy” to “uncomfortable.”
What they tried first
Dashboards on top of the same problem.
Dashboard tools, glued onto each tool’s API. Useful graphs — but graphs of data sitting elsewhere. The problem with dashboards: they show what already happened, they don’t change the workflow. The team still tab-switched, just with charts in front of them.
Why Vectis stuck
A workspace, not a dashboard.
Every other tool Dillon had evaluated was a dashboard — pretty graphs of data sitting somewhere else. Vectis is a workspace. Each customer account pulls open tickets, RMM alerts, backup health, renewals, and contract terms into a single screen, with inline actions to reply, acknowledge, or trigger cross-tool rules without leaving the page. Nothing else he tried changed the actual workflow — they just put a chart on top of it. The team adopted Vectis without formal training.
The result
What changed in the first month.
Cross-tool rules running
4 in production
Including a rule that opens a P2 ticket when a Microsoft 365 backup job fails three consecutive nights — the exact failure mode that triggered the switch.
Time recovered
~6 hrs / week
Across the team, on per-customer context-gathering — the time the techs used to spend tabbing between four tools to answer one question.
“With Vectis I’m handling it right there — tickets, alerts, backup status, licensing, billing, one screen per customer. The techs started using it without a rollout meeting.”
See what Vectis surfaces on your book.
30-day free trial on every plan. Connect your PSA, RMM, and backup tool — see every customer on one page on day one.