How do you get the sales playbook out of the founder's head?

Write down the founder's decisions, not their scripts. Who you sell to, who you walk away from, what you say when a buyer pushes back, and what has to be true before a deal moves forward. Then have someone other than the founder run those rules for a month and fix every spot where they get stuck. A playbook only counts once someone besides the founder can close with it.

Why is this suddenly urgent?

Because sales software now assumes you already have one.

On October 7, AnySoft made Anya, its "team sales agent," generally available. The setup is built around RevOps: configure agents once, with shared playbooks, methodology, terminology, permissions and approval rules, then give every seller a personal agent that preps meetings, drafts follow-ups in the seller's voice for review, updates the CRM and finds deals that need reviving, according to the company's press release. Its founder, Alex Noe, was VP of Product for Sales AI at Salesforce.

That's where sales tools are heading: RevOps writes the rules once, and agents apply them for every rep.

At most Series A companies, the rules live in one person's head, and that person is also the CEO. Agents multiply whatever playbook you have. If your playbook is "ask the founder," there's nothing to multiply.

What actually lives in the founder's head?

Mostly judgment calls the founder doesn't notice making.

• Which accounts deserve a second call and which don't.
• What to say when a buyer asks about price on the first call.
• When to let a deal slide and when to push for a date.
• Which competitor to take seriously and which to ignore.
• Which customer story to tell which kind of buyer.

None of that is in the CRM. Most of it isn't in the deck. The founder wins because they make these calls fast, from memory, on every deal.

How do I get it written down?

Pull it from real deals. Workshops produce values. Deals produce rules.

Review the last ten deals. Won and lost, from recordings or notes. Mark each moment where the founder made a choice: pushed, waited, walked away, changed how price came up.

Ask "why" after every founder call for two weeks. Fifteen minutes, right after the call. A new AE or a RevOps lead asks: Why did you say that? Why did you skip that question? Why did you let the date slip? Write the answers down in the founder's words.

Turn the answers into rules. "We don't take a second meeting without the person who owns the budget" is a rule. "Build rapport" isn't. A rule names a situation and a decision.

Build on the fields you have. If you already track the four founder fields (pain, economic buyer, process, next step), the playbook sits on top of them. Every rule should change what goes into one of those fields.

What goes in the first version?

One page per stage, max. For each stage:

• Entry rule. What must be true for a deal to be in this stage.
• The questions. The three the founder always asks here.
• The walk-away. When the founder drops the deal.
• The words. How the founder answers the two objections that come up most at this stage.
• The exit rule. What moves the deal forward, written as something the buyer does. A mutual action plan makes those buyer steps visible.

Skip the persona deck and the 40-page methodology for now. For the wider view of GTM work beyond sales calls, map the work first.

How do I know the playbook works?

Hand it to someone else and watch.

Your first AE runs the next batch of deals from the written version. The founder joins calls but doesn't lead them. Every time the AE gets stuck, you've found a missing rule. Write it in that day.

When the AE can take a deal from first call to signature without phoning the founder, you have a playbook. Before that, you have notes.

Only then is it worth handing to software. An agent drafting follow-ups and updating the CRM needs a written rule for what a good follow-up says and what each field means. That's where data, rules, and write-back earn their keep. Without the rules, an agent copies each rep's habits faster.

Who should own the playbook after the founder?

One person, and not the founder.

At Series A that's usually the first sales leader or a RevOps lead. They own the document, run a weekly review of lost deals, and decide what changes. The founder still gets a vote, and every rule change gets written down.

If reps get agents later, this person configures them, and the settings should match the written rules line for line.

What mistakes keep sales stuck on the founder?

• Hiring a senior AE and expecting them to figure it out.
• Writing the playbook from memory instead of from calls.
• Letting the founder keep closing every big deal.
• Buying sales agents before anyone has written down what good looks like.

What should I do this week?

1. Pull recordings or notes from the founder's last ten deals.
2. Mark every moment where the founder made a call that changed the deal.
3. Turn each one into a one-line rule: situation, then decision.
4. Draft one page for your highest-volume stage and give it to someone else to run.
5. Name the person who owns the document from now on.

A playbook only counts once someone besides the founder can close with it. Write the calls down before you buy anything that copies them.

Start Signals, Convert, Grow

FAQ

When should a founder stop running every sales call?

When the founder can explain, as rules, why the last ten deals closed or didn't. Until then, a new seller has nothing to follow.

Should the first sales hire write the playbook?

They should help by asking why after every founder call. The founder's judgment is the source. The first hire is the test that proves it's actually written down.

Do I need RevOps before I give reps AI sales agents?

You need someone who owns the rules, whatever their title. Agents set up without written rules repeat each rep's habits at higher volume.

How long should the first sales playbook be?

One page per stage. If a stage doesn't fit on a page, you've written explanations instead of rules.