The Revenue AI Report

Notion-Native Account Plan Agent, "Yes Chef" (L3)

5 chained prompts in Notion AI generate a full account plan, stakeholder map, tiered contacts, history, recommended actions, in 90 seconds. Killed the 6-week change-management drag of rolling out account planning. By Justin Dries, Director of Sales Enablement at Legora, on the GTM AI Podcast.

WORKFLOW1Use Notion as the RAG, no… a separate vector DBNotion2Use ONE agent with named …nstructions, not manyNotion AI3Build prompts by talking …o Notion AI itselfNotion AI4Make the trigger phrase n…n-negotiableManual5Be twice as clear about w…at you DON'T wantPrompt design
5 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 successtime-to-account-plan (target: <2 min); % of named accounts with a current plan; sales-cycle compression on planned vs unplanned accounts; # of training hours replaced by agentic enablementPROVE IT WORKEDtime-to-account-plan (target: <2min)% of named accounts with a currentplansales-cycle compression on plannedvs unplanned accounts# of training hours replaced byagentic enablement

The steps

  1. 01

    Use Notion as the RAG, not a separate vector DB

    Tool: Notion

    If your team already lives in Notion, your RAG already exists. All product marketing, use cases, ICP docs, internal playbooks → the agent reads them natively. No separate retrieval system to build.

  2. 02

    Use ONE agent with named instructions, not many

    Tool: Notion AI

    Notion's unlock: one agent + multiple instruction pages. Justin runs "Account Planner," "Pat GPT" (how the CRO would read your plan), "Max GPT" (how the CEO would read it). Each instruction is just a Notion page, humans can edit it.

  3. 03

    Build prompts by talking to Notion AI itself

    Tool: Notion AI

    Don't prompt-engineer in a vacuum. Tell Notion AI what you want, let it draft the prompts, iterate. 5 chained prompts is what Legora landed on, stakeholder mapping → tiering → history → recommended action → consolidation.

  4. 04

    Make the trigger phrase non-negotiable

    Tool: Manual

    Legora's kickoff theme was "Yes Chef." The agent only fires when the rep types "yes chef" on a new account plan template with the account name in the title. Forces rep adoption to be one keystroke, not a checklist.

  5. 05

    Be twice as clear about what you DON'T want

    Tool: Prompt design

    Justin's rule: be very clear about what you want, twice as clear about what you don't want. Lists stale Slack channels to exclude, deprecated product docs to ignore, etc. Raises the floor of output dramatically.

Tools in this playbook

  • Notion
  • Notion AI
  • Manual
  • Prompt design

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.