Whistleblowing & Case Management Software Pricing Compared (2026)
Before comparing quotes, it's worth understanding that whistleblowing and case management software isn't priced one consistent way across the market. The model a vendor uses shapes their incentives, and it's worth understanding before you're deep in a sales cycle and the framing has already been set by their pitch.
The four models you'll actually encounter
Per-case or per-submission pricing. You pay based on how many reports come in - sometimes a base fee plus overage, sometimes tiered bands. This is more common among smaller or newer vendors trying to keep entry pricing low. The structural problem: it creates a financial incentive, even if unintentional, for a vendor's product decisions to nudge toward fewer reports rather than more. A reporting channel that quietly gets harder to use costs the vendor less to run. That's the opposite of what a compliance product should incentivize.
Per-seat or per-user pricing. Common in general-purpose case management and ticketing tools adapted for compliance use. The problem here is definitional: whistleblowing reports aren't filed by "users" in the seat-license sense - they're filed by any employee, anonymously in many cases, who may never log in as a named user at all. Per-seat pricing on a product like this usually means only counting HR/investigator seats, which doesn't scale with the actual population the compliance obligation covers.
Opaque enterprise quoting. The NAVEX model - no published pricing, a sales call, a quote shaped by company size, perceived budget, and bundled modules. This isn't inherently dishonest, but it means every buyer is negotiating from an information deficit, and the final number can vary significantly for comparable headcounts depending on how the sales conversation went.
Headcount-based flat pricing. You pay based on total employee count, regardless of how many reports get filed or how many staff seats use the admin side. This is the model most closely aligned with how compliance regulations themselves think about scope - the EU Whistleblower Directive's own obligations trigger based on employee headcount, not report volume.
Why the model matters more than the number
A per-case model and a headcount-based model can produce similar dollar figures for a given company in a given year and still represent very different long-term incentives. If your case volume doubles next year - which might mean your reporting culture is actually working - a per-case vendor's bill doubles too, and somewhere in a renewal conversation that creates quiet pressure that shouldn't exist in a product meant to encourage reporting.
Where Rectifia sits
Headcount-only, published self-serve bands under 500 employees (roughly $59-$549/month across three tiers), and a disclosed - not negotiated case-by-case - per-head formula above that. No per-case fee, ever. This was a deliberate choice, not a default: case-volume billing was evaluated early on and rejected specifically because of the incentive problem above, and because it's structurally misaligned with how the EU Directive itself scopes the obligation.
What to actually ask a vendor
"What happens to my bill if reporting volume goes up 40% next year?" If the honest answer is "nothing changes," you're looking at a headcount or flat-enterprise model. If the answer involves recalculating a tier or triggering an overage, you're looking at a model where more employees speaking up costs the vendor's customer more money - worth sitting with for a second before you sign.