Check how it sounds
before you send it.
Build a persona of the person you're writing to, run your draft past them, and read their reaction in their own words — while you can still change it.
What you get back
Hey — I know the timeline's tight, but I don't think we can hit Friday without dropping the QA pass. Want to talk through options?
Agreement to move the date to Tuesday
Test one message against up to three people at once and see where they diverge — the same words rarely land the same way twice.
Which options? Give me two and your recommendation before we meet.
She reads “talk through options” as you not having decided yet. She'd rather see the call already made and be asked to confirm it.
She agrees to Tuesday without a meeting — if you name the QA risk in one line she can repeat upward
How it works
Describe someone
Answer a few questions about them, or paste a thread they're in. Takes a couple of minutes.
Draft your message
Paste what you're thinking of sending, and say what you're trying to get out of it.
Read the levels
See how they'd respond, what tips it either way, and how to steer it — before you hit send.
Why it's different
It answers as them, not about them
You get the reply they'd actually type, in their register — not a summary of how they might feel.
It shows the range, not a verdict
A real person's reaction isn't fixed. You see the likely read plus what would tip it the other way, so you tune against the range.
It remembers the situation
Who they are is stored apart from what's going on right now, so a read can account for the thread last week without you re-explaining it.
Worth a soundcheck
- Pushing back on a deadline with your manager
- Telling a client something they won't want to hear
- A cold email you only get one shot at
- A message to an audience who isn't like you
Request access
Soundcheck is invite-only while it's in testing, and access opens up a few people at a time. Tell us where to reach you.