Enter your ticket mix, the minutes a manual investigation takes you, and your rates. The page runs the same rules your FlowMind dashboard uses once you are connected. Nothing here is our estimate; it is yours.
Every number above is derived from what you entered by four rules. They are the rules the FlowMind dashboard applies to real tickets, so the estimate you build here and the figure you read there are made the same way.
hours = tickets × minutes ÷ sixty
For each class, the tickets you expect FlowMind to investigate times the minutes a technician spends on the lookups and tests today. The dashboard does the same with the baseline minutes you set per class, credited only on tickets that reach a final state with a note posted.
dollars = hours × your rate
Password reset, onboarding and offboarding, service requests and Intake Navigator use your standard rate. Network, endpoint, Microsoft 365, Google Workspace and cross-domain use your senior rate, because those are the investigations a senior technician would otherwise do.
modeled = class lane × adoption + Intake Navigator lane
The value of a note is only real when a technician acts on it, so the per-class lane scales with the adoption rate you choose. The Intake Navigator lane does not: its credit already requires a technician to have created the ticket through it. The ladder shows the same four rungs the dashboard shows.
lift = hours ÷ available technician hours
Technicians times productive hours per day times business days gives the hours your desk has in a month. The hours FlowMind returns, as a share of that, is the capacity lift, applied to the endpoints each technician manages today. Rounded the way the dashboard rounds.
Connect read-only, let the investigators work on real tickets, and read the credited hours on your own dashboard.
No new tools. No new training. No commitment.