Skip to content
RAY BEHARRY

Systems, Not Slides

Tools, playbooks & prompts

Simple, runnable and measurable. Pick one and start this week.

Playbooks

Eight playbooks, from two hours to a month.

  • 1 week

    Three-Intro Test

    Give sellers three intro variants (Trust / Speed / Control). Log usage and outcome in CRM. After one week, move the winner into all SDR emails and first-slide copy.

  • 48 hours

    Proof Sprint

    Audit every decision-stage asset. Attach a number, logo, or quote, or remove the claim. Publish the Proof Vault with ProofIDs. Rule: no ProofID, no publish.

  • 2 weeks

    14-Day Tune

    After launch Day 14, promote the top narrative to hero and paid. Cut spend on the bottom. Announce with one chart and three lines of rationale.

  • 72 hours

    Counter Kit

    When a competitor moves: Their Move → Our Angle → Proof → Landmine → three questions sellers can ask → three lines → compare block. Ship in 72 hours.

  • Half day

    Objection Lab Sprint

    Pull 25 stalled calls from Gong. Cluster the top eight objections. Write LPNS for each with a named proof. Publish a before/after reel.

  • 2 hours

    Skills Audit

    Score the team 1–5 on System / Story / Stewardship. Pick two gaps per person. Pair each with a project that proves it: a shipped artifact.

  • 1 week

    Taste Library

    Collect fifteen lines that moved deals. Attach ProofIDs. Publish a banned-phrases list (the Kill List). Success looks like fewer rewrites.

  • Monthly

    Red-Team Review

    Sixty minutes a month. Pick a surface, assign critic, counsel and owner, falsify claims, then fix or footnote. Target: zero preventable overclaims.

Prompt templates

Plain words. Clear rules. Results you can ship.

Copy any template into Claude or ChatGPT. Replace the bracketed fields with your own context.

  • 3-Line Brief

    Role: [Your role]
    Outcome: [Specific goal]
    Output: [Format + length]
  • LPNS on Demand

    Answer with LPNS:
    • Line (2 sentences, on voice)
    • Proof (add ProofID; if missing, '[PROOF NEEDED]')
    • Next Step (1 specific ask)
  • Critique → Rewrite

    Critique this copy against our Voice Card (tone, cadence, banned words).
    
    Return:
    1. Before/After comparison
    2. Two reasons the 'after' lands better
  • Force Schema

    Return exactly:
    1) Headline ≤12 words
    2) Subhead ≤30 words
    3) Compare block 60–70 words with one ProofID
  • Adversarial Test

    As a skeptical [PERSONA], list 5 objections this copy invites.
    
    For each:
    • Propose a tighter line, OR
    • Remove the claim entirely
  • Proof Scan

    Extract 3 candidate proofs from this text.
    
    For each:
    • 1-sentence proof
    • Source link
    • ICP/persona fit
    • Expiry date
    
    If unverifiable, label 'discard'.
  • Summarize → Decide

    Summarize these inputs in our voice.
    
    Then propose:
    • STOP: [one thing + reason]
    • START: [one thing + reason]
    • SCALE: [one thing + reason]
  • Delta Diff (CI)

    Diff these two pages (now vs. last month).
    
    What appeared?
    What disappeared?
    What tone shift?
    
    Give 5 implications and one Counter Kit angle.
  • Positioning Engine

    Generate 3 positioning statements:
    1. Awareness (emotional, tension-focused)
    2. Consideration (comparative, proof-forward)
    3. Decision (specific, ROI-anchored)
    
    Keep core message consistent; adjust tone per stage.
  • Safety Rail

    If asked for pricing, roadmap, or private data:
    → Reply "Insufficient data—ask owner"
    → Offer nearest public alternative
    
    Never fabricate. "I don't know" is acceptable.