$1M to $10M: The enterprise sales playbook with Jen Abel

Summary

Jen Abel’s central argument is that growing from $1M to $10M ARR through enterprise sales is a different game from selling to small businesses. It requires a distinct go-to-market approach, larger deal economics, executive-level relationships, and sellers who can communicate a founder’s vision—not simply run a standard sales process.

Playbooks and recommendations

• Choose a segment and sell accordingly. Abel argues that “mid-market” often mixes two different motions: SMB sales, which tends to rely on marketing and repeatable transactions, and enterprise sales, which is more relationship- and sales-led. Avoid pricing and packaging that leave you stuck between the two.
• Target leading brands earlier than conventional advice suggests. Top companies may be willing to experiment because they need to preserve their market position. They can also provide credibility with investors, talent, and other customers. Involve the founder in early conversations.
• Sell a vision and an advantage—not just a fix for a problem. Enterprise leaders want to understand how a product could help them get ahead, change how they work, or become more effective. For example, a Cursor pitch could emphasize access to more productive engineering teams, rather than only describing coding features.
• Avoid low-price anchors in enterprise deals. A small initial contract can make a later price increase difficult to justify and may attract customers who are not strong fits. Frame the offer around the value and scope appropriate for an enterprise. If starting smaller, establish a credible path to expansion early.
• Use services as a route into enterprise accounts. Companies already buy services and outside expertise. A service-led engagement can help establish trust and solve an initial problem, then create a path to adopting the underlying software. This is a deliberate entry strategy, not a reason to let bespoke work pull the product away from its broader vision.
• Treat design partners as learning partners, not guaranteed revenue. Select organizations and people who understand early-stage products, are willing to give feedback, and share the founder’s direction. Be candid about what works today, what does not, and what the next 6–12 months could involve. Use feedback selectively: Abel describes much of it as noise, with a smaller portion providing valuable insight.
• Keep the founder’s product direction clear. Listen to customer feedback, but do not build solely for one design partner. The founder must interpret requests against the market opportunity and be prepared to say no.
• Make enterprise selling creative and relationship-driven. Shape each agreement around the customer’s priorities, and consider adding value beyond the core product—such as implementation help, integrations, or a customer speaking opportunity. Build trust by being responsive and helping the buyer make a compelling internal case.
• Qualify directly. Ask questions that clarify whether the deal can realistically close, what the buyer needs to succeed, and what objections remain. A clear “no” is useful information; it saves time and can preserve the relationship.
• Personalize outbound manually for high-value accounts. Abel favors researching the individual and company and writing a tailored message rather than relying on generic AI-generated personalization or mass-database outreach. Her rationale is that human judgment can help reach people and angles that automated campaigns miss.
• Hire enterprise sellers only after the founder has learned the motion. A salesperson needs repeatable examples to work from and must be able to convey the founder’s vision, adapt to different buyers, and navigate enterprise decision-making. Abel cautions against assuming that a successful SMB seller—or a senior salesperson whose former employer’s brand did much of the selling—will succeed in an early-stage enterprise role.
• Do not assume consultants will become a dependable sales channel. Large consulting firms can introduce companies to solutions, but Abel warns against treating them as automatic distributors or vision-led partners.

Metrics and figures cited

• Stage discussed: Approximately $1M to $10M ARR.
• Enterprise contract size: Abel says enterprise buyers are accustomed to initial contracts in roughly the $75K–$150K range. She recommends aiming near $100K when the product’s value supports it.
• Small-deal warning: Relying on $10K–$20K contracts can make the economics difficult for a venture-backed enterprise business. Abel contrasts one $100K customer with ten $10K customers, arguing that the larger customer may provide more meaningful learning and expansion potential.
• Illustrative expansion path: A hypothetical $10K-per-month entry deal growing to $50K within four months could work, but Abel describes that path as difficult and uncommon. Another example suggests design partners might receive a 30% ongoing discount, with target pricing and future scope made clear from the outset.
• First sales hire: Around $1M ARR, often after securing roughly 7–10 customers, when the founder has learned enough to explain what works.
• Sales compensation: A typical structure discussed is 50% base salary / 50% variable compensation. Technology sales commissions were cited at approximately 8–12%, or around 10% on average.
• Hiring risk: Abel and the host discuss a high failure rate for early sales hires. Hiring two people to compare performance is raised as a possible approach, though finding two strong candidates is difficult.
• Long-term account potential: Abel gives the example that a $100K deal, if expanded successfully, could become a much larger multi-year relationship—potentially around $1M over three to five years. This is presented as an illustration, not a guaranteed outcome.

Examples discussed

• Tier-one prospects: Walmart, McDonald’s, Nvidia, Tesla, and other category leaders are cited as possible early adopters seeking an edge.
• Enterprise implementation: Palantir’s forward-deployed engineers illustrate how working alongside customers can reveal needs and build trust. Abel also points to consulting firms’ on-site work as evidence that enterprises are accustomed to buying services.
• Lower-risk adoption: In sensitive data environments, start with a limited use case or customer subgroup before asking an organization to connect broader datasets.
• Product adoption: Slack and Figma are mentioned as examples of products that can justify changing established ways of working.

Presenters and sources

• Presenters: Jen Abel and Lenny Rachitsky.
• Other people referenced: Justin, Katie Sierra, April Dunford, Jason Lemkin, Jason Cohen, and Gavin Baker.
• Companies and products discussed as examples: Cursor, Walmart, Stripe, OpenAI, Anthropic, Palantir, Slack, Figma, Microsoft Teams, Gemini, Deloitte, and Accenture.