Four episodes in, the moves are working. There's a researched cold list, a warm list dug out of the CRM, briefings on demand, and drafts written in your voice. So where is all of it right now? Scattered across chat threads, with no reliable answer to which names you've touched or when the next bump is due.
That is not a prospecting problem. It's a data problem, and it's the point where most bursts of sales energy quietly die.
This is the one episode in the track where the payoff isn't money. It's the container that makes the next episode possible.
The build is small on purpose. A Targets database, the waiting room for everyone who isn't a deal yet, with warm and cold names living side by side: name, company, why them, source, priority, status, next step. A page called "Who We Sell To," holding the ideal customer profile from earlier in the track. A page called "How I Write," built from a few of your real emails. One prompt sets up all of it and loads the database with the names you already researched, marking the ones you've emailed as contacted.
Why pages instead of chat? Because a scheduled job that runs at 6am can't read your chat history. It can read pages. That is the whole reason this episode exists. It also buys you something else worth having: if you swap Claude for a different model later, your profile, your voice, and your customer list are still sitting in Notion where any tool can reach them. No vendor lock-in.
After this, the working rhythm changes. What's due today. Brief me on the next target. I sent this email, mark them contacted, follow up Friday. You talk, it files. It isn't extra work, it's the assistant doing the CRM upkeep you were never going to do by hand.
I'm demoing it in Notion because that's the CRM we built in the last track. If you run HubSpot or Pipedrive, the same four-part prompt applies with your own source named instead. Fifteen minutes of setup, and four episodes of scattered work is finally in one drawer.