If your AI does the work a human used to do, charging per seat is leaving 10x on the table — and YC partners know it.
W25 is the first batch where outcome-based or seat-replacement pricing was the default, not the exception.
The three pricing shapes that showed up in W25
- Per-outcome: charge per resolved ticket, per booked meeting, per filed contract. Maps cleanly to the customer's existing cost line.
- Seat-replacement: price as a fraction of the loaded cost of the human role being replaced. Often 20–40% of fully-loaded salary.
- Usage + floor: a small platform fee plus per-action pricing, so you capture both low and high-volume customers.
Why this shift matters at the seed stage
Outcome pricing changes the ARR conversation. $30/seat × 50 seats reads as a $18k account. 'We close 4,000 tickets/month at $2 each' reads as a $96k account doing the same work — and a much clearer expansion story.
It also changes who you sell to. Per-seat sells to IT. Outcome pricing sells to the line-of-business owner who actually has the budget pain.
How to reframe your pricing in one afternoon
- Find the unit of work your customer already measures (tickets, claims, leads, jobs).
- Price 60–80% below the current cost-per-unit. Make the math obvious on the homepage.
- Add a low monthly platform fee so finance has a line to sign off on.
Key takeaways
- Per-seat SaaS framing reads as legacy in W25.
- Outcome pricing maps to budgets line-of-business owners already control.
- Reframe pricing around the unit of work, not the user.