kazanjy-founding-sales
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.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- kazanjy-founding-sales
- 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.
02 资源文件 7
- 参考文档checklists/review-checklist.md6.7 KB
- 参考文档DERIVATION.json2.0 KB
- 参考文档examples/worked-examples.md9.1 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md16.0 KB
- 参考文档references/sources.md2.0 KB
- 参考文档templates/output-template.md8.9 KB
03 SKILL.md 正文
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, 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]
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]
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.
Procedure
-
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; do not invent traction to make a draft persuasive.
-
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. [S2]
-
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 before selecting prospects. [S3]
-
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. [S3]
-
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 and compare the transformation in examples/worked-examples.md.
-
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, especially its guidance for prospects who do not acknowledge pain. [S3]
-
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. [S2] [S3]
-
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 before counting a deal as proof. [S2]
-
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, retaining uncertainty when evidence is sparse. [S3]
-
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 rather than treating hiring as a cure for discovery problems. [S2] [S3]
-
Review and deliver. Run 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.
Files in this skill
- SKILL.md: Entry point, use cases, and the agent's execution loop.
- references/method.md: Principles, stage gates, decision rules, edge cases, and explicit warnings.
- references/sources.md: Numbered registry of fetched public sources and their contributions.
- examples/worked-examples.md: Invented before-and-after illustrations of early selling and transfer.
- templates/output-template.md: Fill-in sales working packet with field guidance.
- checklists/review-checklist.md: Pass/fail review criteria, failure modes, and repairs.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.