abel-sell-the-alpha git:20261002.46ac0a1A

Immutable. This exact content never changes and is served at /api/v1/blob/872ae4adf49c86ef.

---
name: abel-sell-the-alpha
description: "Build an enterprise sales plan around the buyer's unique advantage using Jen Abel's public method. Use for founder-led discovery, executive outreach, design partnerships, deal framing, pricing, procurement, and the transition from first customers to repeatable enterprise sales."
---
# 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 when a founder or enterprise seller needs to frame an opportunity, qualify an account, design an initial engagement, or diagnose a stalled deal. Its central setting is enterprise growth from roughly $1 million to $10 million ARR, supported by earlier customer discovery practices. Apply it to a named product and buyer, rather than producing a generic sales checklist. [S1]

The procedure below operationalizes Abel's public teachings. Its worksheets and output structure are a synthesis, not a claim that she publishes this exact sequence. Distinguish discovery of a real need from the executive sales narrative: her early discovery work tests specific problems, while her enterprise framing sells the future advantage those insights enable. [S2] [S3]

## Operational procedure

### 1. Decide which sales game this task requires

Record the product, current enterprise revenue, existing customers, likely contract value, buyer role, and buying process. Classify the motion as marketing-led small business or sales-led enterprise. Resolve a mid-market label into one of those motions before choosing pricing or sales talent. [S2]

If the company has established small business revenue but no enterprise wins, treat enterprise as a fresh discovery exercise. Prior success does not establish enterprise repeatability; the value proposition, risk tolerance, and deal structure change. [S2]

Keep the founder involved when the offer and target market are still unproven. Their authority to interpret market feedback and change the vision cannot be delegated to a salesperson who is simply told to sell the existing product. [S3]

### 2. Select a narrow entry point and an ambitious account

Write a hypothesis naming one customer type, one accountable role, and one unmet need. When the product already exists, identify its plausible use cases, then test for a specific commercial entry point rather than pitching everything it can do. Customer discovery should align the founder's vision with market reality. [S3]

Include category leaders in the account shortlist. Abel sees their need to preserve leadership as a reason to experiment; a successful relationship also supplies influential references. Check readiness for the proposed experiment rather than rejecting a large logo on assumed slowness. [S2]

For each account, identify an executive who can defend the opportunity and the people who would implement it. If a deal stalls in procurement, examine whether the buyer has sufficient seniority and commitment before blaming paperwork. [S2]

### 3. Define the alpha before describing the product

Write three sentences covering the buyer's current position, the future capability available to them, and the unusual information, data, access, or way of working that creates the gap. Describe what the leader and organization become able to accomplish, with the product as the mechanism. [S1]

Replace unsupported superiority claims with a different way of seeing the situation. Explain the insight that the existing approach misses and why it matters to this buyer. A claim that a tool is faster or cheaper rarely gives an unknown startup a defensible position against an already trusted solution. [S4]

Check whether the narrative gives the champion a reason to spend scarce internal credibility. If the pitch centers on product attributes, rewrite it around the buyer's new capability and the argument they could take to colleagues. Curiosity about a new perspective is more useful than forcing them to defend their current choice. [S4]

### 4. Earn the meeting with a useful insight

Draft a short outreach message with relevance to the recipient's role, a counterintuitive observation, and an invitation to learn more. Keep it within three or four sentences. The message should earn a conversation through a distinct insight rather than explain the entire solution. [S6]

Research likely buyers manually when shared prospect databases would put the seller in the same crowded channel as everyone else. Find a relevant route to the person whose work the insight concerns; tool volume alone is not evidence of an effective enterprise approach. [S1]

### 5. Run discovery before demonstration

Turn the founder's hypothesis into focused questions about the buyer's experience. Ask about previous attempts, current measurement of the issue, and the person accountable for it. These are Abel's indicators of priority; investigate a claimed priority without corresponding investment rather than accepting enthusiasm as demand. [S3]

Avoid broad questions about whatever happens to worry the buyer today. They generate inconsistent answers outside the hypothesis. Ask why a response matters, including why the buyer finds the idea interesting, and record what would change the original hypothesis. [S3]

Do not consume the first call with a product tour. The founder needs new information about the market, and the buyer needs a reason to continue. Capture the buyer's language and test whether the need is sufficiently specific to support another conversation. [S6]

Try to schedule that next conversation during the call. An unwillingness to commit is a qualification signal. Record what remains uncertain instead of treating a polite promise to email later as deal momentum. [S6]

### 6. Choose a design partnership or a product evaluation

Distinguish the two engagements. A design partnership involves learning and building through uncertainty; a proof of concept evaluates a product already built. Select partners who want the founder's expertise, can explain past attempts, and are willing to participate in messy experimentation. [S5]

Keep design partners within a consistent customer profile and contained problem. Partners across unrelated markets create conflicting demands and can turn the company into a collection of custom services. Judge each proposed change against the broader market the founder intends to serve. [S5]

Explain today's limitations and the intended destination before asking for commitment. Seek payment and a contract early, but do not count a design partner as validated recurring demand. The conversion to a regular paying customer is difficult precisely because they experienced the unfinished product. [S5]

### 7. Establish the commercial frame early

Test an initial enterprise contract around $75,000 to $150,000 against the value and scope. Treat that range as Abel's contextual guidance, not a universal tariff. A $10,000 annual land can anchor negotiations and make a later enterprise expansion difficult to defend. [S2]

For an early discounted engagement, explain the intended future price and expansion path upfront. Separate an introductory arrangement from the full commercial destination. Do not assume the buyer will accept a large price jump merely because the product improves. [S2]

Shape the offer with the champion rather than defaulting to a price cut. Explore bounded implementation work, access to expertise, or changes in term and scope. Explain how these give the buyer additional value and an internally defensible agreement; enterprise deal crafting extends beyond the software itself. [S1]

