ttells / signal toolkit

free front door

pick the smallest useful read first.

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.

free checks firstpaid path only when it helpsbuilt for real send / hold / escalate moments

routes

live free checks and the exact next paid step

the narrow free tools are supposed to end in a clean decision, not a dead end.

free tier

tells main app

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.

5 reads / monthmessagepersonprofile

paid one-off

Deep Dive

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.

$19 onceup to 5,000 messagesone person

practitioner route

for coaches, mediators, and trainers

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.

practitionerpracticeenterprise

companion surface

chrome extension

use the extension after you already have a tells account and want faster message triage from the browser instead of copy-paste every time.

paid companionselection flowbrowser-first

three funnels

what this page is supposed to do

free-to-paid without confusion

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.

consumer and practitioner both stay visible

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.

each micro-tool stops being an orphan

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

two questions most people are really asking

should i stay free or open the main app?

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.

when is Deep Dive better than starter?

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.

what if i work with clients, not just my own messages?

then go straight to the practitioner page. the consumer path is not the best front door for a practice workflow.