Voice · Pre Discovery · Outbound · Pipeline Discipline · Account Recon · Operationalization · Post Call Execution · Claude · Sales Execution · Cold Calling · Personal Operating System · Discovery
S01E15: Claude.... Code? But I Can't F#$&ing Code!
I am proud to be sponsored by Roku.
A click on the advertisement below goes a long way.
How Jennifer Aniston’s LolaVie brand grew sales 40% with CTV ads
The DTC beauty category is crowded. To break through, Jennifer Aniston’s brand LolaVie, worked with Roku Ads Manager to easily set up, test, and optimize CTV ad creatives. The campaign helped drive a big lift in sales and customer growth, helping LolaVie break through in the crowded beauty category.
Hey there! Thanks for being here.
In part 1 of this 3 part mini-series, we set up Claude.
In part 2 (last week), we talked about how to actually live in it. Projects. Context. Using Claude as a thinking partner across your whole day, not just for one task at a time.
This begins part 3, the last issue in the series.
And it's the one that makes everything else compound.
The problem with prompting
Here's what most reps do once they find a prompt that works.
They run it. It works. They close the tab. Next time they need it, they're back to starting from scratch. Typing the same setup from memory. Getting slightly worse output. Wondering why AI feels inconsistent.
Prompts are not single-use. They are not disposable. They're assets.

When you find a prompt that reliably produces output you can use, that prompt is worth saving. Running again. Refining. Sharing with your team.
The best salespeople I know who use AI aren't better at prompting. They're better at keeping the prompts that work.
That's what a skills library is.
What a skills library actually is
A skills library is a collection of your best prompts, organized by task, that you can grab and run without thinking.
Not a folder of half-finished ideas. Not a dump of things you've tried. A short, curated set of prompts you actually use, for the tasks you do most often.
Some people store them in a Claude project as reference content. Some people keep it in Notion or Obsidian. Some in a pinned note. The format doesn't matter. What matters is that it exists, and you actually go back to it.
Here's what mine includes:

Discovery prep brief. Paste what I know about the company and contact. Returns a call brief and five questions worth asking.
Deal gap analysis. Paste my notes from any interaction. Returns a MEDDPICC gap analysis with specific next actions.
Prospecting outreach. Paste an account name and what I know. Returns three versions: LinkedIn message, DM, cold email.
Follow-up drafts. Paste the call notes and what the email needs to do. Returns a draft I edit, not write.
Stuck deal consult. Describe the situation. Ask Claude what's missing and what it would do next.
Five prompts. They cover 80% of my repetitive sales work.
Each one took about an hour to get right the first time. Now they run in seconds and come back usable.
That's why prompts compound.
How to build yours
You already know which tasks you do on repeat. The ones where you're always starting from scratch, always re-explaining the context, always feeling like the output is almost but not quite right.
Pick one. Just one (for now).
Write a prompt that's specific enough to get useful output. Not "write me a follow-up email." Something like this:
You're helping a B2B sales rep write a follow-up email after a discovery call. Here's what happened on the call: [notes]. Here's where we are in the process: [stage]. Here's what the buyer said they would do next: [their commitment]. Write an email that advances the decision without being pushy. Short sentences. No corporate language. End with a specific proposed next step.
Run it. See what comes back. If it's close, tweak the prompt, not the output. Keep tweaking until the first draft is 90% of the way there.
Save that prompt. Name it something obvious. That's your first skill.
Then build the next one.
In a month you'll have a personal prompt library that's worth more to you than any AI productivity course.
What running your sales process from inside Claude looks like
This is where the three issues of this series come together.
You have Claude set up. Projects loaded with your context. A skills library of prompts you actually use.
A morning looks like this.
You've got three calls today. Before each one, you open your project, paste what you know about the account, run your discovery prep brief. Three minutes. Three calls prepped.
After each call, you paste your notes and run your deal gap analysis. You see exactly what's missing. You know what to do next before you close your laptop.
Between calls, you're working a new outbound list. You run your prospecting outreach prompt for each account. You're not writing from scratch. You're editing from a strong start.
End of day, one deal has been sitting too quiet. You run your stuck deal consult. Claude identifies the gap you've been avoiding. You send the email before you shut down.
That's a full sales day, run almost entirely from inside one tool, with almost no starting-from-scratch.

The skill you're building isn't prompting. It's context-loading. The rep who can give Claude the right context, fast, is the rep who gets the most useful output.
The next level: building with Claude Code
Everything above runs inside claude.ai. No technical setup required. It works for anyone.
But there's a level beyond this that's worth knowing about.
It's called Claude Code.
Claude Code is not just a chat interface, its so much more. It's a tool that sits on your computer and lets you build things. You describe what you want in plain English. It writes the code, runs it, fixes the errors, and hands you a working tool.
Even though Claude Code is way more powerful, and can actually start building exactly what you are asking for… it still has a chat interface. Meaning, you don't need to know how to code. That's the point.

How to go from using prompts, to using a system
What salespeople are building with it:
A deal scoring tool that lives in the browser. Paste your call notes, it scores the deal on buyer confidence, internal alignment, process clarity, and decision ownership. Not a chat. An actual app you open and use.
A prospect research tool. Type in a company name and a LinkedIn URL. It generates a one-page prep brief. Faster than doing it manually. More complete than what you'd pull together under time pressure.
A follow-up email generator wired to your voice. Trained on emails you've actually sent. The output doesn't need editing, it needs a read.
The difference between these and the prompts in your skills library: these are tools you own. They don't live inside Claude. They run in your browser, on your computer. Nobody else has them. They compound in a different way because you can customize them indefinitely.
This is the part of the series I said was for developers. Let me correct that.
Claude Code is for anyone willing to describe what they want to someone who can build it in an afternoon.
If you've gotten value out of this series, if you've built your project, loaded your context, and started your skills library, Claude Code is the logical next step.
It's not required. Everything in this series works without it. But if you want to go deeper, that's where to start.
Where you go from here
This is the end of the three-part series.
Part one: what Claude is, why it's better for sales, how to get set up.
Part two: how to live in it. Projects. Context. Collaboration.
Part three (this one): skills library, running your process from inside Claude, and where to go if you want to build.
Three issues. Everything you need to start using Claude seriously for sales.
If you've built your project but haven't built your first skill yet, do that this week. Pick the task you do most often. Write a prompt for it. Run it five times. Refine it until you'd use it every day.
That's the move.
Talk next week.
The Skills Library Starter Pack
Copy/paste ready prompts for paid subscribers | sellingwithai.vip
Build Webinars That Keep Working After You Stop
Webinars drive major results when they're built to perform. The Wistia Webinar Guidebook breaks down how to plan, promote, and run webinars that actually convert. Get more sign-ups, increase engagement, and turn every session into a consistent source of pipeline.

You just read the motion. Now run it.
The prompts, checklists, and templates that turn this into a 10-minute execution are in the Vault.
Get Vault Access Translation missing: en.app.shared.conjuction.or Sign In
Vault access includes:
- Copy and paste execution prompt packs
- Deal, outbound, and follow-up playbooks
- Operating checklists for every motion
- Members Vault access

