saascode
Gem·customer support & success·run 148 · Jun 2026

Tolltruth

A neutral read-only meter that preserves billed events and downstream ticket states, then prepares explainable dispute candidates for customer review.

Genesis score6.41/10
Make Tolltruth real.0/500
500 more votes and Tolltruth is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Outcome-priced support products can define, measure and bill a resolution inside the same vendor-controlled system. The supplied research confirms vendor documentation for the dispute surface and independent commentary calling for audit rights or third-party validation. It did not find a neutral billing-audit product in its reviewed set.

Tolltruth imports authorized invoices, resolution events, transcripts and downstream ticket states. It applies the customer's contract-defined rules for reopen windows, escalation and exclusions, then produces explainable categories with exact evidence and uncertainty. A finance or support owner reviews each candidate and decides whether to open a dispute through the contract's process.

A reopened or abandoned conversation is not automatically overbilling; contract language governs. Customer-satisfaction data is an assertion and not proof of resolution. Missing downstream activity is not proof that an issue disappeared. Billed event, vendor classification, independent candidate, customer review, dispute, vendor response, credit, payment and service outcome remain separate.

The first release should cover one vendor contract and remain read-only. It must not accuse vendors, auto-withhold payment, contact providers, promise recovered money or pool transcript and customer data across clients without explicit rights.

Who pays — and why

Support operations or finance leader paying outcome-based fees to an automated customer-service vendor

What it unlocks
A billing ledger separating contract version, billed event, vendor classification, fee basis, invoice line, transcript availability, source retention and correction
An outcome record separating customer issue, handoff, reopen, downstream ticket, elapsed window, survey assertion, missing data and reviewer annotation
A dispute trail separating independent candidate, cited contract term, customer approval, submitted dispute, vendor response, accepted credit, payment adjustment and later correction
How Genesis scored it
6.41across seven criteria
tension 6temporal 8blindspot 5buyer 6leverage 6convergence 5why-not 8
8
Temporal window

Recent billing changes and governance concerns create a current audit window.

8
Why nobody did it

Outcome-based support billing and standardized event telemetry make independent reconciliation newly practical.

5
Convergence

The record contains two cross-references, three inbound connections and three direct connections.

Why it scored well

The supplied research confirms a measurable vendor-controlled billing conflict and a reviewed-set gap for independent read-only reconciliation.

What's holding it back

Contract definitions vary, transcript windows can be limited, buyer and budget details are incomplete, human dispute work is unavoidable and no structural copying cost is established beyond vendor conflict.

Signals detected3 sources crossed
SignalSupplied primary vendor research

SignalSupplied market research

SignalSupplied market scan

Direction brieftolltruth.md
tolltruth.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.