Prepare first meetings, follow-ups and post-close calls from the questions and commitments that matter at each stage.
Book a demo and see how Cedar helps you process your inbox in a fraction of the time.
Good meeting prep answers three questions: what do we know, what changed, and what decision should this conversation move forward? A company summary alone rarely answers them.
Cedar's meeting-prep workflow uses different instructions for first meetings, follow-ups and post-close conversations. That distinction matters: a first discovery call should uncover the buying problem, while an implementation check-in should resolve commitments already made.
Separate researched account facts from assumptions about the buyer. Review the attendee's role, the reason for the meeting and relevant account context. Then prepare questions that test the hypothesis. A hiring announcement might suggest growth; it does not prove that this person has a budget or an urgent operational problem.
A useful brief contains the meeting objective, known attendees, the evidence behind the account hypothesis, and three questions that would change the next step. Leave unknowns visible rather than filling the page with plausible details.
A second meeting should not restart discovery. Read the previous conversation and subsequent messages. What did each side agree to do? Which document was shared? Did a new stakeholder join? Is a security question still unanswered?
For a fictional example, Northstar agreed to invite its operations lead and share a sample export. The export arrived, but the invitation has not been confirmed. The brief should highlight that difference and suggest confirming who will evaluate the workflow. It should not say the buying committee is engaged merely because someone promised an introduction.
| Brief section | What belongs there |
|---|---|
| Goal | The decision or agreement to advance today |
| What changed | New messages, attendees or evidence since the last call |
| Open commitments | Owner, promised date and current evidence of completion |
| Questions | The unknowns that block progress |
| Suggested next step | A proposal for the rep to validate with the buyer |
After a deal closes, the brief should shift toward rollout. Review agreed scope, milestones, owners and blockers. A promised integration is not a completed integration. A planned kickoff is not proof that onboarding started. Keep the distinction clear so the customer does not have to repeat the sale to the delivery team.
In Cedar, meeting prep can be delivered in Slack as well as the workspace when configured. A full, readable brief is more useful than a notification that requires another search. Confirm that the connected recording and messaging sources cover the meetings in scope; context can only arrive after those sources provide it.
Ask reps whether the brief surfaced a useful change, avoided a repeated question or clarified an open commitment. Track corrections and missing sources. Faster preparation is valuable, but a shorter brief that misses the buyer's concern is not an improvement.
Pair preparation with a buyer-timed follow-up workflow and a clear customer handoff. Explore meeting prep in Cedar.