kazanjy-founding-sales ยท diff
git:20261002.46ac0a1 to git:20261002.d5668a9
23 added, 100 removed. Audit A to A.
---
name: kazanjy-founding-sales
- description: "Build and diagnose a founder-led B2B sales motion using Peter Kazanjy's Founding Sales method. Use for early customer acquisition, sales narratives, outreach, demos, and deciding when to hire and train the first sellers."
+ description: "Build and diagnose founder-led B2B sales using Peter Kazanjy's public method. Use for early customer acquisition, sales narratives, outreach, discovery, demos, and transferring a proven motion to first sellers."
---
# Founding Sales for Founder-Led B2B Selling
Based on Peter Kazanjy's public method. Not affiliated with or endorsed by Peter Kazanjy.
## When to use
- Use this skill when a founder or first seller needs to acquire early B2B customers, repair a weak sales motion, produce sales materials, or transfer a working motion to professional sellers. Treat sales development as an experimental process that the founder first learns, documents, and then teaches. [S1]
-
- For a narrow request, execute the relevant steps below while checking the preceding stage's evidence. For a request to hire a salesperson before anyone has reliably sold the product, first diagnose what has actually been proven and produce the missing founder experiments. Hiring is a scaling mechanism only after a motion exists to transfer. [S2]
-
- ## Operational procedure
-
- ### 1. Locate the next unproven stage
-
- Collect the product, target organization and buyer, existing customers, price, sales history, implementation results, and available sales records. Classify the venture by demonstrated evidence rather than fundraising stage or enthusiasm. Use this sequence as the diagnostic ladder. [S2]
-
- - Problem discovery: prospects describe a real pain and current workarounds; the team has translated that learning into an initial product. [S2]
- - Value creation: implemented customers show improvement in the intended business measures. Product usage alone does not establish this. [S2]
- - Value exchange: customers pay and subsequently receive the promised value. Free pilots cannot prove willingness to pay. [S2]
- - Repeatable exchange: the founder repeatedly sells to suitable customers outside the initial beta group, with documented execution and successful onboarding. [S2]
- - Transfer: other sellers can run the motion efficiently, close suitable customers, and get them to success. [S2]
-
- State the earliest missing proof and design the current task to produce it. Do not substitute a larger pipeline, a polished deck, or an executive hire for an unproven stage. The founder remains responsible for discovering the motion and initially managing its transfer. [S1] [S2]
-
- ### 2. Define the pain-bearing customer
-
- Write the ideal customer profile as observable business conditions that create the problem, plus the role responsible for solving it and the role controlling relevant budget. A broad industry label is insufficient. Target the person close to the pain rather than automatically approaching the CEO. [S3]
-
- For each proposed account, record the evidence of pain, current solution, responsible contact, and reason the account qualifies. Existing expenditure on competing tools or manual work can be positive evidence of demand. Where no solution exists, the narrative must establish why the neglected problem deserves attention and money. [S3]
-
- Separate fit from timing. Identify a real event that makes the pain urgent, such as a newly expanded team exposing management gaps. If creating a new category, identify the hidden budget or opportunity loss and build a business case the champion can carry to the economic buyer. [S9]
-
- ### 3. Create the master commercial narrative
-
- Write one central narrative before producing individual messages. Follow the progression from problem to solution to supporting specifics. Cover who suffers, what the pain costs, how existing alternatives fail, what changed to permit a better approach, how the solution works, and evidence of superiority. [S3]
-
- Translate claims into customer operating measures. Distinguish measurable savings, incremental revenue, and softer qualitative benefits; label estimates as estimates. Explain the mechanics behind headline results and retain the calculations. If a prospect rejects the problem definition, address that disagreement or end the pitch instead of continuing through irrelevant product claims. [S3]
-
- ### 4. Ship minimum viable sales materials
-
- Turn the narrative into a compact deck with coverage of the problem, affected buyer, cost, alternatives, enabling change, solution, proof, and price. Keep slides modular so the argument can become more detailed as customer conversations reveal gaps. Prioritize rapid iteration while preserving credibility. [S4]
-
- Move uncommon integration details and competitor comparisons into an appendix. When the same question appears a second time, create a reusable answer slide. Maintain a concise live presentation and a separate sendable version that reflects what was actually discussed. A generic fundraising story or unexplained product tour does not supply this commercial argument. [S4] [S5]
-
- ### 5. Build appointment-setting assets
-
- Derive a plainspoken outreach email and a short phone outline from the same narrative. In the email, connect an observed qualification fact to the recipient's specific pain, describe the relevant improvement, supply credible proof, and request a synchronous conversation. The immediate goal is an appointment. [S5]
-
- Use a relevant subject line and customer-specific facts rather than ornamental marketing design. Where useful, include a screenshot or linked demonstration that supports the claim. Store reusable templates centrally and fork variants when distinct customer subgroups require different arguments. Do not treat highly targeted prospecting as a general product announcement. [S5]
-
- ### 6. Run discovery and demonstrate a workflow
-
- Before the call, inspect the organization and attendee, identify the likely fit, and decide what progress the meeting should achieve. Use specific, researched rapport. During discovery, investigate the current process and its consequences rather than wasting the conversation collecting facts already available publicly. [S9]
-
- Use discovery to reveal the prospect's pain to the prospect as well as to learn about it. Follow answers into concrete examples of failures and consequences. Then frame how the solution addresses the acknowledged problem before moving into product screens. If time is short, earn a specific next meeting rather than rushing a disconnected demo. [S9]
-
- Write a demo outline around the customer's natural workflow. Start with a compelling, readily understood use case and proceed through the work in its usual order. Customize examples to the prospect's actual needs, pause for discussion, and tie demonstrated capabilities back to the commercial argument. Do not rely on improvisation or exhaustive feature coverage. [S5]
-
- ### 7. Ask directly and preserve the evidence
-
- Explicitly ask whether the prospect has the problem, wants to solve it, and is prepared to spend money. Ask for the sale when appropriate rather than hoping interest turns into a purchase. Treat a poor fit or stalled opportunity as a reason to move on to other qualified prospects rather than hoarding every possible deal. [S6]
-
- Record qualification details, opportunity size, objections, and next actions in the CRM. Make temporary conversational knowledge persistent so future follow-up and diagnosis have evidence. Keep customer interactions moving instead of endlessly perfecting collateral or communications; templatize recurring work to support high activity without sacrificing relevance. [S6]
-
- For the first paid engagements, carry the agreement through procurement and implementation. Instrument the promised business result, review it with the customer, and count successful value delivery alongside payment. Selling many customers who never achieve the intended outcome is a failed proof of repeatability. [S2]
-
- ### 8. Diagnose the motion before scaling it
-
- Review activity volume and conversion between actual steps, including meetings and subsequent commitments. With sparse data, retain qualitative responses as well as progression counts. Repeated engaged discussions that produce a next meeting are stronger evidence than pleasant calls that go nowhere; inspect discovery and narrative when progression is weak. [S9]
-
- Use the founder presentation's examples of 30 to 50 or more non-beta prospects and roughly one to two dozen successful customers as reference ranges, not universal numerical gates. The operative check is healthy sales performance plus a repeatable, documented motion that another seller can test. Avoid hiring a sales leader to manufacture this proof. [S2]
-
- ### 9. Transfer the motion through hiring and training
-
- Once the transfer stage is justified, define the execution the role must reproduce. Assess resourcefulness, coachability, persistence, precision, and demonstrated learning. Prestigious employers or schools are insufficient substitutes for evidence, and selling established products does not automatically prepare someone to sell an unfamiliar solution. [S7]
-
- Use a realistic hiring exercise covering account research, discovery, presentation, demonstration, closing request, and follow-up. For a presentation role, evaluate the whole simulated customer interaction, including the invitation and proposal. Avoid theatrical exercises involving arbitrary objects; observe whether the candidate can execute the relevant work. [S7]
-
- Build onboarding around the buyer's world, narrative, product, tools, and sales process. Rehearse presentation sections with feedback, pair trainees for realistic practice, and let them participate in the work surrounding experienced sellers' calls. Prepare accounts and tools rather than assuming new hires will configure everything correctly. [S8]
-
- Start live selling with well-qualified opportunities and available support. Do not use unsuitable prospects as disposable practice. Review calls and leading performance measures, and reduce supervision as execution improves. Prove that a small number of sellers succeeds before adding many; the founder must make time for coaching rather than personally closing every opportunity. [S8] [S2]
-
- ## Finished output
-
- Deliver a sales working packet scaled to the requested task, with these elements or explicit reasons they are premature. Keep its claims traceable to observed customer and sales evidence. [S2] [S6]
+ Use this skill when a founder or first seller needs to acquire early B2B customers, diagnose stalled selling, prepare customer-facing materials, or transfer a working sales motion to other people. Its central deliverable is a sales working packet: an evidence-based stage assessment, the assets needed for the next experiment, and a review plan. Scale the packet to the user's request rather than producing every possible asset. [S1] [S2]
- - Stage assessment, missing proof, and next experiment with an observable exit condition. [S2]
- - Customer profile, prospect qualification evidence, and master narrative with business measures and supporting calculations. [S3]
- - Relevant deck outline, outreach drafts, discovery branches, workflow demo, objection answers, and closing request. [S4] [S5] [S6]
- - Opportunity records and review measures covering progress, payment, and delivered value. [S2] [S6] [S9]
- - If transfer is justified, a hiring exercise, onboarding sequence, and criteria for independent execution. [S7] [S8]
+ Treat selling as a process the founder discovers, tests, documents, and teaches. A fundraise, enthusiastic pilot, or experienced sales hire does not establish a transferable motion. Start with the earliest missing proof, including delivered customer value, and make that proof the purpose of the work. Read the relevant sections of the method before drafting. [S2]
- ## Worked example: invented illustration
+ This package uses public presentations, an interview, and a website overview. It excludes book text. References distinguish source-backed guidance from package conventions for making the work reviewable. Citations identify the method's basis; customer claims still need customer evidence. See [references/sources.md](references/sources.md).
- An invented startup, DispatchLoop, automates exception handling for regional delivery operators. Three free pilot customers report fewer missed deliveries, but nobody has paid. The agent identifies value exchange as the next missing proof and recommends founder selling rather than an immediate sales executive hire. [S2]
+ ## Procedure
- The target profile becomes operators with dispatch staff manually coordinating repeated delivery exceptions. The narrative compares the current calls-and-spreadsheets process with automatic exception routing. An illustrative calculation of 40 dispatcher hours saved monthly at $30 per hour implies $1,200 in potential labor capacity; it remains a hypothesis until measured with customers. [S3]
+ 1. **Bound the assignment.** Identify the requested asset, product, target buyer, available evidence, price, and constraints. Record missing inputs as questions or assumptions. Use the scope and evidence fields in [templates/output-template.md](templates/output-template.md); do not invent traction to make a draft persuasive.
- The agent drafts an outreach message tied to observed delivery expansion, then prepares discovery about recent exception failures and a demo following one exception from detection through resolution. The founder asks for a paid engagement and follows through on implementation. The review compares meetings, commitments, payments, and measured customer results before considering a first seller trained on the documented motion. [S5] [S6] [S2]
+ 2. **Find the earliest unproven stage.** Separate problem discovery, demonstrated value, payment, repeatable sales, and transfer. Include implementation results when judging progress. Choose one next proof and an observable exit condition using the maturity rules in [references/method.md](references/method.md#1-diagnose-maturity). [S2]
- ## Sources
+ 3. **Define a narrow customer profile.** Specify organizational conditions, pain indicators, and relevant people. Separate the user, champion, and budget authority. Mark inferred fit and timing as unverified. Apply [references/method.md](references/method.md#2-define-fit-and-timing) before selecting prospects. [S3]
- All sources below were fetched directly with curl. The articles and transcript are publicly available; no gated book chapters were used.
+ 4. **Construct a commercial narrative.** Connect the current workflow, its consequences, inadequate alternatives, the proposed change, and supporting evidence. Include the buyer's personal stakes when relevant. Label estimated economics and retain their inputs using [references/method.md](references/method.md#3-build-the-value-argument). [S3]
- [S1] Founding Sales: The Founder Led Sales and Startup Sales Handbook. https://www.foundingsales.com/
+ 5. **Prepare only the necessary assets.** Derive an outreach draft, presentation outline, or call plan from that argument. Keep each asset directed toward its next commitment. Follow [templates/output-template.md](templates/output-template.md) and compare the transformation in [examples/worked-examples.md](examples/worked-examples.md).
- [S2] Peter Kazanjy, Founder-Led Sales: A design pattern for iterative startup GTM development and execution, public presentation. https://docs.google.com/presentation/d/1t-2gOEhYSXEUow67j7_n3CbgoNPwpFVp4eaolEn3H24/export/txt
+ 6. **Plan discovery before demonstration.** Research available facts, set a meeting objective, and prepare branches about current practice, specific failures, consequences, and urgency. Let answers change the conversation. Use [references/method.md](references/method.md#4-run-the-conversation), especially its guidance for prospects who do not acknowledge pain. [S3]
- [S3] To Build An Amazing Sales Team, Start Here First. https://review.firstround.com/to-build-an-amazing-sales-team-start-here-first/
+ 7. **Show the relevant solution and ask for progress.** Connect demonstrated capabilities to acknowledged problems. Request a specific next meeting, evaluation, or purchase suited to the stage. Capture the buyer's response using the conversation and commitment fields in [templates/output-template.md](templates/output-template.md). [S2] [S3]
- [S4] Building Your Best Sales Deck Starts Here. https://review.firstround.com/building-your-best-sales-deck-starts-here/
+ 8. **Carry the agreement into customer success.** Record procurement steps, implementation ownership, a baseline, and a business outcome to validate with the customer. Payment and usage answer different questions. Consult [references/method.md](references/method.md#5-record-and-diagnose-results) before counting a deal as proof. [S2]
- [S5] Here are the Scripts for Sales Success: Emails, Calls and Demos That Close Deals. https://review.firstround.com/here-are-the-scripts-for-sales-success-emails-calls-and-demos-that-close-deals/
+ 9. **Diagnose the bottleneck and revise.** Review activity, stage progression, objections, and delivered outcomes together. Distinguish poor fit, weak explanation, and product or implementation failure. Choose a focused next test using [references/method.md](references/method.md#5-record-and-diagnose-results), retaining uncertainty when evidence is sparse. [S3]
- [S6] 10 Ways You Need to Change How You Think and Talk to Succeed at Sales. https://review.firstround.com/10-ways-you-need-to-change-how-you-think-and-talk-to-succeed-at-sales/
+ 10. **Transfer only a demonstrated motion.** If justified, define seller stage fit, training, supervision, and independent execution criteria. If premature, explain the missing proof and prepare the founder's next experiment. Apply [references/method.md](references/method.md#6-transfer-and-scale) rather than treating hiring as a cure for discovery problems. [S2] [S3]
- [S7] The Anatomy of the Perfect Sales Hiring Process. https://review.firstround.com/the-anatomy-of-the-perfect-sales-hiring-process/
+ 11. **Review and deliver.** Run [checklists/review-checklist.md](checklists/review-checklist.md), resolve failures, and provide the requested packet with assumptions, evidence gaps, owners, and a next review date. Mark unused sections as premature or outside scope; preserve useful drafts without implying they have been tested.
- [S8] You're Losing Hundreds of Thousands of Dollars Because of Poor Sales Onboarding. https://review.firstround.com/youre-losing-hundreds-of-thousands-of-dollars-because-of-poor-sales-onboarding/
+ ## Files in this skill
- [S9] Founders: Here's how to get your sales pitch in ship-shape, Peter Kazanjy, In Depth podcast and public transcript. https://review.firstround.com/podcast/founders-heres-how-to-get-your-sales-pitch-in-ship-shape-peter-kazanjy/
+ - [SKILL.md](SKILL.md): Entry point, use cases, and the agent's execution loop.
+ - [references/method.md](references/method.md): Principles, stage gates, decision rules, edge cases, and explicit warnings.
+ - [references/sources.md](references/sources.md): Numbered registry of fetched public sources and their contributions.
+ - [examples/worked-examples.md](examples/worked-examples.md): Invented before-and-after illustrations of early selling and transfer.
+ - [templates/output-template.md](templates/output-template.md): Fill-in sales working packet with field guidance.
+ - [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail review criteria, failure modes, and repairs.