When an enterprise understands how to buy services but not the new technology, consider a contained service engagement that leads toward product adoption. Make the transition explicit so the service becomes an entry point rather than an indefinite substitute for a scalable offer. [S6]

### 8. Make procurement part of the sale

Prepare a procurement explanation showing what the buyer is purchasing, the experiment it supports, the engagement boundaries, and the evidence of value. Educate procurement so it can coordinate Finance, IT, Legal, and the business unit around the actual offer. [S8]

Ask early about IT review timing and involve the champion in initial procurement calls. Project-manage the buyer and procurement together; neither should be expected to resolve the entire process alone. Treat fading champion responsiveness as a warning about commitment. [S8]

Build the financial argument with the buyer. Distinguish hard savings, such as replacing an external contract, from general claims about saved time. Identify dependencies, payment approval, and delivery obligations before doing substantial work; route enterprise contract interpretation to qualified counsel. [S8]

Investigate an RFP that arrives without meaningful collaboration, especially if the buyer rushes evaluation and shows little patience. Abel warns that this can mean the startup is only satisfying a required vendor comparison. Requalify before committing significant effort. [S8]

### 9. Transfer judgment before scaling headcount

When hiring becomes part of the task, describe the repeatable entry point and the knowledge a seller must carry. Seek someone who can build trust, understand the buyer's business, and convey the founder's vision, rather than assuming a large-company sales title predicts success in an early enterprise motion. [S2]

Keep a founder-managed phase between founder-led selling and a sales executive hired to scale. Verify that a non-founder can generate and close opportunities with comparable success. More logos and more headcount do not establish repeatability if every meaningful sale still depends on the founder. [S7]

## Finished output and checks

Deliver an account-specific sales brief containing the following artifacts. Separate observed buyer evidence from hypotheses so that the user can see which decisions are ready and which require discovery. [S3]

- A motion decision, narrow customer hypothesis, account rationale, and buyer map identifying executive support and implementation responsibility. [S2] [S3]
- A buyer-centered alpha narrative and concise outreach draft showing the distinctive insight that earns attention. [S1] [S4] [S6]
- A discovery agenda, evidence of priority, and decision about the next conversation, design partnership, or evaluation. [S3] [S5] [S6]
- An initial commercial proposal with scope, price rationale, limitations, and future pricing expectations. [S1] [S2] [S5]
- A procurement path with champion participation, IT timing, financial evidence, and outstanding questions, plus a handoff assessment when hiring is in scope. [S7] [S8]

Before delivery, flag feature-led messaging, compliments mistaken for demand, unrelated design partners, undefined introductory discounts, absent senior sponsorship, and premature delegation. Explain the correction and the evidence needed for each flag. [S3] [S4] [S5] [S7] [S8]

## Worked example

Illustration only. A fictional startup helps a national grocery chain detect supplier disruption from unusual upstream signals. The initial pitch lists dashboards and alerts. The revised alpha hypothesis is that a merchandising leader can secure alternatives before competitors recognize a shortage, protecting availability during a seasonal peak. This is an opportunity narrative requiring validation, not a promised result. [S1] [S4]

Discovery asks how shortages were handled previously, what losses are measured, and who owns mitigation. If those answers establish priority, the founder proposes a contained paid engagement in one category, with stated data limitations and a clearly discussed future commercial price. Procurement receives the buyer's financial case and IT review requirements. A partner requesting unrelated workforce software would be declined to preserve the chosen market and vision. [S3] [S5] [S8]

## Sources

All listed pages were fetched with curl. Only publicly accessible material was used. S2 is a public transcript of the freely distributed podcast; S6 is the host's public episode notes. No subscriber-only commentary or book text was used.

[S1] Lenny Rachitsky's public LinkedIn post introducing Sell the Alpha, Not the Feature. https://www.linkedin.com/posts/lennyrachitsky_sell-the-alpha-not-the-feature-the-enterprise-activity-7393315917297803264-tFYn

[S2] Sell the alpha, not the feature: The enterprise sales playbook for $1M to $10M ARR, Jen Abel, public podcast transcript, November 9, 2025. https://podscripts.co/podcasts/lennys-podcast-product-career-growth/sell-the-alpha-not-the-feature-the-enterprise-sales-playbook-for-1m-to-10m-arr-jen-abel

[S3] SaaS Deep Dives: Early Stage Sales, Product Demos & Right to Sell with Jen Abel, Prime Venture Partners, March 3, 2023. https://www.primevp.in/content/podcast/saas-deep-dives-early-stage-sales-product-demos-right-sell-jen-abel-co-founder-jjellyfish

[S4] We're different is Far Superior to We're better in B2B Sales, Jen Abel, April 3, 2024. https://www.jjellyfish.com/content-library/articles/were-different-is-far-superior-to-were-better-in-b2b-sales

[S5] The Dark Side of Design Partners, Jen Abel, May 23, 2024. https://www.jjellyfish.com/content-library/articles/design-partners-are-far-messier-than-you-thinknbsp

[S6] The ultimate guide to founder-led sales, Jen Abel, public episode notes, November 24, 2024. https://www.lennysnewsletter.com/p/master-founder-led-sales-jen-abel

[S7] Why The Founder-Managed Sales Step is So Critical (and Often Skipped), Jen Abel, April 18, 2024. https://www.jjellyfish.com/content-library/articles/why-the-founder-managed-sales-step-is-so-critical-and-often-skipped

[S8] A Few Tips For Getting Through Procurement as an AI Startup, Jen Abel, June 17, 2024. https://www.jjellyfish.com/content-library/articles/10-tips-for-navigating-procurement-in-the-age-of-ai-hint-this-list-will-likely-evolve