top of page

The Ultimate Guide to Founder-Led Sales with Jen Abel, Co-Founder of JJELLYFISH

For an early-stage startup, sales is not merely the commercial function that follows product development. It is one of the fastest ways to discover whether the market recognizes the problem, values the founder’s perspective, and is willing to change its behavior. That makes selling an essential part of building the company—not a responsibility to hand off at the first opportunity.

On Lenny’s Podcast, JJELLYFISH co-founder Jen Abel draws on her experience helping startups navigate the zero-to-one stage. Her central argument is that founder-led sales should initially optimize for learning rather than immediate revenue. By speaking directly with prospective customers, founders can refine their market thesis, recognize real buying signals, and gradually earn the right to build a scalable sales operation.

Why the Founder Should Lead Early Sales

Abel defines founder-led sales as the startup’s first commercial milestone: finding and closing an initial group of customers before there is a recognizable brand, a marketing engine, or a library of references. At this stage, the founder is often the company’s most credible representative because the founder holds the original insight behind the product.

That advantage goes beyond enthusiasm. Abel identifies several qualities that are difficult to reproduce through an early sales hire. A founder can explain the company’s vision with unusual depth, carries the authority to make decisions during a conversation, and can notice unexpected customer reactions that might reshape the product or positioning.

Those small moments matter because the original vision rarely survives contact with the market unchanged. A prospect may describe the problem differently, care about a use case the founder considered secondary, or reveal an organizational constraint that changes how the solution must be sold. If this information passes from customer to salesperson to founder, it can become distorted. Direct participation removes that “telephone game” and makes the founder accountable for what the market is actually saying.

Treat the Sales Cycle Like Product Development

Founders without sales experience often see selling as a mysterious talent. Abel recommends making it more manageable by separating the process into stages, each with a distinct objective.

A conventional business-to-business cycle might begin with an introductory conversation, move to a demonstration, continue through a proposal and jointly defined scope, and then enter procurement and contracting. The exact sequence varies, especially when an experienced buyer has an established purchasing process. The important point is that every meeting should create a specific form of progress.

This resembles product development. An initial pitch is only a hypothesis. Conversations, objections, demonstrations, and proposal revisions provide the tests. The founder then uses the results to improve the next version of the sales motion.

This perspective also helps diagnose failure. A weak pipeline does not automatically mean the founder needs better closing techniques. The problem might be poor targeting, an unconvincing market insight, or insufficient urgency. Breaking the cycle into stages reveals where momentum disappears.

Cold Outreach Should Create Curiosity

Prospects are surrounded by generic messages claiming that a new product is faster, easier, or better. Abel argues that effective outreach must give the recipient a reason to reconsider something they already believe.

She prioritizes relevance over superficial personalization. Mentioning a prospect’s recent social post may show effort, but it does not prove that the message concerns an important business issue. Strong outreach instead connects a specific person or company to a meaningful problem and introduces a surprising technical, commercial, or market insight.

The best opening may even create a moment of disbelief: “I have never thought about it that way.” Abel’s own example—asserting that zero-to-one sales talent does not exist—works because it challenges a familiar assumption and naturally invites a follow-up question.

A useful outreach message generally does four things:

  • Establishes why the issue is relevant to this recipient.

  • Introduces an unexpected or counterintuitive observation.

  • Focuses on the unresolved problem rather than explaining the whole product.

  • Fits into three or four clear sentences.

Conciseness is not just stylistic. A short message is easier to understand on a phone and intentionally leaves room for curiosity. The objective is to earn a conversation, not compress the entire pitch deck into an email.

Abel also notes that founders should test more than email. LinkedIn and cold calls can work, and calling may generate stronger engagement in some markets. The right channel matters less than whether the problem is recognizable and the insight feels worth discussing.

Start with 30 Carefully Chosen Prospects

Before purchasing prospecting software or launching an automated sequence, Abel recommends manually finding 30 people the founder genuinely wants to learn from. This small sample forces clarity.

Can the target buyers be discovered through public information? What characteristics do they share? Which role owns the problem? What observable signals suggest that the issue is relevant to them? If finding 30 plausible prospects is difficult, reaching thousands through automation will not solve the underlying segmentation problem.

Each person should receive a thoughtful, compact note. Abel suggests investing roughly 15 to 30 minutes per message at this stage. Founders can then compare responses and adjust one variable at a time: the target role, the framing of the problem, or the central insight.

This is a quality-first experiment, but it also tests future scalability. Tools for enrichment and outbound campaigns become useful only after the founder understands which data points identify a promising buyer. Automation magnifies an established pattern; it cannot discover that pattern on the founder’s behalf.

Abel offers a simple editing technique as well: listen to the email read aloud. Hearing the words can expose a tone that sounds awkward, insincere, or unintentionally aggressive.

