**Summary of the talk on pricing for founders**
1. **Start with the value equation**
- Work with the customer’s champion to list the concrete value your product will deliver (cost savings, time savings, revenue increase).
- Get the champion to validate the assumptions; this becomes the justification you can show to finance or the CFO.
- Price your offering at roughly **one‑third of the quantified value** (letting the customer keep about two‑thirds).
2. **Check your costs**
- Determine the actual cost to deliver the service (e.g., cloud fees, API usage).
- Your price must be **well above cost**; otherwise you’re unsustainable. Aim for **80‑90% gross margins** in software.
- Treat any promotional credits (AWS, OpenAI, etc.) as real cash costs—don’t assume they’ll last forever.
3. **Consider competition**
- If a competitor undercuts you, avoid a price‑to‑price war; it erodes margins for everyone.
- Differentiate your product (features, integrations, industry focus, compliance, data‑privacy, etc.) so the comparison isn’t apples‑to‑apples.
- Only compete on price if you have a credible plan to dramatically lower costs; otherwise, focus on value.
4. **Pricing structure & sales motion**
- Mirror the pricing models your target customers already use (flat monthly, per‑seat, usage bands, etc.) and keep it simple.
- Prefer **recurring revenue (MRR/ARR)** over pure usage‑based models for stability.
- A useful tactic: start with usage‑based pricing for a trial period, then convert to a minimum monthly commitment with volume discounts.
- Align price with the champion’s signing authority (e.g., keep pilot pricing under the amount they can approve solo).
5. **Publishing prices**
- For self‑serve or SMB plans, publish clear prices on the website.
- For enterprise deals, keep pricing “contact sales” because the value equation varies per customer; publishing a single number risks over‑ or under‑pricing.
- Gate enterprise‑only features (SSO, audit logs, compliance certifications, data‑residency, etc.) behind higher tiers.
6. **Free trials / pilots**
- Keep them short (2‑4 weeks) with explicit success criteria tied to the value equation.
- Alternatively, offer an annual contract with a 30‑/60‑day money‑back guarantee to lock in recurring revenue up front while still reducing risk.
7. **Sales‑team economics**
- Ensure each salesperson can generate enough new ARR to cover their compensation (≈5:1 ratio of new ARR to total comp).
- Adjust deal size and volume accordingly (few large “whale” deals vs. many smaller transactions).
8. **Early‑stage pricing advice**
- If you’re uncertain, pick a price comparable to similar software your customers buy, then increase it by ~50 % with each new customer until you start losing >25 % of deals on price alone.
- Early customers are a tiny fraction of long‑term revenue; focus on closing deals, learning, and raising price as the product improves and you add paid modules or upsells.
**Bottom line:**
- **Value equation → price ≈ 1/3 of value**
- **Validate that price ≫ cost** (target high margins)
- **Differentiate rather than price‑war**
- **Match pricing to customer buying habits, keep it simple, and favor recurring revenue**
- **Use short, measurable pilots or money‑back guarantees**
- **Align price with sales‑team economics and signing authority**
- **Iterate: start with a reasonable market‑based price, test, and raise as you gain traction and proof of value.**
1. Tom is a partner at Y Combinator.
2. He discusses how founders often struggle to set price after a successful sales call.
3. Founders may lack calibration on what companies typically pay for software.
4. They sometimes choose low prices like $19 or $49 per month based on personal software purchases.
5. Asking for tens or hundreds of thousands of dollars can feel uncomfortable for founders.
6. The value equation involves determining the expected value (cost saving, time saving, or revenue increase) with the customer champion.
7. The expected value should be written down step‑by‑step and challenged by the champion to verify assumptions.
8. The value equation provides justification that the champion can present to a CFO or boss.
9. In an example, a company with 100 support agents each costing $100,000 per year has a total customer‑service cost of $10 million.
10. An AI tool that reduces queries or time by 20 % yields a potential cost saving of $2 million.
11. Pricing is often set at 25‑50 % of the delivered value, meaning the vendor keeps roughly one‑third and the customer keeps two‑thirds.
12. Applying this to the example, a $2 million saving could justify a vendor price around $700 k.
13. The value equation also defines success metrics for a pilot, such as achieving a 20 % query reduction or 20 % time saving.
14. Cost should be used only as a floor; pricing should not start with a cost‑plus approach.
15. If the vendor’s cost exceeds the price, the business would not be profitable.
16. Software companies typically aim for gross margins of 80‑90 %.
17. Cloud credits (e.g., AWS, OpenAI) should be treated as a cash cost, not assumed to be unlimited.
18. Pricing at or below cost is a risky maneuver sometimes used to gain market share.
19. In competitive markets, engaging in a price war can lead to a race to the bottom with no winners.
20. Differentiating the product via functionality or value is recommended instead of competing solely on price.
21. In commodity markets (e.g., airlines), margins are driven low; the airline industry averages a 2.7 % net profit margin.
22. Founders should ask champions how they currently pay for similar software (monthly flat fee, per‑seat, usage bands, credits).
23. Mirroring familiar pricing structures can improve adoption; keeping pricing simple is advised.
24. Committed recurring revenue (MRR/ARR) is preferable to pure usage‑based revenue for stability during downturns.
25. A common technique is to start with usage‑based pricing for new customers, then transition them to a minimum monthly commitment with volume discounts after measuring usage.
26. Knowing the champion’s signing authority (e.g., up to $15 k) helps set pilot pricing that can be approved without higher‑level review.
27. Publishing a single price on a website for enterprise deals can leave money on the table because value varies per customer.
28. SaaS companies often gate enterprise‑only features (SOC 2 reports, SSO, audit logs, compliance, data residency) behind higher tiers, allowing price differentiation up to 10×.
29. Pricing strategy influences sales channels; a rule of thumb is a 5:1 ratio between new signed ARR and total sales compensation.
30. For a salesperson earning $100 k total compensation, the expected new ARR is about $500 k per year.
31. That ARR can be achieved through few large contracts or many smaller ones, affecting the sales model (e.g., hunting whales vs. high‑volume inside sales).
32. Free trials or pilots should be short (a couple of weeks to four weeks) with clear success criteria.
33. An alternative is to offer an annual contract with a 30‑ or 60‑day money‑back guarantee, which counts as recurring revenue from the start.
34. Early‑stage founders should leverage their strengths (e.g., founder accessibility) rather than pretending to be a larger company.
35. The first few customers represent only a tiny fraction of future revenue; getting initial deals closed and establishing a sales flow is more important than perfect early pricing.
36. The first sales are typically the hardest; closing them builds validation and enables later price increases as the product improves.