Value & ROI
Value puts a number on what Qalibr is handing back to you: the triage, dedup checking and ticket write-up your team no longer does by hand.
- Time reclaimed and Value reclaimed for the window, with a per-week read underneath.
- Bugs auto-triaged, Duplicates caught, Tickets auto-enriched — the counts the money figure is built from.
- Avg processing time — how long Qalibr’s own processing takes, against the minutes the same work costs by hand. A speed stat, not part of the money arithmetic.
Windows are 7D, 30D and MTD.
The assumptions are yours
The money figure is your run counts multiplied by assumptions you can see and change. Click Adjust assumptions to set triage time per bug, dedup check per bug, write-up per ticket, an hourly rate and a currency. Benchmark defaults are 6 min · 4 min · 5 min at $60/hr.
Assumptions are saved for the workspace, so everyone reads the same figures.
These are estimates for planning, not billing. Nothing here affects what you are charged — that’s Usage & overage.
Until you’ve routed enough bugs for the counts to settle, the page carries a [ Provisional ] tag.
Dedup rate
There’s no separate Dedup rate page. The share of reports Qalibr resolved as repeats shows up in two places: a Dedup rate · 30d tile on your dashboard home, hidden until there’s enough volume to be meaningful, and a raw Duplicates caught count here.
That dedup-rate tile counts a wider set than the Duplicate row on Reports, over a different time window. The two are not meant to reconcile.
Value vs Reports
Two different questions, two pages:
- Value — what Qalibr saved you. Hours and money, from your own assumptions.
- Reports — what actually happened to your intake. What reached your team, what keeps coming back, and whether triage is improving. No money figures appear there.