This video by Tom Blomfield from Y Combinator outlines a structured B2B sales progression for founders, identifying common pitfalls and best practices, and emphasizes moving quickly through stages to secure recurring revenue.
Avoid Overly Long Design Partnerships: Many founders get stuck in poorly defined, unpaid design partnerships that yield little revenue. Instead, focus on understanding customer problems.
Identify Narrow Problems: Engage with customers by observing their work and asking about their biggest pain points. Develop a "narrow wedge product" quickly (within 48 hours) to solve a specific problem.
Transition to Focused Pilots: Move from free trials (often too long and low commitment) to paid pilots with clear, agreed-upon success metrics and a short timeframe (7-14 days).
Secure Financial Commitment: Discuss willingness to pay early and accept smaller upfront payments to bypass lengthy procurement processes.
Aim for Recurring Revenue Contracts: The "pro move" is a monthly or annual contract with a 30-60 day opt-out period, which automatically converts to full recurring revenue.
Prioritize Customer Success: Post-contract, dedicate significant effort to onboarding and ensuring customers derive value, as this is crucial for retention.
Key Sales Tips: Start security certifications early (e.g., SOC2), identify and empower internal champions, understand the customer's buying process, visit customers in person, be flexible with contract terms, and use scarcity to drive commitment.
Reducing customer service staff from 100 to 80 employees, saving $1 million annually with AI.
[
00:07:50
]
Take less money if it shortcuts a lengthy approval process.
[
00:11:00
]
Overview of B2B Sales Progression and Common Pitfalls [00:08]
Many founders navigate B2B sales for the first time and often make avoidable mistakes.
The goal for early-stage companies is to rapidly progress through sales stages to achieve annual recurring revenue (ARR).
Common Mistakes:
Most founders get stuck in early stages, particularly with long, unpaid design partnerships [01:03].
A smaller percentage (5-10%) try to "speedrun" to the end without a mature enough product or social proof [01:17].
Design partnerships are often too long and poorly defined.
[
00:02:20
]
Context: This stage is typical for very early companies with minimal product development (e.g., Figma mock-ups or just an idea) or those entering industries requiring deep domain knowledge (e.g., law, accounting) [01:41].
Traditional Approach: Founders spend time with a customer, often one with a "big fancy logo," observing their work and co-designing a product to meet their needs [02:02].
Common Problems:
Excessive Duration: Design partnerships are often too long (3-6 months) and poorly defined in scope [02:19].
Low Customer Engagement: Since customers aren't paying, they have low commitment and prioritize their own business, leading to vague and meandering engagements [02:27].
Misleading Progress: Founders get a "fancy logo" for their website, but it doesn't translate to real revenue [02:44].
Direct Observation: It's valuable to sit next to customers in their office and observe their work for a few days [02:57].
Focus on Automation: Identify narrow pieces of work that can be automated [03:07].
Key Questions: Ask customers, "What's the part of your job you hate the most?" or "If you could wave a magic wand, what part of your work would you get rid of?" [03:14].
Manual Immersion: Offer to do the work manually for the customer to deeply understand the process [03:22].
Undercover Work: Some founders go as far as getting qualified (e.g., as an auditor or real estate agent) and taking temporary jobs to gain deep domain understanding [03:30].
Develop a "Wedge Product": The goal is to identify a narrow, burning problem and build a minimal "wedge product" to solve it, ideally within 48 hours, then iterate [03:45].
Avoid Overbuilding: Do not try to build a broad platform or reach feature parity with existing software too early; focus on one problem and solve it exceptionally well [04:18].
Overbuilding wastes resources and lacks customer validation [04:26].
Customers in design partnerships might suggest features to be "helpful" rather than honestly critiquing the product [04:50].
Beware of customers treating founders as an "unpaid dev shop," constantly adding bespoke requirements without financial commitment [05:09].
Actionable Advice: Pick a narrow wedge product, sell it aggressively for a few weeks, and if it doesn't work, pick a different one [05:41].
Stage 2: Free Trials, Pilots, or Proof of Concepts [06:11]
Context: Used when an initial or narrow wedge product is built, but social proof from other customers is lacking [06:23]. Customers want to try the product before committing financially [06:34].
Common Problem: Similar to design partnerships, free trials are often too long (2-3 months) and suffer from low customer commitment due to undefined targets or end goals [06:52].
Techniques: Offer back-testing on historical data, side-by-side trials with existing processes, or phased rollouts (e.g., 1% of customer service volume or a smaller geography) [08:44].
Reduced Risk: These methods allow customers to test the product in a low-risk environment, protecting the champion from potential failure [09:21].
Address Willingness to Pay: Crucially, have conversations about the customer's willingness to pay early on to disqualify those not ready or able to buy [09:34].
Prove your product's value with a well-designed pilot.
[
00:08:00
]
Rationale: Once founders are comfortable with the sales process, they shorten pilots and secure upfront financial commitment.
Benefits:
Increased Engagement: A financial commitment makes customers take the pilot much more seriously, as they are paying for your time [10:21].
Early Price Point Discovery: Discuss the annual fee and full product price point upfront. It's better to know early if they aren't willing to pay [10:33].
Shortcut Procurement: Ask the champion if they can personally approve a smaller amount (e.g., $10,000-$20,000 on a corporate credit card) to bypass lengthy procurement processes [10:49].
Take less money if it shortcuts a lengthy approval process.
[
00:11:00
]
Having a dedicated person or team on the client side for testing [11:33].
Regular Check-ins: Schedule frequent check-ins (every couple of days) to address bugs immediately and impress enterprise customers with rapid fixes [11:40].
Short Timeframe: Keep the pilot duration as short as possible (7-14 days) to allow the customer to experience the full benefit quickly [12:01].
Selling the Founders/Team: Early-stage products are not bug-free. You are selling the promise of the founders and early team to solve the problem, offering personal commitment and 24/7 support [12:15].
Time-to-First-Value (TTFV): Track TTFV as a north-star metric, aiming to reduce it from weeks to hours to improve pilot-to-paid conversion [12:35].
Employ "janky" methods (e.g., Excel imports/exports, email data) instead of full API integrations to get the product live faster [12:45].
Pre-book Post-Pilot Review: Schedule a post-pilot business review meeting before the pilot even starts, where you present hard ROI numbers to determine if the customer wants to continue using the software [13:14].
Book a post-pilot business review meeting even before the pilot begins.
[
00:13:14
]
Stage 4: Recurring Revenue Contracts with Opt-Out [13:47]
The "Pro Move": Transition from paid pilots to a monthly or annually recurring contract with a 30-60 day money-back guarantee or opt-out period at the beginning [13:51].
Seamless Conversion: By default, if the customer does nothing and is satisfied, the contract automatically converts to full recurring revenue after the opt-out period, eliminating a second sales process [14:03].
Confidence in Sales: This approach allows founders to confidently state that "this is how customers buy our product," backed by existing clients [14:22].
Progression: While it can be challenging to start directly at this stage without a mature product or social proof, an initial free pilot for 1-2 customers can serve as a stepping stone [14:36].
Investor Reporting: Be careful and transparent when reporting Monthly Recurring Revenue (MRR) or Annual Recurring Revenue (ARR) to investors, especially if customers are still within their opt-out period [15:08].
Post-Contract Importance: After signing contracts, dedicate as much or even more effort to onboarding customers and ensuring they derive full value from your product [15:39].
Example: A company signed $4 million in contracts but only implemented $2 million due to a missing customer success function [15:47].
Security Certifications: Start SOC2 (as well as HIPPA, ISO 27001, etc.) as soon as possible, as these can cause significant delays [16:03].
Prioritize starting SOC2 and other necessary security certifications.
[
00:16:10
]
Internal Champion: Identify your internal "champion" within the customer's organization and treat them like a co-founder; they will sell for you and fight for budget [16:25].
Identify and cultivate your internal 'champion' within the customer's organization.
[
00:16:30
]
Defined Closing Date: Work with your champion to set a defined closing date, even if it's often missed, to create urgency [16:39].
Understand Customer's Sales Process: Ask the champion to describe their internal buying process upfront – who needs to approve it (economic buyer, technical approver, security gatekeeper, legal team, day-to-day users) – and devise a plan for each stakeholder [16:48].
Ask customers upfront about their internal sales and approval process.
[
00:16:50
]
Drive the Process: Always drive the process forward; don't leave a meeting without setting up the next touch point [17:12].
In-Person Visits: Physically visit customers in person; it can work wonders and accelerate the sales process [17:21].
Contract Flexibility: Be flexible with contracts and NDAs, avoiding endless redlining by legal teams, unless a clause poses "company-ending" risks like unlimited liability or IP transfer [17:36].
Avoid getting bogged down in endless contract or NDA redlining.
[
00:17:40
]
Use Scarcity: Create urgency by stating limited capacity (e.g., "We only have capacity to work with two enterprise customers this quarter") [18:10].
Use scarcity as a sales tactic to create urgency.
[
00:18:20
]