Phase 1 PoC · Mac desktop companion + Slack · the bidirectional coach
On connect, Dossier imports history and drafts each teammate's profile. Onboarding isn't a questionnaire — it's a 30-second review of what Dossier already inferred. You nod or tweak.
Here's what I learned about your teammates
One quick question
When engineers misread you, it's usually because…
↑ Core identity is inferred. The one thing Dossier can't guess — your pain points — is the only thing it asks.
You type in Slack as normal. Running in the background, Dossier reads the draft + sees the recipient. On a likely misread it drops a subtle chip — never blocks you. Hit ⌘⇧Space to open the full coaching.
The core surface. Three parts: how she'll read it, the missing context, and a recipient-aware rewrite. The red "how she'll read it" line is the differentiator — it's mind-reading, not spell-check. Accept writes it straight back into Slack.
Your draft
“Hey can you get the API piece done soon? Customer's been asking.”
◉ How Priya will read it
“Soon” reads as a soft, unscoped ask — she'll deprioritise it behind work that has a real date.
◎ Missing context
She doesn't know this blocks the Acme renewal closing Friday. Name the customer and the date.
✎ Recipient-aware rewrite
“The API endpoint is blocking the Acme renewal that closes Fri. Can it land by Thu EOD? If not, tell me what date is realistic.”
The mirror image, for the recipient. An incoming message assumes context you don't have — Dossier gives the plain-language gist and fills in the prior decisions and threads you weren't part of.
What he sent
“Need the Mercury config flipped before the QBR — Dana already signed off.”
◉ Plain-language gist
He's asking you to enable the Mercury feature flag for a customer demo, and says it's already approved.
◎ Context you missed
“Mercury” = the Acme pilot account (renamed in #deals last week). “QBR” = their quarterly review, this Thu. Dana approved the flag in a thread you weren't in →
The most demo-able artifact. The confirmed profile becomes a standing reference and a proactive tip surface — what lands, what backfires, what they lack. This is the coach, made tangible.
▲ What lands
Lead with the ask · give a hard date · name the customer + business impact
▼ What backfires
Vague timelines (“soon”) · burying the ask · no context on why it matters
✦ She usually lacks — and her pet peeve
Rarely has sales-pipeline context (customer names, deal urgency). Dislikes being asked to clarify timelines — so set them yourself.
✦ Built from 142 messages · sharpens as you communicate
Where the soft skill is actually built. A recipient's preferences become explicit acceptance criteria. You draft against them and get scored — no real message sent. This is what makes "coach, not autocomplete" real.
Your practice draft to Priya
“API endpoint is blocking the Acme renewal (closes Fri). Can it land by Thu EOD?”
Priya's acceptance criteria
Because Dossier reads drafts and imports history, privacy isn't a footnote — it's load-bearing. Per-channel opt-in, easy pause, and a clear promise about what leaves your machine.
What Dossier can see