Meeting Prep & Pre-Call Briefs
Good sales engineers prep for every call. They just do it at 11 PM, re-reading transcripts and scrolling back through Slack. Opine does that reading for you, and the brief is waiting the day before the call.
trusted by the world's
highest performing revenue teams
What's in a brief, and where it came from
Every meeting linked to a deal gets one. This is a real brief, marked up with what goes into building it.
Halcyon Health · Technical deep dive
Thursday 10:00 · 60 min · 4 attendees · linked to the Halcyon Health opportunity
Meeting purpose
Second technical session. Last time, Priya asked for the data-residency answer in writing, and Marcus held the timeline until security signs off.
Mar 4 call · 32:14
stage · close dateEvery deal meeting, automatically
Any upcoming meeting with attendees that's linked to a deal gets a brief. Nothing to request, no template to fill in, no rule to remember.
Participant intel
- Priya RamanVP PlatformChampion. Ran the last two sessions. Cares about failover.
- Marcus WebbSecurity leadFirst time on this call. Blocked the incumbent's renewal in January.
- Dana OrtizProcurementJoins for pricing questions only. Has never seen a demo.
invite · 4 attendees3 prior callsBuilt from the deal, not the last call
Conversation insights, participant history, thirty days of activity, open tasks, key qualification fields, and the latest CRM status.
Discussion points & objection handling
- Walk the failover path end to end. It's what stalled the last session.
- Confirm the EU data-residency commitment in writing, as Priya asked.
- Get Marcus to name what security needs before he'll sign.
“What changed since the last SOC 2 audit?”
Point at the June report. It’s already shared with Priya, and Marcus hasn’t seen it.
3 calls
#halcyon-evalA run of show, not a recap
What to raise, the objection to expect, the answer already sitting in the record, and what to send before you dial in.
Pre-meeting tasks
- Send Marcus the June SOC 2 report. He has never seen it.
- Ask Priya whether Dana needs to be on this one.
Timed agenda
- 0–5Where we left off
- 5–20Data residency, in writing
- 20–35Failover walkthrough
- 35–50What security needs, and who signs
Risks & data gaps
Legal review hasn’t started, and the close date is 19 days out. Three things the record doesn’t know:
It names what the record doesn't know
The gaps come back as questions to ask, so the call closes them instead of the record staying thin for another three weeks.
one reminder per meeting, in the 24 hours before it · declined meetings never trigger a briefA recap reads the last call. A brief reads the deal.
Your meeting tools can summarize the hour they recorded. At 9:55, that isn't what you need. Opine keeps every call, thread, task, and field change on one record per opportunity, so the brief opens with what your buyer asked for three weeks ago, who blocked it, and what you already promised in writing. The whole deal, not the last hour of it.
Walk in already prepared
The prep still happens. It just stops happening at 11 PM, and it stops being the thing that gets skipped when the day runs long.
Prep you never have to remember
Every deal-linked meeting gets a brief, including the one that landed on your calendar this morning.
A run of show for the hour
Discussion points, objection handling, a timed agenda, and the tasks to clear first. Follow it or change it, but never start from a blank page.
Know what the record doesn't
The things nobody ever wrote down come back as questions to ask, so the call fills them in.
It finds you before the call
One reminder in the 24 hours before, by Slack, Teams, or email, with the full brief on the calendar event itself.
Asked in real demos
The questions that come up when technical sales teams stop prepping by hand.
Have one we didn’t cover? Bring it to the demo →
vs. call summariesWe already get a summary after every call. Isn't this the same thing?
A recap looks back. A brief looks forward. A call summary covers the hour it recorded. The brief covers the opportunity: what the buyer asked for three weeks ago, who has joined since, what's still open, and what to expect in the next hour. It's built from calls, threads, tasks, and fields together, and it lands before the meeting instead of after it.
What it isIs it a recap, or does it tell me how to run the meeting?
A run of show. Critical discussion points, the objections to expect, the tasks worth clearing beforehand, a timed agenda, and the risks to navigate. The recap of what happened last time is in there, but it's the first section, not the whole document.
New attendeesWhat if someone gets pulled into a call last minute, with no history on the deal?
The brief is built from the deal's history, not yours. A specialist who has never touched the account opens exactly what the deal owner opens: what happened on every prior call, who's in the room, what's still open. The data-gaps section flags what the record genuinely doesn't know, so nobody walks in assuming coverage that isn't there.
CoverageWhich meetings actually get a brief?
Upcoming meetings with attendees, linked to a deal. Internal blocks and personal events don't trigger anything, and neither does a meeting you declined or one that was cancelled. Deal-linked meetings get a brief, with at most one reminder per meeting per day in the 24 hours before it.
ParticipantsDoes it use history from prior meetings with the same people?
Yes. Participant intel is one of its inputs. The brief draws on each attendee's history with your team, so it can tell you who ran the last session, who went quiet after pricing, and who is new to the conversation. How much per-person history it pulls in is something we're actively deepening.
ControlCan we shape what a brief looks like?
Yes, at the org level today. Custom instructions control the structure and tone of every brief, so a security-led team and a platform team don't get the same shape. Per-user personalization is in early access.
AccuracyHow do I know the brief isn't making things up?
It reads the record, and it says where the record is thin. The brief is generated from the deal's own material: transcripts, threads, tasks, fields, and the technical sale, not summaries of summaries. When the record doesn't hold an answer, the data-gaps section names the gap rather than filling it in.
Proven in the field
Technical sales teams run their pipeline on Opine. The results are public.
“I’ve used countless presales tools over the years, and I can confirm that not a single one comes close to what Opine is doing. Because of their platform, win rates are up, SEs are more efficient, and leadership has access to never-before-seen pipeline intelligence. It’s amazing.”
Shaun Dolan
Director of Solutions Engineering at Orca Security
