Prep sales meetings with AI

Coco builds the pre-meeting brief while you sleep: account context, deal state, recent activity, risks to address, talking points, and a draft of the post-meeting follow-up. About 8 credits per brief. Each brief lands in your inbox the morning of the meeting, or whenever you've scheduled the watcher. Once you've run the meeting, Coco drafts the follow-up email and any CRM updates for your approval. The 30 minutes of prep per meeting becomes 5 minutes of review. Prep gets faster; the meeting itself still depends on you.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

What's in a pre-meeting brief

A Coco brief is structured for the way an AE actually uses one: to walk into a meeting prepared, not to read an essay. The sections are consistent so you know where to look:

• Account snapshot. Company name, stage, employee count, industry, recent funding. Pulled from your CRM and enrichment sources, with the last-updated timestamp visible.
• Deal state. Current stage, amount, owner, days in stage, last activity, next-step task if any. From HubSpot or Salesforce.
• Recent activity (last 90 days). Touches, replies, meetings, CRM changes, anything material. The thread Coco saw, not just the metadata.
• Public signals. News in the last 30 days, hiring posts, LinkedIn or podcast commentary from the people in the meeting.
• People in the room. Attendees pulled from the calendar invite, with each person's role, recent LinkedIn activity, and any prior contact history with your team.
• Suggested talking points. Three to five anchor points, each tied back to the activity or signal it came from. Not a script; a set of openers.
• Deal risks to surface. Concrete items: pricing question unaddressed, decision-maker who hasn't been on a call yet, competitor named in the last meeting, silent for X days at this stage.

About 8 credits per brief at standard depth. The plan card shows the credit cost and the time before anything runs. You configure the template once and Coco follows it across briefs.

How Coco runs the brief

The watcher pattern is what makes the brief land before you need it.

1. Calendar watch. Coco connects to Google Calendar and watches for external meetings (anything with an attendee whose email domain isn't yours).
2. Trigger at your lead time. For each external meeting, Coco kicks off a brief at the lead time you set. Default is 7am the morning of the meeting; common alternatives are the night before or 60-90 minutes ahead.
3. Pull context across tools. CRM data, email history, call recording transcripts if connected, LinkedIn signals, news. Coco doesn't transcribe calls itself but it can read transcripts your call-recording tool produces.
4. Synthesize. The brief comes together as a structured document. About 8 credits per brief; faster lookups cost less, deep public-signal research costs a few credits more.
5. Land in your inbox. The brief is delivered as an email summary (or Slack DM, depending on your config) with the full brief either inline or linked. Read time: about 5 minutes.

Watchers are a Founder-tier capability. On the Hobby tier you can run briefs ad-hoc instead, triggering them manually before each meeting.

From brief to follow-up

The post-meeting drafting runs on the same workflow. After the meeting, Coco drafts the follow-up email and any CRM updates for your approval.

The landing page's sample ask is the anchor: "Prep tomorrow's Mercury call, flag risks, and draft the post-meeting follow-up." Both halves run in one job. You hand off the prep work and the after-work in the same instruction.

The post-meeting follow-up draft references the actual meeting outcome: call notes from your transcription tool if connected, your own quick notes if you add them, the deal-stage change if any. About 3-5 credits per follow-up draft. It queues in Gmail drafts; nothing sends without your approval. For the broader follow-up workflow across deals, see how Coco automates sales follow-ups.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Risks Coco surfaces

The risks section is the part most AEs find load-bearing on a busy week. Examples of what Coco flags:

• Deal silent more than your threshold. "Mercury was active through April; the thread went quiet on May 3rd. The last open item was a pricing question. You haven't followed up."
• Decision-maker missing. "Two product managers and a director have been on calls. The VP whose budget this comes from hasn't been in any meeting yet."
• Pricing question unaddressed. "On April 22nd, Maya asked about volume discounts at 5,000 seats. The thread continued without an answer. Worth surfacing today."
• Competitor mentioned. "In the last call, the prospect named Outreach as the incumbent. You haven't surfaced the wedge against Outreach in any subsequent touch."
• Procurement signal. "Their legal team requested an MSA on May 8th. The draft is in your sent folder but no acknowledgment."

Each risk is tied to a source (the call note, the email, the CRM event) so you can verify quickly. False positives are flagged for dismissal with one click. The risks that matter compound from meeting to meeting because Coco remembers what you've already addressed.

Why this beats Gong, Chorus, or your own pre-call notes

Call recording tools are good at what they do. They show you what was said: the transcript, the topics, the sentiment, the talk-track analysis. They're observation tools, anchored to the calls you've already had.

Coco's job is the prep: what's about to happen, and what should you do about it. Different category, different output. If you have a call recording tool, Coco reads its transcripts as one input to the brief; it doesn't compete. Coco synthesizes what you have into a one-page document you can walk into the meeting with.

The other alternative, writing your own pre-call notes, is the right tool when you have the time. Most AEs don't, and the prep ends up being a 5-minute skim of HubSpot in the elevator. The brief turns that into a structured read on the same elevator, with risks and talking points already surfaced.

The approval gate model still applies. Coco never updates your CRM or sends a follow-up without your sign-off the first time. See how Coco's approval model works for the full trust model.

Frequently asked questions

When does Coco run the brief?

Configurable per workflow. Defaults are 7am the morning of the meeting, but common alternatives include the night before (good for evening prep) or 60-90 minutes ahead (good for back-to-back days). You can also trigger ad-hoc whenever you want.

Does Coco pull notes from call recordings?

Yes, if you've connected your call recording tool's transcripts (Gong, Chorus, Fireflies, etc.). Coco reads the transcripts as one input to the brief; it doesn't run its own transcription. The integration depends on the call-recording tool's API surface.

Can I tell Coco to focus on certain types of risks?

Yes. Set guardrails per meeting type or per deal stage: "for enterprise deals, surface procurement risks specifically," "for renewals, prioritize usage and engagement risk." The rules stick for future briefs in the same workflow.

Will the brief be in the right format for my team?

You set the template once: sections, order, what to include, what to drop. Coco follows it across briefs. Teams typically tune the template once at setup and leave it.

Can I share the brief with my team?

Yes. Coco can post the brief to a Slack channel, share via your CRM activity feed, or email it to the meeting attendees on your side. Each delivery destination gates on your approval the first time, then runs inside the rule you set.

Get started

Connect your calendar and your CRM. Pick one meeting this week (ideally one you'd otherwise spend 30 minutes prepping for) and hand Coco the brief.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Or book a walkthrough → if you'd rather see a brief run on a real account first.