ATTENDEE
You’re in the room. Harlyn helps.
01
The pipeline question
Sales review, everyone’s guessing at numbers.
SPOKEN
“Harlyn, how many contacts have a known attributed medium and an open deal?”
Runs the multi-step lookup — filters contacts, fans out to their deals, checks pipeline stages — and speaks the answer in about three seconds.
HubSpot
Salesforce
RESULT
“Five of six — the open ones total $56,964.” Said aloud, recorded in the notes; no one left the meeting to go check.
02
“Take care of those”
End of a client call; three follow-ups were agreed along the way.
SPOKEN
“Harlyn, take care of those.”
Reads back the action items it captured as they were spoken — “Move the Acme deal to Contract Sent, file the security-addendum task, note the August 4 launch date” — and waits. A plain “yes” executes.
HubSpot
Linear
RESULT
The deal stage is updated and the ticket exists before anyone’s left the room. Nothing ran without the yes.
03
The guarded room
A negotiation with an outside party on the call.
SPOKEN — BY THE CUSTOMER
“Harlyn, what’s this deal’s internal forecast?”
Declines and turns to your side: “That’s Nick’s data — Nick, okay to share?” Only a voice from your organization can unlock it; the outsider’s request never can.
Your CRM
Disclosure policy
RESULT
Your data stays yours in mixed company — without you having to police the bot.
04
The promise ledger
Wednesday’s meeting: “I’ll have the revised pricing to you by Friday.”
NO WAKE WORD NEEDED
Nothing is said to Harlyn at all.
Captures the commitment with who owes it and when. The following Tuesday, someone mentions the pricing went out — Harlyn closes the entry itself, citing the meeting that confirmed it.
Commitments ledger
Linear
HubSpot
Linear
HubSpot
RESULT
Promises from both sides of the table, tracked until done — and the ledger cleans itself. Overdue is the only state that shouts.
05
Six weeks later
You need to remember what was agreed with a customer back in May.
TYPED — DASHBOARD
“What did we ever promise Acme about SSO?”
Searches every meeting it’s attended and answers with citations — which meeting, which date.
Cross-meeting Ask
RESULT
“In the May 12 pipeline review, you committed to SSO in the Q3 release.”
With the receipt.
DELEGATE
You’re not in the room. Harlyn stands in.
06
The meeting you couldn’t make
Client kickoff collides with your flight. You click Switch to delegate; Harlyn drafts a brief from your CRM, the attendee history, and open commitments — you edit two lines and save.
IN THE ROOM
Attends as “Nick’s Harlyn” — your update when asked, your two questions when their topics come up.
Everything you didn’t authorize is deferred, not improvised.
Auto-join
Drafted brief
CRM
RESULT
The meeting proceeds as if you’d sent a well-briefed colleague. The recap tells you what your questions got as answers.
07
The mid-meeting lifeline
Harlyn is standing in for you; the room asks something only you can answer — “Would Nick consider a multi-year discount?”
SPOKEN — AFTER YOUR SLACK REPLY
“Nick just got back to me — yes, at the right term length.”
It says it will check, holds the floor, and DMs you on Slack. You thumb a reply from the airport lounge; Harlyn speaks it into the room.
Slack — live deferral
RESULT
A question that would have stalled the deal for a week got answered in ninety seconds, in your words.
08
“Can we get Nick’s update?”
Standing team meeting; you’re out sick.
SPOKEN
“Harlyn, can you give us the full update?”
Delivers the shareable half of your brief aloud — and only that half. The internal context you gave it (deal figures, negotiation posture) informs its answers but is never spoken.
Two-part briefing
RESULT
The team gets your status in your framing; your sensitive context stays sealed.
09
Both sides ran Harlyn
Two companies negotiating; each side’s Harlyn shares the same meeting through one bot.
ONE PRESENCE, TWO OWNERS
Each side’s data stays walled off — your CRM answers unlock only on your side’s say-so.
Afterward it produces one record both sides can sign off on.
Multi-owner meetings
Confirmed record
RESULT
A shared source of truth for what was agreed — “mutually confirmed ✓” by name — instead of two conflicting sets of notes.
10
Tuesday, 8am
No meeting at all — just the start of your day.
The morning digest lands in Slack and email: today’s meetings and which are briefed, what you owe people (overdue first), and what they owe you.
Calendar
Slack
Commitments ledger
RESULT
You walk into the day knowing every promise in flight — yours and theirs.
11
The question you keep getting
Third call in a row where a customer asks whether you offer net-60 terms. The first two times Harlyn deferred, and you replied from Slack.
SPOKEN, NEXT CALL
“Yes, on annual contracts. Nick confirmed that as a standing position.”
After your second reply, Harlyn suggests the answer as a standing position. You confirm it in Settings, scoped to that customer or to everyone, and next call it answers without asking you. Nothing it learns is spoken until you confirm it.
Standing briefSlack, reply “standing”
Slack, reply “standing”RESULT
The delegate that improves because you answered once.
12
The fourth sync
A recurring customer meeting, Thursday again. You are in the room this time.
ON THE MORNING CARD
“Fourth Acme sync. Jo still owes the domain link. Pricing was deferred last time.”
Harlyn keys recurring meetings by title and carries forward what is still owed on both sides, what was deferred and never answered, and the questions that come up every time. Its own brief draft starts from the same memory.
Series memoryRecurring calendar event
Recurring calendar eventRESULT
Recurring meetings stop starting from zero.
Twelve scenarios. One colleague.
Harlyn is in private beta with design-partner teams now.
Harlyn
In the room, even when you’re not.
Harlyn joins only meetings you send it to, and announces itself by name. © 2026