Write Your Sales Playbook Once: Claude Skills for Small-Team Follow-Up

• In this note:
• What a skill is
• Write the playbook
• Keep a person in charge
• Try it
• Your notes

Most small business owners and nonprofit leaders I talk with know their sales process works. They have the right answer for a curious prospect, a good follow-up email, and a sense of who is ready to buy. The trouble is time. A reply sits for two days, a follow-up never goes out, and each email gets written from scratch because the good version lives in someone’s head.

That gap is costly. In “The Short Life of Online Sales Leads,” published in Harvard Business Review, James Oldroyd, Kristina McElheran, and David Elkington reported that most companies are not responding to online leads nearly fast enough. A small team rarely has a sales assistant to close that gap. A well-built AI skill can do part of that job.

What a Claude skill is, in plain terms

The Claude Help Center describes skills as “folders of instructions, scripts, and resources that Claude loads dynamically.” In practice, a skill is your playbook written down once. When you ask Claude for help with a matching task, it finds the skill and follows it.

That matters for sales because consistency is the point. A skill can hold your voice, your offers, the questions prospects ask most, the follow-up schedule you use, and the rules for what never goes out without you. The Help Center lists skills on the Free, Pro, Max, Team, and Enterprise plans, with code execution turned on. Plans and settings change, so check the current article before you start.

How the skill creator works

You can write a skill file by hand, but most owners will not need to. Claude Academy’s tutorial on creating a skill through conversation lays out the steps:

• Describe the task in a new chat and upload what shows your approach: your best emails, a pricing sheet, a call script.
• Answer Claude’s questions about how you do the work. The tutorial suggests giving enough detail that “someone capable but unfamiliar could follow your approach.”
• Let Claude build it. Claude reads its skill-creator skill, writes the main instruction file (called SKILL.md), organizes your materials, and packages the skill.
• Save it, turn it on, and test it in Settings, under Capabilities and then Skills. When Claude uses it, you see the skill’s name in its thinking. If the result is off, ask Claude to update the skill and test again.

The skill creator helps you write the playbook

A skill can only follow the process it is given, and in many small teams that process has never been written down. It lives in the owner’s head and in old emails. The skill creator’s questions draw it out with you: which replies you get, what each one means, what you say back, and what changes in your CRM (customer relationship management system) afterward. Bring real examples, and answer as if you were training a new team member.

Anthropic’s guide to creating skills offers three useful rules. Build a skill only for work you repeat: the guide suggests asking whether you have done the task at least five times and expect to do it ten more. Keep each skill to one purpose. And write the description carefully, because the description decides when the skill is used; the guide calls it “the most critical component.”

My own business development work runs on skills like these. A reply playbook skill sorts each new reply by type and drafts a response, and I read and approve every draft before it goes out. I also used the skill creator to build the brand guide skill that keeps StrideForward drafts in my voice. These are my own tools in my own work, so I treat them as working examples rather than proof of results for every team.

Keep a person in charge of what matters

Human-centered AI starts with deciding what stays with people. For sales, I keep these with a person: anything sent to a prospect, any price or commitment, and any reply that is unusual or sensitive. Write those rules into the skill itself, so it drafts and flags instead of guessing.

Name the information the skill may use and what it must never share. Then test it the way the Anthropic guide recommends: with a normal case, an odd case, and a request it should decline. Keep changing the skill until all three come back the way you want.

What an AI workflow engagement looks like

When StrideForward sets up sales skills for a small team, the work is short and specific:

• Map the sales process with the people who do it: where leads come from, what happens next, and where follow-up slips.
• Write the playbook: reply types, follow-up timing, voice, and what never goes out without a person.
• Build two or three skills with the skill creator, test them with your real past emails, and connect them to the tools you already use.
• Train the team and hand it over, so people know how to run each skill, check its work, and change it.

Signs a sales skill would help

• New leads wait more than a day for a first reply.
• Each follow-up email is written from scratch.
• Only one person knows how to answer the common questions.
• Your CRM is out of date by Friday.
• You prepare for calls by scrolling through old emails.

If two or more of those sound familiar, one sales skill is a good place to start.