Support-ROI calculator
What is a quieter endpoint worth?
Price the support contacts your Windows desktops generate today, decide how many a single-purpose XPC endpoint would remove, and see the hours and cost that come back — against what the subscription costs.
How the model works
Contacts, handling time, and the rate you pay to answer them.
Endpoint support cost is contacts multiplied by handling time multiplied by your hourly cost. XPC does not change your remote desktop platform; it changes what the user can reach on the PC in front of them, which is where a specific and countable class of contact comes from. Set the reduction you believe is achievable and the rest follows arithmetically.
Your numbers
Change any value and the result updates immediately. Nothing is sent anywhere — the calculation runs in your browser.
PCs that would run XPC.
Tickets, calls and walk-ups. 0.6 means roughly seven contacts per endpoint a year.
Total effort per contact, including triage, the fix itself and any deskside attendance.
Fully loaded cost of the person handling the contact, internal or outsourced.
An assumption you set, not a vendor claim. Base it on the share of your tickets that concern the Windows desktop itself rather than the remote session.
66 hrs
Returned per year
6 hrs a month of support effort no longer spent on endpoint problems.
180
Contacts avoided per year
Out of 720 endpoint contacts in the baseline.
$3,630
Support cost avoided per year
Against an XPC subscription of $2,280 a year for the same endpoints — a net position of $1,350.
0.6 mo
Payback period
Months of avoided support cost needed to cover the subscription.
$2.00
Effective XPC rate
Per billable PC per month. 95 of 100 endpoints are billable; the first five are free.
Annual position
| Baseline endpoint support cost | $14,520 |
|---|---|
| Support cost avoided | $3,630 |
| XPC subscription | − $2,280 |
| Net benefit per year | $1,350 |
Your result, in words
XPC support ROI — 100 endpoints. Baseline: 720 support contacts a year at 22 minutes each, costed at $55.00 per hour. At a 25% reduction: 180 contacts avoided, 66 hrs returned a year, $3,630 of support cost avoided. XPC subscription for the same endpoints: $2,280 a year (first 5 PCs free, 95 billable at $2.00 per PC per month). Net position: $1,350 a year, with payback in 0.6 months. Figures are calculated from the values entered on xpc.direct/support-roi-calculator; the reduction percentage is an assumption you set, not a vendor claim.
What this does not include
Only support effort is priced. The time your people lose waiting for a fix is real and usually larger than the support cost, but it varies too much by role to model credibly here — so treat the result as a floor rather than the whole benefit.
Contacts caused by the remote desktop platform, the network or a line-of-business application are not addressed by XPC and should be excluded from the reduction you set. XPC changes what the user can reach on the local Windows PC; it does not change what happens inside the session.
Deployment labour, optional priority support and any chargeable configuration work sit outside this model. The TCO calculator covers those.
Related reading
Where the contacts go.
The mechanics behind a quieter endpoint, and the wider cost picture.
Questions
About this calculator.
Where does the reduction percentage come from?
You set it. It is an assumption, clearly labelled as one, not a vendor claim. A defensible way to choose it is to look at your own ticket categories and count the proportion that concern the Windows desktop itself — stray applications, changed settings, wrong shortcuts, users landing outside the remote session — because those are the contacts a locked, single-purpose endpoint experience removes.
Why compare against the XPC subscription?
Because the only fair test of avoided support cost is whether it exceeds what the licence costs. The calculator prices the subscription using the published model — the first five active PCs free, then $2 per PC per month, falling to $1.80 once 500 or more PCs are billable — and shows the payback period in months.
Should I include deskside visits?
Yes, in the handling time. If a class of contact routinely ends in someone walking to the desk, its average handling time is far longer than a remote fix and should be reflected in the minutes you enter. Modelling those separately with a higher handling time gives a more honest number than one blended average.
Does this include the value of user time?
No. It prices support effort only. Time lost by the person waiting for the fix is real and usually larger than the support cost itself, but it varies so much by role that including it would make the number arguable. Treat the result as a floor.
Is anything I enter stored?
No. The calculation runs in your browser, nothing is transmitted, and there is no form to complete. Copy the summary or print the page if you want to keep the result.
Test the assumption on five PCs, free.
Pick the five endpoints that generate the most contacts, run them on XPC, and compare a month of tickets against the month before.