A B2B MVP is validated by five paying design partners, not by sign-ups, and it needs things a consumer MVP can skip: user roles and permissions, an admin view for the customer, audit trails, data export and enough security to pass a questionnaire. A B2C MVP is validated by activation and retention across hundreds of users and lives or dies on its first session. The build cost is similar. The scoping, the measurement and the sales motion are different, and treating one like the other is a common reason MVPs fail.
Most MVP advice is written for consumer products, and founders selling to businesses follow it into trouble. They optimise onboarding for a user who will never self-serve, chase sign-ups from companies that will never buy without a call, and launch without the admin and permissions features that every buyer asks about in the first meeting. This post sets out what changes when your customer is a company, and what stays the same.
What does validation look like for each?
| B2C MVP | B2B MVP | |
|---|---|---|
| Proof of demand | Hundreds of users activate and a healthy share retain | Three to five companies pay, or sign a pilot with a price attached |
| Who uses it | The person who chose it | Often not the person who bought it, and several roles at once |
| Who decides | The user, in minutes | A buyer, a user, IT, sometimes legal and procurement, over weeks |
| First session | Must deliver value alone, unguided | Usually a guided setup with you on the call |
| Key metric at 90 days | Week-four retention | Pilots converted to paid, and weekly active seats per account |
| What kills it | A bad first session | A missing feature the buyer's process requires, or failing the security review |
What does a B2B MVP need that a B2C MVP can skip?
- Roles and permissions. An owner, an admin and a member at minimum. The buyer will ask in the first demo.
- A customer-side admin view. Someone at the customer needs to add users, see usage and remove a leaver. If they have to email you, the pilot will not scale.
- Data export. Buyers want to know they can leave. A CSV export is enough and removes an objection.
- An audit trail for important actions. Who changed what, when. Needed for anything financial or compliance-adjacent, and asked about far more often than you expect.
- Enough security to pass a questionnaire. Encryption in transit and at rest, single sign-on or at least strong passwords, a written answer to where the data lives. Our post on building software for regulated industries covers what the questionnaire asks.
- Invoicing, not only card payment. Companies pay on invoice. Build for it or process the first ones by hand, but have a plan.
What a B2B MVP can skip: polished self-serve onboarding, since you will onboard the first customers personally; a mobile app, unless the job happens away from a desk; social features; and most of the consumer growth machinery.
What does a B2C MVP need that a B2B MVP can skip?
- A first session that delivers value in under two minutes, with no one to help. This is the whole product for a consumer MVP, and it is why design takes longer than founders expect.
- Frictionless sign-up. Social login, no credit card, no form longer than it has to be.
- Analytics on every step of the first session. You cannot interview hundreds of people. The funnel is the interview.
- A reason to come back, built in: a notification, a streak, new content, a reminder tied to the job.
- Store presence, if mobile. Listing, screenshots and the review cycle. See app store optimisation basics.
How do design partners work?
Design partners are the B2B equivalent of beta users, with one difference: they pay, or they commit to pay at a stated price when the pilot ends. Three to five is the right number. Fewer and you are building for one customer. More and you cannot serve them properly with a small team. Choose companies that have the problem acutely, have someone senior who wants it solved, and are typical of the market rather than the largest logo you can reach. A pilot with a large enterprise is slow, demands bespoke work and teaches you little about the mid-market you will actually sell to.
Agree in writing: the problem the pilot tests, the success criteria, the price at the end, the pilot length, and who on their side owns it. Then onboard them yourself, sit with their users, and ship fixes weekly. The MVP is finished when the design partners convert.
What changes in the sales motion?
Consumer products are discovered. Business products are sold, at least at first. The founder sells the first ten accounts personally, and the MVP exists to support those conversations: a demo environment with realistic data, a one-page security answer, and a clear price. The landing page matters less than the deck and the demo. A B2B founder who spends the MVP budget on self-serve growth features has bought a consumer product for a business market. Getting your first 100 users covers both motions.
Scoping rules
- B2B: roles, admin, export, audit, security answer, invoice. Skip self-serve polish and mobile.
- B2C: two-minute first session, frictionless sign-up, funnel analytics, a reason to return. Skip roles and admin beyond your own.
- Both: one core journey, one platform, measured from day one.
How 7L scopes each
The first question in discovery is who pays and who uses, because the answer sets half the scope. For B2B MVPs we build the account model, permissions and export into the first release as standard, and we help founders write the design partner agreement. For B2C we spend proportionally more on design and the first session, and wire the funnel before any feature. If you are not sure which side your product is on, which happens more often than you would think, describe who pays and who uses and we will tell you what that implies.
Frequently asked questions
Can an MVP serve both businesses and consumers?
It can be used by both, but it should be scoped for one. A product used by individuals and sold to their employers is B2B for scoping purposes, since the buyer's requirements decide whether it ships. Pick the paying side and build for it first.
How many design partners should a B2B MVP have?
Three to five. Enough that you are not building for one company's quirks, few enough that you can onboard and support them personally. They should pay, or agree a price for when the pilot ends.
Does a B2B MVP need single sign-on?
Not for the first customers unless they are large enterprises. Strong passwords and two-factor authentication pass most questionnaires for small and mid-sized buyers. Plan for single sign-on in version two if your market is enterprise, and say so when asked.
How long does a B2B pilot take?
Six to twelve weeks is typical. Shorter and the customer has not changed their process enough to judge. Longer and the pilot drifts without a decision. Agree the length and the success criteria before it starts.
Is a B2B MVP more expensive to build than a B2C MVP?
Roughly the same. B2B adds roles, admin and export, and B2C adds design and onboarding work. Both land in the same cost bands. Our post on how much MVP development costs has the figures.