agentleFS
andrerodriguesopsandrerodriguesops/gtm-engine/.claude/skills/sales-playbook/SKILL.md

sales-playbook

Skill0 starsChanged 10 days agoMITView on GitHub

The sales conversation from qualification to signature: what each call is for, the questions, objection handling with scripted answers, and pricing. Use for any sales call prep or debrief, "what do I say when they ask X", qualifying a lead, objections, or a pricing conversation. references/commercial.md is the ONLY home for prices; read it before quoting any figure.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never improvise a number. If a buyer asks for something commercial.md does not cover, say you will come back with it, and file it in …

    line 44

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sales playbook

Read first

  • references/commercial.md — what we sell and what it costs. Quote from it and nowhere else.
  • company-context — who buys and why.
  • product-context — what exists. Never claim beyond it.

The calls

<!-- One block per call in your motion. Keep the stage names the same as crm-records. -->

Call 1 — Discovery

  • Purpose: qualify, find the acute pain, earn the next meeting.
  • Win condition: a dated next meeting with the person who feels the pain.
  • Must learn: budget reality, who decides, the trigger event, how they buy.

Call 2 — Demo

  • Purpose: show the product against the pain they named. Demo to the pain, not the menu.
  • Win condition: a trial or a proposal meeting on the calendar.

Call 3 — Proposal

  • Purpose: walk the options; let them choose.
  • Win condition: a chosen option and a named path to signature.

Objections

references/objections.md — each with the scripted answer.

Pricing

Never improvise a number. If a buyer asks for something commercial.md does not cover, say you will come back with it, and file it in NEEDS.md. A custom deal is recorded in clients/<slug>/custom-offer.md with a variance table; it never edits commercial.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.