← Back to the catalog
B4SALES & REVENUE

Meeting prep briefs

Before a scheduled customer or prospect meeting, generates a concise briefing document for the person taking the meeting: who's on the other side, what their company has been doing recently, what the relationship history with them looks like, what was discussed in prior meetings, what's currently outstanding. Replaces the 15-20 minutes of frantic research that most reps either do badly or skip entirely. Lands in the rep's morning email or calendar event so they read it before the meeting, not during it.

WHERE THIS FITS
BUSINESS SHAPES
B2B servicesProfessional servicesProduct company
VOLUME THRESHOLD
Below 5 external meetings per rep per week a month, the payback rarely earns the build. Patterns this shape reliably pay back at 15+.
FITS BEST
Mid-market sales motions where prep matters and reps are time-constrained.
PAYBACK · 5-8 moBUILD · Low-MediumVALUE · $25k-$90kWHEN · reps running 4+ meetings/day
FAILURE MODE TO DESIGN AROUND
Briefs read but not acted on → measure quality via post-meeting feedback.
REQUIREMENTS · 4 REQUIRED, 1 OPTIONAL

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

  1. calendar_source
    REQUIREDREADbatch

    Where upcoming meetings live. The pattern reads from here to know when and what to prep.

    DATA SHAPE
    Calendar events with attendees, time, title, location, any meeting notes attached to the event.
    COMMONLY FILLED BY
    • primary work calendar (Google, Outlook)
    • shared team calendar with customer meetings
    • calendar managed by a scheduling tool
  2. contact_and_company_records
    REQUIREDREADrequest

    Who the attendees are, what role they have, what company they're at, what the firm's relationship with that company is.

    DATA SHAPE
    Contact records by email address; company records; deal or account context.
    COMMONLY FILLED BY
    • CRM lookup by attendee email
    • internal directory plus customer database
    • combined view across CRM and customer success tool
  3. interaction_history_archive
    REQUIREDREADcorpus

    What the firm has already done with these people: prior meetings, emails, support tickets, deal stages. Lets the brief reference real continuity rather than starting from scratch.

    DATA SHAPE
    Interaction records linked to the contact or account: emails, call summaries, ticket history, prior meeting notes.
    COMMONLY FILLED BY
    • activity log in the CRM
    • transcripts and summaries from A4 if that pattern is also live
    • email archive with sender/recipient indexing
    • support ticket history per customer
  4. external_intelligence_source
    RECOMMENDEDREADbatch

    Public news and signals about the company being met: funding, leadership changes, product launches, hiring patterns.

    DATA SHAPE
    Per-company recent events with date, source, and relevance signal.
    IF MISSING
    Briefs cover internal context well but miss external context. Reps still get value but the 'did you see they raised a Series B last week' quality erodes.
    COMMONLY FILLED BY
    • news monitoring service
    • company-news section of an enrichment data provider
    • manually curated alerts from sales operations
  5. brief_delivery_channel
    REQUIREDWRITEbatch

    Where the brief reaches the rep. Important that it reaches them before the meeting, not after they're in it.

    DATA SHAPE
    Structured brief: meeting context, attendees with one-line summary each, company snapshot, relationship history highlights, open items, suggested talking points.
    COMMONLY FILLED BY
    • morning email digest with the day's briefs
    • attachment to the calendar event itself
    • Slack DM the morning of the meeting
    • card in the CRM tied to the deal
RUNTIME FLOW · 6 STEPS
  1. 01
    Each morning, scan the day's and next-day's calendar for external meetings
    calendar_source
  2. 02
    For each meeting, identify attendees and look up their contact and company records
    contact_and_company_records
  3. 03
    Pull recent interaction history with each attendee and with their company
    interaction_history_archive
  4. 04
    Query external intelligence for recent newsworthy events at the company
    external_intelligence_source
    DECISION Skip if external_intelligence_source not filled.
  5. 05
    Synthesize the brief: context, attendees, company snapshot, relationship history, open items, suggested questions or talking points
  6. 06
    Deliver the brief through the configured channel, timed to arrive before the meeting
    brief_delivery_channel
EMISSIONS · 2

Structured outputs this pattern produces. Other patterns and client systems can subscribe to them, which is how the catalog composes over time.

  • meeting_prep_signal

    Briefs generated per rep per week, useful as a leading indicator of meeting volume and prep coverage.

    CONSUMED BY
    • sales activity dashboards
    • rep coaching reviews
  • open_items_signal

    Open commitments and unanswered questions surfaced across briefs, useful as a follow-through health metric.

    CONSUMED BY
    • sales leadership monthly review
    • account hygiene workflows