Sales Playbook

Builds the argument for a sales conversation on one topic. Not just the evidence: what the workaround costs them, how you are positioned against the competitor they named, and which objections to expect.

/closedloop-sales-playbook checkout flow @ Adventure Works

Arguments

Argument	Required	Default
Topic	yes
`@ <company>`	no	general playbook across all customers

Naming a company switches it to a micro-targeted playbook: what that customer said, plus peers in their segment.

What you get

SALES PLAYBOOK: checkout flow
Targeted at Adventure Works

THE PAIN, IN THEIR WORDS
  Saved cards fail at renewal and nobody finds out until the
  customer complains.
    "We learned from the guest, not from the system."
      Northwind Trading

COST OF INACTION
  What they do instead: a person reconciles failed payments by
  hand every Monday morning. That is the price of the status quo,
  and it is easier to argue with than a projected return.

WHAT ADVENTURE WORKS SAID
  "We've had three chargebacks this quarter we didn't see coming."
    On their last call, unprompted.

SOCIAL PROOF FROM THEIR SEGMENT
  Contoso Retail, same segment, same problem, now closed-won:
    "The retry logic paid for itself in one month."

EXPECT THIS OBJECTION
  They raised pricing twice in the last month. Lead with the
  Monday-morning reconciliation, not the feature list.

Cost of inaction, not projected return

A forecast is something the buyer has to trust. “Someone spends Monday morning reconciling failed payments by hand” is their present, and verifiable. Built from the workarounds customers described.

Proof from their segment

A reference that looks like the prospect outweighs a more impressive one that does not. Naming a company matches proof points to their segment first.

Three, not ten

Three pain points, three objections, three proof points. Chosen by frequency and severity together.

Naming a company adds

What that customer said themselves.
Which competitor they mentioned.
The objections to expect from them.

MCP

Claude Code Skills

For product

For engineering

For sales

For marketing

For leadership

For customer success

For everyone

Arguments

What you get

Cost of inaction, not projected return

Proof from their segment

Three, not ten

Naming a company adds

​Arguments

​What you get

​Cost of inaction, not projected return

​Proof from their segment

​Three, not ten

​Naming a company adds

Arguments

What you get

Cost of inaction, not projected return

Proof from their segment

Three, not ten

Naming a company adds