B2C vs B2B: the two ways to sell, and how to choose

Every product you have ever paid for sits on one side of a line. Either a company sold it to you as a person (B2C), or it sold it to a company (B2B). Netflix, your coffee shop, and a mobile game are B2C. Salesforce, AWS, and your payroll software are B2B. The line looks small, but it quietly decides almost everything about how a product is built, priced, marketed, and supported.

I have spent a lot of time on the product side of software, and the single mistake I see most often is building a great thing and then selling it the wrong way, because the founder never decided which of these two games they were actually playing. They are different games. The rules that win one will lose the other.

This post takes you from zero to a working mental model of both. By the end you will be able to look at any product and reason about why it is sold the way it is, and, more importantly, decide which model fits something you want to build. If you want the structured reference versions, I keep them in the wiki: B2C and B2B. This is the narrative tour.

Start with one question: who decides?

Forget acronyms for a second. The thing that actually separates these two models is a single question: who makes the decision to buy, and how?

In B2C, one person decides. They spend their own money, usually in seconds, and usually on feeling. Bored, so they download a game. Tired of cooking, so they try a meal kit. They like the shoes. The buyer and the user are the same person, and nobody needs to approve anything.

In B2B, an organization decides. The purchase has to produce a business result that justifies its cost, and several people are involved: the person who will use it, the person who pays for it, and often a few people whose job is to find reasons to say no. The buyer and the user are frequently different people, and the decision takes weeks or months.

Almost every other difference flows from that one fact. Hold onto it, because it explains the rest.

The differences, side by side

Here is the contrast in one place. Read it as cause and effect, not trivia: each row is downstream of “who decides.”

The shortest way to remember it: B2C wins on volume and simplicity; B2B wins on contract size and depth. A B2C company needs millions of small, fast, emotional decisions to go its way. A B2B company needs a much smaller number of large, slow, rational decisions to go its way. Those are different muscles.

Why B2C lives and dies on friction and emotion

Because each B2C customer is worth very little, the entire model only works at scale. You cannot afford a salesperson to win a customer worth twelve dollars a year. So everything has to be self-serve, and two forces dominate: emotion gets people in, and friction pushes them back out.

Emotion is the hook. People buy consumer products because of how they expect to feel: status, relief, fun, belonging, identity. A spec sheet does not sell a consumer app; a feeling does.

Friction is the silent killer. Every extra step between a person and the value they came for leaks customers. A confusing signup, a forced account before they can try anything, a slow page, a surprise paywall. I have watched conversion rates double from nothing more than removing form fields. In B2C, friction is not an annoyance, it is lost revenue.

You can see this in how consumer decisions actually move, the classic funnel:

flowchart TB
Awareness["Awareness, an ad, a friend, a search"] --> Interest["Interest"]
Interest --> Consideration["Consideration, compared to alternatives"]
Consideration --> Conversion["Conversion, sign up, download, buy"]
Conversion --> Retention["Retention, keep using and paying"]
Retention --> Advocacy["Advocacy, tells a friend"]
Advocacy --> Awareness

The job in B2C is to widen the top of that funnel and shrink the leaks, then turn the bottom (advocacy) back into the top through word of mouth. When that loop spins on its own, growth gets cheap.

Why B2B lives and dies on the buying committee

B2B has no single buyer to charm. It has a committee, and the deal dies if you ignore any member of it. This is the concept that takes newcomers the longest to internalize, so it is worth naming the roles:

• User, the person who will actually use it. Cares whether it makes their work easier.
• Champion, your internal advocate. Sells for you when you are not in the room.
• Economic buyer, controls the budget. Cares about return on investment, not features.
• Decision maker, signs off, sometimes a more senior executive.
• Blockers, legal, security, finance, procurement, IT. Their job is to find risk.

The classic failure is winning the user and losing the deal. Your champion loves the product, the team is excited, and then security flags a data concern or finance will not approve the spend, and it all stalls. In B2B, the product is necessary but not sufficient. You are not selling software; you are helping a champion build an internal case strong enough to survive a committee.

That is why the sales cycle is long, and why it justifies real human effort. A B2B sale typically walks through stages like this:

flowchart LR
Prospect["Prospecting"] --> Qualify["Qualification"]
Qualify --> Discovery["Discovery"]
Discovery --> Demo["Demo"]
Demo --> Proposal["Proposal"]
Proposal --> Negotiate["Negotiation"]
Negotiate --> Procure["Procurement & legal"]
Procure --> Close["Close"]
Close --> Expand["Onboard & expand"]

Every one of those stages can stall a deal for weeks. The upside is that when it closes, a single customer can be worth more than thousands of consumer signups, and they tend to stay for years.

How each one makes money

The business model, meaning how the money actually arrives, looks different on each side.

