saascode
ecommerce, retail & dtc·run 156 · Jun 2026

Toneproof

A self-serve guardrail layer for commerce voice experiences that versions approved claims, returns and pricing rules, disclosures, escalation, tests, runtime blocks, and per-call evidence.

Genesis score6.38/10
Make Toneproof real.0/500
500 more votes and Toneproof 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 opportunity
0Direct commerce voice policy apps
1Confirmed horizontal competitor
The case

Commerce voice widgets can speak with customers before a merchant has formalized brand claims, return exceptions, pricing authority, disclosure language, escalation, or incident evidence. Research found a live horizontal policy-enforcement product but no commerce-native voice policy app; its API was still listed as coming soon. Toneproof turns approved policy into versioned runtime checks and safe fallback. The source confirms an August 2, 2026 Article 50 date and draft May 2026 guidance, but applicability and final guidance require qualified review. Geolocation is only one uncertain signal, not a compliance switch. A call receipt records observed inputs, checks, blocks, disclosure, and output; it cannot prove the whole conversation stayed compliant or that the customer understood it.

Who pays — and why

The ecommerce, customer experience, brand, legal, or operations owner deploying a third-party or custom voice assistant on a storefront.

Market signalValidate per store and call volumeNo observed market reference in the source; validate before fixed product pricing
What it unlocks
A versioned policy pack for identity, disclosures, brand claims, product facts, pricing, returns, refunds, promotions, privacy, prohibited content, and escalation.
Pre-deployment scenario tests and runtime checks that distinguish allowed response, safe rewrite, reviewed fallback, transfer, block, and unknown policy state.
Per-call evidence linking policy and agent versions, locale signals, disclosure, checks, proposed and spoken output, provider acknowledgment, transfer, correction, and outcome.
How Genesis scored it
6.38across seven criteria
tension 7temporal 8blindspot 5buyer 6leverage 8convergence 5why-not 5
8
Temporal window

The source confirms an August 2, 2026 date and May 2026 draft guidance, creating an immediate review window.

8
Asymmetric leverage

Policy packs, tests, runtime checks, evidence, and exports are code-scalable.

5
Why nobody did it

The deadline and voice-widget growth sharpen the need, but policy guardrails are an established pattern.

Why it scored well

The dated disclosure signal, horizontal enforcement validation, and missing commerce-native voice layer support a low-friction software wedge.

What's holding it back

The buyer quartet is incomplete, one original-stage interface was unverified, guidance was draft, runtime coverage is technically hard, and incumbents can add policy controls.

Signals detected3 sources crossed
SignalRegulatory research

SignalGuidance research

SignalMarket research

Direction brieftoneproof.md
toneproof.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.

Toneproof — Genesis · saascode