**Summary**
The speaker outlines a typical B2B sales progression for early‑stage founders and highlights common pitfalls and best practices at each stage:
1. **Design Partnership** – Often starts with unpaid, loosely scoped collaborations (e.g., observing a customer’s workflow, co‑designing). These tend to drag on for months with low engagement and rarely lead to revenue.
*Tip:* Use the time to pinpoint a narrow, “burning” problem, build a minimal wedge product (as fast as 48 h), test it, and iterate until the customer loves it—then stop adding features.
2. **Free Trials / Pilots / Proof‑of‑Concepts** – Customers want to try before paying, but these are frequently too long (2‑3 months) and lack clear success metrics or commitment.
*Tip:* Define a specific value equation (e.g., % cost saved or revenue uplift), agree on measurable success criteria, keep the trial short, and use side‑by‑side or back‑testing to prove value quickly.
3. **Paid Pilots** – Introducing an upfront financial commitment (even a modest amount) makes the customer take the pilot seriously.
*Tip:*
- Secure a willingness‑to‑pay conversation early.
- Align the pilot with a live customer project and dedicated internal resources.
- Keep the duration just long enough to experience value (often 7‑14 days).
- Use lightweight data exchange (Excel imports/exports, email) to avoid delays from heavy integrations.
- Schedule a post‑pilot meeting before it starts to review ROI metrics.
4. **Recurring Revenue Contracts with Opt‑Out Period** – The “pro move”: sell a monthly/annual contract that includes a 30‑60‑day money‑back or opt‑out window. If the customer does nothing, it automatically converts to a full recurring contract, eliminating a second negotiation round.
*Tip:* Only attempt this once you have a proven wedge product, some social proof, and a sales process that can deliver quick time‑to‑value.
**Additional Advice**
- **Avoid overbuilding:** Focus on solving one narrow problem exceptionally well rather than trying to match feature‑parity with incumbents.
- **Internal champion:** Identify a customer advocate who can sell internally, budget‑fight, and help drive the deal.
- **Security certifications:** Start SOC 2, HIPAA, ISO 27001, etc., early to prevent months‑long delays.
- **Customer success:** After signing, invest heavily in onboarding and ensuring the customer realizes value; otherwise, contracted revenue may go unrealized.
- **Pragmatic contract handling:** Be flexible on NDAs/legal redlines unless they pose existential risk; use scarcity (“we can only take two enterprise customers this quarter”) to create urgency.
- **Investor reporting:** Be transparent about whether ARR/MRR includes customers still in an opt‑out period.
By moving swiftly through these stages—short, validated pilots with clear metrics, early financial commitment, and opt‑out recurring contracts—founders can close new ARR weekly and scale their B2B business efficiently.
1. YC works with many founders who are navigating the B2B sales process for the first time.
2. Founders commonly make avoidable mistakes in early B2B sales.
3. The typical progression starts with a poorly defined, overly long unpaid design partnership.
4. After design partnership, founders often move to free trials, pilots, or proof of concepts.
5. Next step is paid trials with an upfront financial commitment.
6. The final stage is recurring revenue contracts with an opt‑out period.
7. Early‑stage companies aim to close new ARR every week by moving quickly through this sequence.
8. Approximately 90% of founders get stuck in the early stages (long unpaid design partnerships).
9. About 5‑10% of founders try to speedrun the entire process before their product is mature or they have social proof.
10. Most founders progress too slowly through the sales stages.
11. A design partnership involves observing the customer’s work and co‑designing the product.
12. Design partnerships often last 3‑6 months and have poorly defined scope.
13. Customer engagement in design partnerships is usually low because the work is unpaid.
14. Sitting next to a customer for a few days to observe their work is valuable for understanding the problem.
15. Founders should identify narrow pieces of work to automate, such as asking what part of the job the customer hates most.
16. Founders can manually do the work for the customer or even go undercover to get qualified and perform the job for a couple of months to deeply understand the domain.
17. The goal is to find a narrow burning problem and build a wedge product in as little as 48 hours.
18. Iterate on problem‑solution sets until the customer loves the wedge product.
19. If the customer is willing to pay and use the wedge product, founders should not build additional features but instead sell the wedge to about 10 similar customers.
20. Trying to overbuild a broad platform at this stage wastes time due to limited resources and lack of customer signal.
21. It is better to focus on delivering one part of the solution exceptionally well (a narrow wedge).
22. In design partnerships, customers sometimes treat founders as an unpaid dev shop and give ever‑growing requirement lists.
23. Founders often avoid asking for money, do bespoke work for free, and the relationship can feel abusive.
24. Not all design partnerships are wasted time, but most are.
25. Free trials, pilots, and proof of concepts are essentially the same: customers try the product before paying.
26. Early customers want to test the product before making a financial commitment.
27. Free trials often last 2‑3 months and suffer from low commitment and no clear end goal.
28. A proof of concept must define what is being proved and agree on success metrics with the customer.
29. Example value equation: solving 20% of inbound queries could reduce a 100‑person team to 80, saving $1 M/year; charging $200k for the software reflects that ROI.
30. To prove value, give the customer a sample (e.g., 1,000 queries) and measure the actual solve rate.
31. Validation techniques include back‑testing on historical data, side‑by‑side trials with existing processes, taking on 1% of volume, or rolling out in a smaller geography first.
32. Free pilots risk low customer engagement and founders’ reluctance to discuss willingness to pay.
33. Founders should ask customers how much the solution would be worth to them to determine willingness to pay.
34. Customers who are not ready, able, or willing to buy should be disqualified early.
35. After a free trial, founders normally transition to paid trials.
36. In a paid trial, secure an upfront financial commitment and ask about willingness to pay for the full product (annual fee/price point).
37. Founders can ask the internal champion for the amount they can personally approve (e.g., $10k‑$20k on a corporate card).
38. Additional commitments beyond payment may include waiting for a live project, having a dedicated customer‑side team, or scheduling frequent check‑ins.
39. Paid trials should be kept short—just long enough for the customer to experience the full benefit (often 7‑14 days if the product is well‑tuned).
40. Early‑stage sales sell the founders and early team, promising personal support (cell phone, 24/7 response) if issues arise.
41. Tracking time to first value as a northstar metric and reducing it from weeks to hours improves pilot‑to‑paid conversion.
42. To get the product live quickly, avoid full API integration that requires customer engineering time; use Excel imports/exports or email data back and forth.
43. Book a post‑pilot meeting before the pilot starts to review metrics and show hard ROI numbers at the end.
44. After a paid pilot, a second sales process is needed to negotiate the full contract.
45. Sophisticated founders move from paid pilots to recurring revenue contracts with an opt‑out period (typically monthly or annual with a 30‑ or 60‑day money‑back guarantee).
46. If the customer takes no action and is happy, the contract automatically becomes a full recurring agreement after the opt‑out period, requiring no additional sales process.
47. This “pro move” turns one sales process into a recurring revenue contract.
48. Early‑stage founders may lack the sales process, social proof, or product readiness to jump straight to this step.
49. An alternative is to start with a free pilot for the first one or two customers, then progress onward.
50. After signing contracts, focus on customer success: onboarding and ensuring the customer derives value.
51. Example: a company signed $4 M of contracts but implemented less than $2 M due to missing customer‑success function.
52. Founders should start SOC 2 compliance as soon as possible; other certifications (HIPPA, ISO 27001) can also cause months of delay.
53. Identify the internal champion and treat them like a co‑founder who sells for you when you’re absent and fights budget battles.
54. Set a defined closing date with the champion and use it to create urgency, even if the date is often missed.
55. Ask the champion to describe their last software purchase, including who had to approve it and the process, to map the organization.
56. Map stakeholders: economic buyer, technical approver, security gatekeeper, legal team, day‑to‑day users, and devise a plan to win each explicitly.
57. After understanding the buying process, drive it forward yourself and never leave a meeting without setting the next touch point.
58. Physically visiting the customer in person can significantly advance a deal.
59. Avoid getting stuck in endless rounds of contract/NDA reviews; legal teams’ redlining slows progress without substantially reducing risk.
60. Be flexible on contract terms as long as they do not expose you to unlimited liability or IP‑transfer clauses that could end the company.
61. Using scarcity helps: state you have capacity for only a limited number of enterprise customers and ask for a commitment or suggest revisiting in six months.