Read Conversion and Win Rates Together

Response or meeting-conversion rates receive plenty of attention, but Abel cautions against evaluating them in isolation. The downstream win rate determines how much top-of-funnel efficiency a company actually needs.

If a startup wins 30% or 40% of qualified opportunities, a modest outbound conversion rate may still support a healthy motion. If few opportunities become customers, the company must generate a much larger pipeline merely to compensate. Abel describes approximately 5% to 7% as a healthy outbound conversion range in many situations, while acknowledging that results can fall below or rise well above it.

More importantly, low conversion may be a market signal rather than a sales-execution problem. When buyers acutely feel a problem, they tend to respond across channels. Persistent indifference can mean that the issue is too narrow, insufficiently urgent, or framed through the wrong insight.

This also helps explain why product-market fit arrives at different speeds. Abel contrasts startups that begin with a known market pain with those built around a technical breakthrough. Starting from demand may shorten the search, although it can constrain the opportunity. Beginning with technology can carry greater risk and require a longer market-discovery period, but it may offer a much larger upside.

Make the First Call a Learning Environment

Early-stage founders sometimes exaggerate how complete the product is because they fear that vulnerability will weaken their position. Abel recommends the opposite. A founder can explain that the company is early, describe the problem it is investigating, and invite the buyer to correct its assumptions.

This candor creates space for more useful feedback. It also encourages founders to treat the prospect as an informed participant who may understand the domain better than they do.

Rather than relying on generic questions about “pain points,” Abel suggests exploring the structure and consequences of the problem:

  • How does the issue appear inside the organization?

  • What happens if it remains unresolved?

  • Is anyone measuring or managing it today?

  • What has the company already tried?

  • Is the problem expanding, or has it become a tolerable inconvenience?

The founder should listen for evidence that the prospect is mentally constructing a solution. Previous attempts to fix the issue, discussion of budget, or a desire to involve colleagues can all indicate movement from polite interest toward buying intent.

A growing problem has particular value. Buyers rarely accept switching costs and career risk merely to replace something that feels “good enough.” They act when the consequences of inaction begin to exceed the difficulty of change.

Secure Progress, Not Polite Interest

A productive first call should end with a concrete next step. Abel recommends opening calendars during the conversation and deciding who should join the next meeting. This makes the second call a natural continuation rather than a vague future possibility.

A prospect who promises to follow up by email may simply be declining politely. Founders should respect that possibility while recognizing it as a weak signal. Calendar commitment is more informative than verbal enthusiasm.

The same principle applies throughout the cycle. Prospects demonstrate seriousness through actions: sharing internal context, introducing stakeholders, revising a scope, explaining procurement, or committing time. Compliments alone are not progress.

Co-Author the Solution with Early Customers

Abel sees co-authoring as one of the strongest tools available to an early startup. Instead of presenting a rigid proposal, the founder invites the customer to help define the desired outcome and scope of work. Specificity makes the offering feel relevant while revealing how prepared the organization is to buy.

Buyer maturity is crucial. A company without an internal process, strategy, or owner for a problem may not yet be capable of adopting software to solve it. In that case, Abel suggests that a time-limited service engagement can help the customer develop the necessary operating model.

Services revenue may be non-recurring, which can make investors wary, but it can still produce valuable evidence. The customer pays to learn, the founder gains access to real workflows, and both sides discover what a future product must accomplish. Abel notes that this pattern has been particularly useful for AI startups introducing unfamiliar capabilities.

She recommends time-boxing such work—often to approximately 90 days—rather than making an open-ended services commitment. A defined period allows the parties to establish goals, learn together, and reassess as the product and customer environment evolve.

Know When to Build a Sales Team

There is no universal revenue threshold for ending founder-led sales. Abel discusses figures ranging from roughly $500,000 to $1 million in annual recurring revenue, but emphasizes that velocity and repeatability matter too.

The deeper question is whether the company has learned enough for another person to reproduce the motion. Can it identify likely buyers, articulate the problem, run discovery, recognize qualification signals, navigate the purchasing process, and explain why customers win?

Abel challenges the assumption that an early salesperson can answer those questions for the founder. She points to companies such as Sprig and Zip as examples of startups that invested heavily in customer learning before expanding sales. One provocative interpretation is that seed-stage companies should remain focused on experimentation, while the period around Series A is better suited to exploiting a pattern that has already emerged.

Founder-led sales therefore ends not when founders become tired of selling, but when they can transfer a tested system. Until then, every customer conversation is part of the product, positioning, and market-discovery process.

Sources

Get started for free

A local first AI Assistant w/ Personal Knowledge Management

remio only supports Windows 10+ (x64) and M-Chip Macs currently.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page