From 0 to €1M, 0 to 10 Clients: The B2B Founder-Led Sales Playbook

Jen Abel has coached hundreds of B2B startups through their first ten enterprise deals. Her framework, distilled from years of pattern-matching across industries, stages, and deal sizes, is the most practical playbook I have encountered for the zero-to-one phase of enterprise sales. It is not a sales methodology. It is a learning methodology that uses sales as its instrument.

This essay synthesises her key ideas and extends them with observations from the European B2B landscape.

The Founder Is the Product

Abel’s first principle is disorienting for technical founders: in the first ten deals, the founder is the product. Not the software. Not the platform. Not the technology. The founder. Their domain knowledge, their ability to understand the customer’s problem, their willingness to do whatever it takes to make the customer successful.

This is not a motivational platitude. It is a structural observation about early-stage B2B dynamics. The customer is not buying software. The customer is buying a bet on the founder’s ability to solve their problem. The software is evidence of that ability, but it is not the thing being purchased.

The implications are immediate:

• The founder must sell. Hiring a salesperson before you have ten customers is a mistake. Not because salespeople are bad, but because the founder needs the direct feedback that only selling provides. Every objection is product insight. Every lost deal is a positioning lesson. You cannot outsource learning.
• The founder must deploy. Being present during implementation reveals the gap between what you sold and what the customer actually needs. This gap is the most valuable information in the company. A founder who sells but does not deploy is flying blind.
• The founder must support. Early customer support is not a cost centre. It is a research lab. Every support ticket is evidence of a product failure, a documentation failure, or a positioning failure. Founders who delegate support before product-market fit are delegating their most important source of insight.

The first ten customers are not revenue. They are R&D.

Outbound as Insight Test

Abel reframes outbound sales in a way that removes the stigma many founders attach to it. Outbound is not selling. Outbound is hypothesis testing. Every cold email tests a hypothesis about who has the problem you solve, how they describe it, and what they would pay to make it go away.

The methodology:

1. Define the hypothesis. “VP of Operations at mid-market logistics companies spend 20+ hours per week on shipment exceptions, and would pay $50K/year to reduce that by 80%.” This is specific enough to test and falsifiable enough to be useful.

2. Write the outreach. The email does not describe your product. It describes the customer’s problem. “Do you spend more than 20 hours per week on shipment exceptions?” If the answer is yes, you have a conversation. If the answer is no, you have a data point. Both outcomes are valuable.

3. Measure responses, not meetings. The response rate tells you whether your hypothesis about the problem resonates. The meeting rate tells you whether your positioning is credible. The conversion rate tells you whether your solution is compelling. Each metric tests a different hypothesis.

4. Iterate weekly. Change one variable per week. Different persona. Different problem statement. Different value proposition. The outbound motion is a search algorithm. You are searching for the intersection of a real problem, a reachable buyer, and a viable price point.

The founders who struggle with outbound are usually the ones who treat it as persuasion. They try to convince people to buy. Abel’s reframe converts outbound from persuasion to research. You are not trying to sell. You are trying to learn. The sales, when they happen, are a byproduct of having found a genuine problem-solution fit.

Co-authoring and Services

Abel’s most controversial advice: in the early days, sell services, not software. This horrifies investors who want to see scalable, high-margin SaaS revenue. But Abel’s argument is precise: the service layer is how you learn what the software should do.

The pattern she recommends:

• Phase 1: Service. Do the work manually for the customer. Understand every step, every edge case, every exception. Bill for the service. This is not charity. This is paid research.
• Phase 2: Co-author. Build software that automates the parts of the service that are repetitive and well-understood. Keep doing the complex parts manually. The customer is co-authoring the product with you because the product is being built around their actual workflow, not your imagination of their workflow.
• Phase 3: Product. When the software handles 80% of the work, transition the customer to a software contract. The remaining 20% becomes the next development cycle. Repeat.

This approach has three advantages:

1. Revenue from day one. You are billing for the service while you build the product. This extends runway and demonstrates willingness to pay.
2. Product-market fit by construction. The product is built from observed workflows, not hypothesised ones. It cannot fail to fit the market because it was extracted from the market.
3. Switching costs. A product co-authored with the customer is deeply embedded in their workflow. Replacing it requires rebuilding the workflow, not just swapping vendors.

Procurement as a Second Sale

Abel identifies a failure mode that kills deals after they have been won: procurement. The buyer says yes. Then the deal enters procurement, legal review, security review, vendor onboarding. Each of these is a separate sale to a separate stakeholder with separate incentives.

The procurement team does not care about your product’s value. They care about risk, compliance, and vendor management. You must sell to them on their terms, not yours. This means:

• Have your security documentation ready before anyone asks. SOC 2, GDPR compliance, data processing agreements. The absence of these documents does not kill the deal. The delay caused by scrambling to create them does.
• Understand the procurement timeline. Large enterprises have quarterly budget cycles. If you miss the window, you wait three months. Map the procurement process in the first sales meeting, not the last.
• Find a procurement champion. Just as you need a champion in the buying organisation, you need someone in procurement who will shepherd your deal through the process. This person exists. Find them.
• Price for procurement simplicity. A $48K/year contract that fits under the VP’s signing authority closes in two weeks. A $52K/year contract that requires C-suite approval closes in four months. The $4K difference costs you three months of deployment and learning.

Four Essential Principles

Abel’s framework resolves into four principles that apply to every B2B founder navigating the zero-to-one phase:

1. Sell learning, not product. Every sales interaction is a learning opportunity. The deal is valuable. The insight is invaluable. Structure every interaction to maximise both.

2. Narrow before you broaden. The instinct is to cast a wide net. The correct strategy is to go impossibly narrow: one industry, one persona, one problem. Dominate a niche before you expand. The niche gives you case studies, references, and expertise that make the expansion credible.

3. Price on value, not on cost. Your cost structure is irrelevant to the customer. What matters is the value you create. If you save the customer $500K per year, a $100K price point is a bargain. Founders consistently underprice because they anchor on their costs rather than the customer’s savings.

4. Build the machine before you scale it. The first ten deals should be messy, manual, and deeply personal. The founder should be in every meeting, on every call, at every deployment. Only after the pattern is clear should you begin to systematise. Premature systematisation locks in assumptions that have not been validated.

The playbook is not complicated. It is hard. It requires founders to do uncomfortable things: cold email strangers, sit through procurement reviews, do manual work that does not scale. But the founders who do these things in the first year build companies on a foundation of genuine customer understanding. The ones who skip them build on assumptions, and assumptions do not compound.