On the B2C side you will see one-time purchases, subscriptions (Netflix, Spotify), freemium where a free tier feeds a small paying minority, advertising where the user’s attention is the product and the advertiser is the real customer, in-app purchases and microtransactions (mobile games live here), and marketplaces that take a cut of each transaction. Big consumer companies usually blend several at once: a free ad-supported tier, a paid subscription, and in-app purchases all together.

On the B2B side the dominant model is the annual subscription (SaaS), often priced per seat or by usage (API calls, compute, storage), packaged into tiers like Starter, Pro, and Enterprise, and frequently sold alongside implementation and support services. The biggest accounts get custom pricing. The reason annual recurring revenue rules B2B is simple: it is predictable, it compounds, and it is what investors and operators use to judge the health of the whole business.

If you want to go deeper on choosing a model and a number, I wrote that up separately in Pricing your first product.

The economics: the numbers that decide everything

Both models, underneath, obey the same law: you must make more from a customer than it costs to win and keep them. Two numbers capture it.

• CAC (Customer Acquisition Cost), what you spend on average to win one customer.
• LTV (Lifetime Value), the total profit you expect from that customer over the whole relationship.

The ratio between them is the heartbeat of the business:

LTV / CAC ratio
  < 1   You lose money on every customer. Unsustainable.
  ~ 1   You break even but cannot grow profitably.
  ~ 3   A common healthy target: earn about 3x what acquisition costs.
  > 5   Strong economics, or maybe you are underspending on growth.

The same law, two very different shapes. In B2C, CAC is small (an ad click) but so is LTV, so you survive by getting CAC low through scalable channels and pushing LTV up through retention and repeat use. In B2B, CAC is large (salaries, months of selling) but LTV is also large (big contracts, multi-year relationships), and people also watch the CAC payback period, how many months of revenue it takes to earn the acquisition cost back. Under roughly a year is healthy.

There is one more metric I want you to know because it is the truest signal of B2B health: Net Revenue Retention (NRR). It compares this year’s revenue from existing customers to last year’s, including upgrades, downgrades, and churn. Above 100% means your existing customers spend more over time even before you win a single new logo. A B2B company with high NRR grows almost by itself. The B2C equivalent obsession is retention and the churn rate, because a leaky bucket makes every dollar of acquisition pointless.

The lesson on both sides is the same and it is the one beginners get backwards: retention comes first, then monetization, then acquisition. Pouring traffic or sales into a product people abandon just makes you lose money faster.

How they reach people

Because B2C needs huge volume, it reaches people through anything that scales: paid ads, organic social and content, SEO, app store optimization, influencers, and the holy grail, word of mouth. Because B2B needs the right organizations and the right people inside them, it uses outbound sales, content and SEO that catch buyers researching a problem, account-based marketing aimed at a named list of target companies, events, partnerships and integrations, and referrals backed by case studies that de-risk the next buyer’s decision.

A newer pattern blurs the line: product-led growth (PLG), where a B2B product is adopted bottom-up by individual users on a free tier (think a tool that one developer starts using, then a whole team, then the company buys). It uses B2C-style self-serve mechanics to land inside a company, then a B2B-style sales motion to expand. Slack and many modern dev tools grew this way. It is worth knowing because it shows the two models are ends of a spectrum, not a rigid binary.

How to choose, if you are building something

This is the part that actually matters when it is your product. Most ideas can technically be aimed either way, and the choice shapes the company you will build for years. Work through these questions honestly:

1. Who feels the pain, and whose money solves it? If it is the same person, you are leaning B2C. If the user and the payer differ, you are leaning B2B.
2. How big is one customer worth? Tiny means you need volume and self-serve (B2C). Large means you can afford a sales process (B2B).
3. How fast and emotional is the decision? Seconds and feelings point to B2C. Weeks and spreadsheets point to B2B.
4. Can you reach enough of them affordably? B2C needs a cheap, scalable channel. B2B needs access to specific organizations and the people inside them.
5. What does retention look like? B2C must build habit. B2B must deliver measurable ROI and become embedded enough that leaving is risky.

A blunt heuristic: if you would need millions of customers to build a real business, you are signing up for the B2C game of volume, brand, and friction-free design. If a few hundred customers paying real money would do it, you are signing up for the B2B game of committees, ROI, and relationships. Neither is easier. They are just different, and the worst outcome is running one playbook on the other model.

Whichever side you land on, the discipline before you write code is the same: test the riskiest assumption cheaply before you bet months on it. I covered exactly how to do that in Validating a SaaS idea, including the B2B-specific move of getting a letter of intent from someone who actually controls the budget.

The acronyms are trivial. The mental model behind them, who decides and how, is one of the most useful lenses you can carry into building anything.