Markets and business models
Customer segment economics
Consumer, SMB, mid-market and enterprise buyers change CAC, churn, sales cycle and org design inside the same model.
The label "SaaS" hides different machines. A $5/month app and a $2M annual platform can both bill as subscriptions and still be different careers. The buyer — a person with a phone, a small-business owner, or a procurement committee — sets the cycle time, the cost to acquire and the chance they stay.
Concept
ACV is annual contract value: what one customer pays in a year. CAC is the cost to acquire that customer. Logo churn is the share of customers who leave, counted as accounts rather than dollars. See unit economics.
Walking through the four bands
| Segment | Typical ACV | Sales cycle | Churn shape | What you build |
|---|---|---|---|---|
| Consumer | dollars to tens of dollars | self-serve | high; habit or ads | viral loops, store billing, cheap CAC |
| SMB | hundreds to low tens of thousands | self-serve or light touch | higher logo churn | onboarding, dunning, simple admin |
| Mid-market | tens to low hundreds of thousands | product-led plus sales-assisted | mixed | onboarding, SSO starts to matter |
| Enterprise | hundreds of thousands to millions | 3–18 months | low logo churn | security, custom terms, solutions engineering |
Consumer revenue is easy to count and hard to keep. CAC is often paid media or a viral loop. App stores take roughly 15–30% of digital goods. You need efficient acquisition or ads at huge scale. See consumer economics.
SMB is faster: card-on-file, short cycles, ACV that rarely pays for a field salesperson. Logo churn is higher because switching is cheap and companies die.
Enterprise revenue is "better" per logo and expensive to get. Security reviews, custom terms and a 3–18 month cycle mean heavy S&M and solutions engineering. Once in, logo churn is low — ripping you out is a program.
The model must match the buyer's budget process. A consumer pays from a card. An IT buyer pays from an annual software budget. A marketplace seller pays from a COGS line. Wrong buyer, wrong motion.
A $100k example
Suppose you sell a $10k ACV tool with a 45-day self-serve-plus-email cycle, and 18% annual logo churn. One salesperson with light assist can close many deals. Now the same product is packaged at $250k ACV for a bank. Cycle time becomes 9 months, you need security questionnaires and a solutions engineer, and you might close four deals a year. That is a different company — support load, product surface and org chart all change — even though both are "B2B SaaS."
Common mistakes
- Hiring enterprise AEs for SMB ACV. The math cannot pay for the human.
- Building consumer acquisition for a product that only buys like an elephant. You will get signups that never clear procurement.
- Treating mid-market like enterprise. You add cycle time without adding ACV.
Check yourself
Why can enterprise revenue look "better" and still be a worse first motion?
Low logo churn and high ACV arrive after a long, expensive cycle. Early teams often cannot fund 3–18 months of selling.
A $5/month app and a $2M ACV platform both use TypeScript. What actually differs?
Buyer, ACV, CAC, cycle time, churn and what engineering must build (store billing versus SSO and audit logs).
Key takeaways
- Segment (consumer → enterprise) changes CAC, churn, cycle time and org design inside the same model family.
- Enterprise is better per logo and slower to get. Consumer is easy to count and hard to keep.
- Match the model to how the buyer budgets — card, IT budget, or COGS line.
- Pick the segment your distribution can actually win.
Further learning
Next, how customer count and ACV multiply to $100M in five ways to $100M ARR.