Ops

Compress the pre-call into three slides

Call books. Deep Research the pair of value props. Dump nothing. Slack the brief. Three slides, then twenty minutes of discovery.

The loop

  1. 01Start when the call is bookedThe trigger is the calendar, not a weekly research block. No meeting, no brief.
  2. 02Pull their value prop, then yoursChatGPT on the customer. Cross-ref the seller’s own story (he used TestBox). Two sides, not a company dump.
  3. 03Run the pair through Deep ResearchThe long read happens here. You are allowed twenty-five pages of research. You are not allowed to hand twenty-five pages to a rep.
  4. 04Compress into a Google Doc briefThe artifact is the compression. If the seller still has to hunt, you dumped.
  5. 05Zapier the Slack ping and three slidesBrief hits Slack before the call. A Google Slides POV deck auto-populates. Discovery is about twenty minutes. The deck is three slides.
gtmshift.substack.com ↗Twenty-five pages in. Three slides out.When a call is scheduled, ChatGPT pulls a high-level value prop on the customer, cross-refs the seller’s own value prop, runs the pair through Deep Research, compresses it into a Google Docs brief, and Zapier pushes Slack plus a Google Slides POV deck before the meeting. Twenty-five pages of research get compressed, not dumped. About twenty minutes of discovery, then three slides.

Most pre-call research is a tab explosion the seller never reads. James’s version is a box that fires when the meeting lands: two value props, one Deep Research pass, one short doc. The point is what gets deleted.

The interesting constraint is the deck, not the model. Twenty-five pages can go in. Three slides come out. Twenty minutes of discovery, then the POV. Zapier is only the last mile — Slack and Slides — so the work is already done when the seller looks.