macOS · private beta
Prepped before.Cued during.Written up after.
1cue watches your calendar, reads everything your team already knows about the account, and has the brief on screen before you dial. It follows the call while you talk. It files the write-up when you hang up.
macOS 14+ · free during beta · your notes stay on your Mac
brief built 09:58 · 6 sources · 2 people on the invite
No price has ever been said out loud — only requested. The incumbent is unnamed. Seat count is unknown.
T−90s · before
The brief is finished before you’ve found the meeting link.
No “generate” button and no blank box to type into. 1cue sees the meeting on your calendar, works out which account it belongs to, and builds the brief in the background. You open your laptop and it’s there.
It knows which call this is
Matched by who’s on the invite and what domain they email from — not by guessing at the words in the title.
Every thread with this account
What was asked, what you promised, and which question has been sitting unanswered for nine days.
Notes, decks, transcripts, PDFs
Point it at a folder. Paste a page. Drop in a contract. It reads what you give it and nothing you don’t.
Stage, amount, close date
Read-only. 1cue is the layer you work in; Salesforce stays the system of record and nothing is written back without you.
What you actually sell
Pricing, limits, integrations, the competitor you keep losing to. The part every generic AI notetaker is missing.
What the last rep learned
Accounts are shared, so someone picking up your pipeline starts with what you knew, not with an empty CRM field.
And you can check its work. Three rules the brief never breaks:
Every claim names the file it came from. Click it and you’re looking at the email, the note, or the transcript line it was drawn from.
A guess is marked as a guess. Anything 1cue worked out rather than read is tagged inference, so you never repeat it back as fact.
It tells you what it doesn’t know. “Not in the record” is a section, because the gap before a renewal call is usually the thing worth asking about.
T−0 · during
A cue at minute nine beats a transcript tomorrow.
1cue follows the conversation and puts one line in front of you at the moment it’s worth something — the number you promised, the objection you’ve heard from this account before, the question nobody has answered yet. Then it goes quiet again.
Records the call. You read the summary tomorrow, if you read it.
Hands you the thing you needed at the second you needed it, and stays quiet the rest of the time.
Transcribes what everyone said.
Tracks what nobody answered, and what you just committed to out loud.
Generic objection handling, pulled from the internet.
Your pricing, your integration limits, your competitor — because it was set up knowing what you sell.
What that looks like over twenty-two minutes:
Raj asked about uptime. 99.9% contractual, 99.97% trailing twelve. Last quarter’s incident was 41 minutes, region-scoped.
You said “we can probably do that by the 20th”. That’s a commitment — it’ll be in the write-up.
This is the partial-file retry question from 1 Sept, asked a different way. Still unanswered.
Jane hasn’t mentioned the finance committee. It meets on the 15th and she needs pricing in writing first.
T+2m · after
The write-up is filed before you’ve closed the window.
Not a transcript and not a wall of bullet points. What changed, what you promised, what happens next — in the shape a human would have written it if they had the time, which they never do.
What happened
Renewal is moving but gated on finance. Jane will not take it to committee without written pricing, and the committee meets 15 Sept. Raj pushed hard on reliability — his objection is shaped by Meridian Rx, not by anything we’ve done.
You committed to
- Written pricing to Jane by 20 Sept — said on the call at 08:40.
- An answer on partial-file retries. Asked 1 Sept, asked again today, still open.
- A single-site pilot scoped before the committee meets.
Changed since last time
- Close date still 30 Nov, but the real gate is now 15 Sept.
- Raj moved from silent to engaged — and sceptical.
- New name on the call: Dana Wu, procurement. Not in the CRM.
Worth knowing
Nobody has said a number out loud yet. The first one said will anchor the whole negotiation.
It saves as a plain file you own, and — when you connect a CRM — offers to push the summary and the next step. You approve it; it never writes on its own.
Why the brief is any good
It knows what you sell, not just who you’re selling to.
Every tool in this category models the buyer. Almost none of them model the thing you’re selling — so they can tell you Jane replied on Tuesday, but not that what she’s asking for is the one thing your integration can’t do yet.
Your product is a real object
Pricing, packaging, limits, integrations, proof points, and the competitors you actually run into. You enter it once when you set up, not every time you ask.
Two lines, two briefs
Sell more than one thing and the briefs stay separate. Each deal names its product, so the right one shows up without you picking it.
Someone else can pick it up
Everything a rep learns lands in the shared record. When an account changes hands, the next person starts where the last one stopped.
What it plugs into
It reads your sources. It doesn’t replace them.
Connect what you already use. Everything read-only until you say otherwise — 1cue is where you work, not another place to maintain.
Straight answers
The questions people ask first.
Mostly about where the data goes. Fair.
Your next call is already in the calendar.
Tell us what you sell and who you sell it to, and we’ll send you a build. Beta is small on purpose.
macOS 14+ · free during beta · no card