Sell the Alpha, Not the Feature

Based on Jen Abel's public method. Not affiliated with or endorsed by Jen Abel.

When to use

Use this skill to prepare or improve an enterprise sales opportunity for a named product and buyer. It fits founders finding their first commercial entry point, teams moving from small business customers into enterprise, and sellers growing an established enterprise motion. Abel's later interview focuses on approximately $1 million to $10 million ARR; her earlier work supplies the discovery practices needed before that stage. [S2] [S3]

The deliverable is an account-specific sales brief: buyer advantage, evidence of priority, outreach, discovery and demonstration plan, engagement choice, commercial frame, procurement path, and next decision. Adapt the emphasis to the assignment. A stalled deal needs diagnosis; an untouched account needs a hypothesis and discovery agenda. Include hiring analysis only when handoff or scaling is in scope.

These steps and worksheets synthesize the public method. They are not an official Abel framework. Treat account facts as supplied evidence, proposed advantages as hypotheses, and illustrative numbers as assumptions. Never manufacture research, buyer commitments, savings, product capabilities, or contract acceptance. Read references/sources.md when verifying attribution; public host summaries and transcript reproductions have different evidentiary weight from Abel's own articles.

Procedure

1. Frame the assignment. Record product maturity, revenue motion, existing wins, account, buyer role, intended output, and current obstacle. Open templates/output-template.md and populate the context fields. Mark missing facts as unknown and continue with explicitly labeled assumptions where useful.
2. Choose the sales motion. Use references/method.md to distinguish a low-touch business from enterprise selling. Resolve a mid-market label into actual buying behavior. Treat a new enterprise segment as new discovery even when the company already has small business revenue. [S2]
3. Narrow the hypothesis and account. Define one customer type, accountable role, and contained unmet need using references/method.md. Consider category leaders on evidence of willingness to experiment. Map executive sponsorship and implementation responsibility separately. [S2] [S3]
4. Draft the buyer's alpha. State their present capability, the future advantage, and the distinctive mechanism that bridges them. Use references/method.md and examples/worked-examples.md. Make the advantage meaningful enough for a champion to defend internally and identify what must be validated. [S1] [S2]
5. Earn a relevant conversation. Draft three or four outreach sentences around role relevance, a useful insight, and a small invitation. Follow references/method.md. Use a verified observation or an openly stated hypothesis; do not disguise conjecture as proprietary knowledge. [S6]
6. Discover priority before demonstrating. Apply references/method.md: investigate prior attempts, measurement, ownership, and willingness to act. Explain contradictions and revise the hypothesis. If a demo follows, show only the capabilities connected to the buyer's confirmed concerns. [S3] [S6]
7. Decide whether to advance. Seek a specific next conversation during the call, record the unresolved question, and select advance, reframe, nurture, or stop. Use the evidence fields in templates/output-template.md. Politeness without commitment is a qualification warning, not automatic disqualification. [S2] [S6]
8. Choose the engagement. Consult references/method.md to distinguish collaborative learning from evaluation of a built product. Specify limitations, participation, boundaries, and conversion criteria. Keep design partners within a consistent customer profile. [S5]
9. Co-author the commercial frame. Use references/method.md to connect price, access, scope, value, and expansion. Explain introductory terms and future expectations. Evaluate a contained service entry when appropriate, with an explicit product destination. [S2]
10. Build the buying path. Use references/method.md to map procurement, Finance, IT, Legal, approval timing, champion participation, and financial evidence. Requalify disengaged sponsorship or an unexplained RFP. Flag legal interpretation for counsel. [S8]
11. Assess handoff when relevant. Apply references/method.md to test whether a non-founder can generate and close opportunities. Identify the learning still held by the founder before recommending additional sales leadership. [S7]
12. Review and deliver. Complete checklists/review-checklist.md, revise failed items, and deliver the filled brief from templates/output-template.md. Include a clear next decision, owner, evidence required, and target date. These action fields are packaging conventions, not claims about Abel's published process.

Files in this skill

• SKILL.md: Entry point, activation guidance, and the agent's main loop.
• references/method.md: Detailed principles, decision rules, edge cases, and attributed warnings.
• references/sources.md: Eight fetched public sources, provenance, and citation key.
• examples/worked-examples.md: Two invented illustrations with weak drafts, revised briefs, and rule notes.
• templates/output-template.md: Fill-in sales brief with guidance for every field.
• checklists/review-checklist.md: Pass/fail review criteria and failure-mode repairs.