Syntic
All playbooks

Playbook

Sales 6 min read

Source insights from your tools to build a deck

Your AI Account Director Employee pulls every signal — call transcripts, CRM activity, product usage, support tickets — and ships a customer review deck ready to present.

The request

"Build the Q3 business review for Acme. I want the wins, the open risks, the product usage story, and one bold next step. Pull from Gong, HubSpot, Mixpanel, and Zendesk. Ship a slide deck in our template."

What the Director sources

  • Gong: every call from the last 90 days — quotes, themes, tone shifts.
  • HubSpot: deal stage history, NPS, churn risk score, exec relationships.
  • Mixpanel / Amplitude: usage trend per workspace, feature adoption, drop-offs.
  • Zendesk: ticket volume, top categories, resolution time, anything escalated.
  • Drive: the master template, the previous QBR, any notes the AE attached.

How the Director thinks

It doesn't dump the data. It looks for the story: where the customer is winning, where they're stuck, and what changed since the last review. Each finding gets tied to a specific signal — a quote from a call, a chart from product usage, a ticket with a name on it. Nothing in the deck is unsourced.

The deck it ships

  1. One-slide summary — health, momentum, the one bold next step.
  2. Wins since last QBR — outcomes the customer asked for, with proof.
  3. Usage story — adoption curve, the workspaces that are humming, the ones that aren't.
  4. Open risks — what could shrink the account, with the mitigations.
  5. What we're proposing — the next step, with the impact case and the ask.
  6. Appendix — every chart and every source, in case anyone wants to dig.

Stay in your voice

Drop your last three winning QBRs into Projects. The Director matches the tone, the slide structure, and the level of detail you actually use. Customers shouldn't be able to tell which deck you wrote and which one your Employee did.

Follow-up dispatches

  • "Draft the email I send the day before — context, agenda, and the one slide they should pre-read."
  • "Build a one-page exec summary I can leave behind with the CFO."
  • "After the meeting, capture the action items from the recording and ship the follow-up email."

Tip

Ask the Director to flag any slide where the evidence felt thin. You'll either go pull a better source — or know exactly where to lead the conversation when you present.

Run this play yourself

Spin up Syntic free and bring your context. Most teams ship their first dispatch in under an hour.