samarv/shanon

repeatable-sales-motion-while-loop

A framework for founders and product managers to build a scalable B2B sales process. Use this when you are launching a new B2B product, when your current sales process feels inconsistent, or when you are preparing to hire your first full-time salesperson.

First seen Jun 24, 2026

Installation

$ npx skills add samarv/shanon --skill repeatable-sales-motion-while-loop

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from samarv/shanon · top by installs.

npx skills add samarv/shanon

Browse all from samarv/shanon

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 31
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,193 B
  • docs SUMMARY.md 297 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Repeatable Sales Motion While Loop

In B2B startups, the "While Loop" is the iterative process of transforming founder-led expertise into a repeatable system that a non-founder can execute. Startups are a race to see if innovation can get to distribution before distribution gets to innovation. This framework ensures you don't "error out" when moving from founder selling to a scaled sales team.

Phase 1: Establish Your "Local" Environment

Before hiring anyone, you must prove the sales motion runs on your "local machine" (the founder's brain).

  1. Run 50-100 At-Bats: Do not rely on "revenue trades" with friends or accelerator buddies. Engage arm’s-length parties who have no reason to be nice to you.
  2. Target a 15-25% Win Rate: If you are closing 1 out of every 4 or 5 discovery meetings with cold prospects, your "code" is stable enough to document.
  3. Practice Turbo Rapport: Use every daily interaction (baristas, flight attendants) to practice breaking down "shields up" behavior. In a sales call, you have 90 seconds to make a prospect trust you enough to be honest about their pain.

Phase 2: Update the "Source Code"

Treat your sales collateral (slides, scripts, templates) like software that requires constant version updates based on "bugs" found in meetings.

  1. Identify Objections as Bugs: Every time a prospect asks a question you can't answer or expresses a concern that stalls the deal, treat it as a system error.
  2. Patch the Collateral:

Visual Guardrails: Create a specific slide to handle the objection visually. Talk Tracks: Write a specific script or "objection handle" for that scenario. Discovery Questions: Add a question to your early-stage script that uncovers that specific pain point before* the objection even arises.

  1. Continuous Deployment: Use the updated slide/script in your very next meeting. Repeat until the objection no longer stalls the deal.

Phase 3: Move to the "Sales Cloud" (Hiring)

Once the loop runs reliably for you, "abstract" the logic into the brains of your first hires.

  1. Hire "Pioneer" Sellers, Not VPs: Do not hire a VP of Sales who is a "manager of managers." Hire "gritty" individual contributors who have sold similar products at similar price points at an early stage.
  2. Hire in Pairs: Hire two reps simultaneously. If one fails and one succeeds, you have a performance issue. If both fail, you have a "source code" (product-market fit) issue.
  3. Monitor Leading Indicators (The "Second Date" Heuristic): Do not wait 6 months for closed deals to evaluate success. Monitor these conversion metrics weekly:

Discovery to Scoping: Are they getting "second dates"? Stage Conversions: Are they moving prospects through the pipeline at the same rate you did? * Activity Volume: Are they maintaining the necessary calendar density of new meetings?

Examples

Example 1: The Design Tool Startup

  • Context: A founder is selling a new collaborative design tool to mid-market tech companies.
  • Application: After 20 meetings, the founder notices every prospect asks, "How does this integrate with Jira?" Instead of just answering "It's coming soon," the founder creates a slide showing the integration roadmap and a screenshot of the prototype.
  • Output: In the next 10 meetings, the integration question is handled in 2 minutes rather than 15, and the conversion to "Trial" stage increases from 20% to 40%.

Example 2: The Analytics Startup

  • Context: A PM-turned-founder is selling a data-driven management platform.
  • Application: The founder documents the "While Loop" by creating a Notion page with:

1. A 5-step discovery script. 2. A 10-slide deck. 3. Three "Golden Questions" that always trigger a "Wow" moment.

  • Output: The founder hires two AEs and provides this "Source Code." Within 30 days, both AEs are maintaining a 20% "Second Date" conversion rate, proving the motion is repeatable.

Common Pitfalls

  • Outsourcing the First Sale: Hiring a "sales person" to "figure it out" for you. If you can't sell it, they can't sell it. You lose the feedback loop necessary to fix the product.
  • Mistaking Lead Gen for Business: Relying on low-cost self-serve signups (PLG) without realizing that large contracts require human intervention to navigate internal organizational hurdles.
  • Hiring "Professionally Rich" VPs: Hiring someone from a giant like Google or Salesforce who expects a massive support staff and hasn't actually "carried a bag" or built a deck from scratch in years.
  • Asynchronous Distance: Hiring junior reps for a remote-only environment too early. Junior reps need "shoulder-to-shoulder" coaching and the ability to overhear successful calls to learn the "vibe" of the sale.