Source: raw/This_Claude_Second_Brain_Setup_Will_Change_How_You_Do_Sales_Forever.md
Creator: Ben AI · URL: https://www.youtube.com/watch?v=d7VPnW1KsgA · Duration: 24:27 · Platform: YouTube · Uploaded: 2026-07-08
Ben AI shows the “AI sales operating system” his agency runs. Raw data stays in the sales tools; scheduled routines filter it daily into a sales second brain; skills and Claude chats read the brain to do the work; a per-rep dashboard reads it to tell each rep what to do today. Ben says that a month after the dashboard went live, his rep “barely” opens the CRM, because routines keep the CRM updated too. His argument is that most people automate the work (skills) before they have automated the sales intelligence the work depends on.
Key Takeaways
- Sales is intelligence plus work. You cannot prep a call without lead research, qualify without ICP criteria, or plan without metrics. Ben says most AI-for-sales efforts skip the intelligence half.
- Five parts: connectors (raw data), routines (filter), sales second brain (intelligence), skills and chats (work), dashboard (what to do today). Work done by skills writes back into the brain so the dashboard shows it.
- Three core routines keep the brain current: a morning routine, a CRM sync and (optional) call scoring. Three long-term ones add monthly and quarterly reports and campaign metrics.
- The dashboard replaces the CRM tab, not the CRM. The CRM is still the system of record; a routine keeps it clean.
- Start with permanent context. ICP, offer, positioning and sales process docs come first because every skill and chat uses them.
The system
| Layer | What it is | Ben’s setup |
|---|---|---|
| Sales software | Raw data | Attio (CRM), Fireflies (meetings), PandaDoc (proposals), Google Workspace, Aircall, Slack, Vercel |
| Research connectors | Web and social data for lead research | Apify (LinkedIn and web scraping); for outbound, a lead database (Vibe Prospecting, Apollo or Sales Navigator) and the outreach tool |
| Routines | Daily filter from raw data into the brain | Scheduled tasks or Claude Code routines |
| Sales second brain | A folder of Markdown files | See folders below |
| Skills and chats | Do the work using brain context | About 10 sales skills |
| Dashboard | Per-rep control center | Hosted on Vercel |
Ben’s tip on Google tools: in Claude Code, use the Google Workspace CLI, which covers Gmail, Calendar, Sheets and the rest in one install.
Brain folders
calls/— each call transcript with a summary and a call score for the rep.- Context files — ICP, about-me, offer, positioning, sales process, tone of voice.
deals/— the full history of each lead: “the CRM but for AI”.intelligence/— monthly and quarterly reports.- Lead-gen campaigns — each outreach campaign with metrics, results and the sequence.
- Skills and templates — email templates, NDA, one-pager, pitch deck, proposal.
daily/and a log folder, written by the morning routine.
Each folder has its own CLAUDE.md describing its files, under a root CLAUDE.md with a routing table. In Ben’s company brain the sales OS is a subfolder under the sales team member’s folder, not a separate brain.
Routines
| Routine | Trigger | What it does |
|---|---|---|
| Sales OS morning | Daily | Reads the last 24 hours of calendar, email and call transcripts; preps today’s calls; logs yesterday’s calls; adds new deals; runs a hygiene pass; writes the daily log |
| Sales CRM sync | Daily | Checks proposal status in PandaDoc, cleans deal fields, freezes won and lost deals, flags cold deals, snapshots metrics, updates deals/ |
| Call scoring (optional) | Daily | Grades recent sales calls and saves the score next to each transcript for coaching |
| Monthly report, quarterly report, campaign metrics | Monthly / quarterly | Long-term reporting; campaign metrics only matter if you run outbound |
| Dashboard refresh | Daily | Reads the existing pages and the latest brain data, rebuilds the page and redeploys it to the same URL |
| Event-triggered | New meeting booked / meeting finished | Run call prep when a meeting is booked; draft a follow-up email and proposal after a meeting ends |
Ben runs these as cloud routines but recommends starting with scheduled tasks if routines are new to you; scheduled tasks only run while the Claude desktop app is open. His free resource contains the full prompts for each routine.
Skills
Call prep, client one-pager, lead generation, LinkedIn scraper, outreach, pipeline review, follow-up and a proposal generator. His example: “run the client one-pager for my call with Tim tonight” reads the skill’s SOP, looks Tim up in deals/, and produces a personalized sales deck. One-off work happens in a normal chat with the brain folder selected.
Dashboard tabs
- Today: upcoming calls with prep briefs, qualification scores and links; top tasks and leads.
- Pipeline: deals by stage, pipeline trends, meetings booked per week, revenue and commission, close rates, rep scores by dimension. (Ben says the figures in the video are fake.)
- Documents: offer, positioning, objections, ICP, process, tone.
- Tech stack and Automations: what is connected and what is running.
- Monthly report per rep.
Two ways to publish: a Claude live artifact, shareable only with people in your Claude team account, or a Vercel deployment (free plan) that anyone with the link can open. Tell Claude to save the dashboard HTML into the brain either way.
Try It
- Connect your CRM, meeting recorder, proposal tool, email and calendar to Claude; add Apify for lead research.
- Create a
sales/folder (or a subfolder of your existing brain) withcalls/,deals/,intelligence/,campaigns/and a context folder. - Write the ICP, offer, positioning and sales process docs first: ask Claude to interview you with 20 to 30 questions for each.
- Ask Claude to write a root
CLAUDE.mdwith a routing table and a shortCLAUDE.mdin each subfolder. - Create the morning scheduled task: last 24 hours of calendar, email and transcripts into
calls/,deals/anddaily/, plus prep notes for today’s calls. - Add the CRM-sync task once the morning task is stable.
- In Claude Code, with the folder selected, ask for “a dashboard on top of my sales second brain” with a Today tab; deploy it with the Vercel connector and add a daily refresh task.
- Point each existing sales skill at the brain’s ICP and offer files instead of its own copies.
Open Questions
- Ben’s full routine prompts are in a free resource linked from the video description; not fetched for this wiki.
- “Barely in the CRM anymore” is Ben’s report for one rep after one month; no metrics shown (the dashboard numbers are fake by his own statement).
- Live artifact sharing limit. Ben says live artifacts can only be shared with members of your Claude team account; not checked against current Cowork sharing rules.
- The paid “Sales OS plugin” (10 skills including a setup skill that builds the brain, routines and dashboard) is in his paid community; its contents were not reviewed.
Related
- Ben AI’s Second Brain Playbook — the general version of this setup
- Agentic OS Command Center (Ben AI) — three ways to build the dashboard layer
- Claude Code Routines — running the routines with the laptop closed
- Scheduled Tasks — the desktop-app version
- Cowork Live Artifacts — the artifact option for the dashboard
- Clay + Claude Code Lead Generation — an alternative lead-research layer
- Cowork + Apify Scraping Recipe — the scraping connector Ben treats as required