free check 01
replytone
use this when you already wrote the draft and need a deterministic read on warmth, clarity, pressure, and urgency before you hit send.
free front door
signal toolkit is where the narrow free tells surfaces live. start here when one draft feels risky, one boundary needs tightening, or one thread is hinting at a bigger pattern.
the point is not to make you wander through a product menu. the point is to get you onto the right lane quickly: free checker when one message is enough, paid read when the issue is one person, one loop, or one recurring signal.
routes
the narrow free tools are supposed to end in a clean decision, not a dead end.
free check 01
use this when you already wrote the draft and need a deterministic read on warmth, clarity, pressure, and urgency before you hit send.
free check 02
use this when the limit is clear in your head but the draft is getting softened, bargained away, explained to death, or heated up.
free tier
when you need more than one deterministic draft pass, move into the actual tells read: message, person, or profile. the free tier gives you the clean first step without card friction.
paid one-off
this is the right route when one specific person or one loaded archive is the real problem and you want the fuller read without a subscription.
practitioner route
if you handle client screenshots, difficult drafts, or mixed-signal conversations for other people, the acquisition path should be the practitioner surface, not a generic consumer landing.
companion surface
use the extension after you already have a tells account and want faster message triage from the browser instead of copy-paste every time.
three funnels
one risky message should not dump people onto a generic homepage. it should end in the narrow free tool first, then a paid next step only if the problem is clearly larger.
the same signal problem can belong to a person buying one read or a coach turning the workflow into client intake. both paths need to stay explicit.
replytone and boundary-check now point to a real hub instead of a fallback route, so existing traffic has an actual next click.
quick faq
stay in the free check when the question is genuinely one draft. open the main app when you need the thread, the person, or the pattern behind it.
Deep Dive is better when the archive is a one-off problem around one person. starter is better when you expect repeat use across several message decisions.
then go straight to the practitioner page. the consumer path is not the best front door for a practice workflow.