AI record summaries inside Salesforce or HubSpot (L1)

Turn on the summary feature your CRM already ships. Every account and opportunity gets a plain-language recap so managers stop reading raw activity logs. No integration work, no new contract.

WORKFLOW1Enable summaries for one …eam firstSalesforce2Check the summary against…the recordManual3Put the summary where the…decision happensSlack4Retire one manual reportManual
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 1.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 L1 Starter. Running it above your level is how pilots stall.
Measures of successHours saved on deal review prep; Summary accuracy sample rate; Manual reports retiredPROVE IT WORKEDHours saved on deal review prepSummary accuracy sample rateManual reports retired

The steps

  1. 01

    Enable summaries for one team first

    Tool: Salesforce

    Pick one segment. Turn on native record summaries there before you enable them org-wide, so you can compare before and after. Owner: RevOps admin. Pitfall: an org-wide switch on day one. If quality is poor you have no clean comparison. DoD: summaries appear on accounts for one team and nowhere else.

  2. 02

    Check the summary against the record

    Tool: Manual

    Review ten records by hand. Any summary that states something the record does not support gets logged. If more than one in ten is wrong, the input data is the problem, not the model. Owner: RevOps. DoD: a logged accuracy check with a pass rate written down.

  3. 03

    Put the summary where the decision happens

    Tool: Slack

    Push the opportunity summary into the deal review channel the morning of the review, so nobody prepares a separate slide. Owner: RevOps. DoD: deal reviews run off the summary instead of a manual doc.

  4. 04

    Retire one manual report

    Tool: Manual

    The point is removed work. Name the report or ritual this replaces and stop producing it. Owner: RevOps lead. DoD: one recurring manual artifact is formally retired.

Tools in this playbook

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.