Weekly RevOps Leadership Deck, On Cron (L3)

Replaces the manual hour-long deck prep. A scheduled agent pings reps to refresh in-month pipeline, re-reads the thread, pulls from Slack/Linear/Snowflake, and ships the deck to leadership. Demoed by Nate Follen at Perplexity on the GTM AI Podcast.

WORKFLOW1Define deck skeleton as a…reusable skillPerplexity Computer / Claude …2Cron-trigger 24h before t…e meetingPerplexity skill / scheduler3Connect Salesforce + Snow…lake + LinearNative connectors4Re-scan thread + publish …eckAgent
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 3.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L3 Integrated. Running it above your level is how pilots stall.
Measures of successhours saved/week per RevOps lead; % deck prepped before 8am day-of; in-month pipeline accuracy; # of leadership asks captured from rep threadPROVE IT WORKEDhours saved/week per RevOps lead% deck prepped before 8am day-ofin-month pipeline accuracy# of leadership asks captured fromrep thread

The steps

  1. 01

    Define deck skeleton as a reusable skill

    Tool: Perplexity Computer / Claude Code

    Hardcode the section structure: in-month commit, project status by Slack channel, top deals, blockers, asks. The skill knows where each data source lives, that's your reusable artifact.

  2. 02

    Cron-trigger 24h before the meeting

    Tool: Perplexity skill / scheduler

    Wednesday morning for a Thursday meeting. Agent posts in #pipeline-prep: "Reply in thread with anything to include, I'll re-read this thread Thursday at 8am." Pins it.

  3. 03

    Connect Salesforce + Snowflake + Linear

    Tool: Native connectors

    Snowflake for revenue cuts (via Claude Code in Nate's setup). Salesforce for pipeline. Linear for engineering burndown adjacent to GTM initiatives.

  4. 04

    Re-scan thread + publish deck

    Tool: Agent

    Agent re-reads pinned thread, merges everything into the skeleton, drops PDF/slides in #leadership-readouts. Human spends 5 min editing, not 60 min building.

Tools in this playbook

  • Perplexity Computer / Claude Code
  • Perplexity skill / scheduler
  • Native connectors
  • Agent

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.