If you run NPS in B2B, the core question should be "How likely are you to recommend {product} to a peer at another company facing the same problem?" Do not reuse the B2C "friends and colleagues" wording. A B2B respondent answers on behalf of their company, so a private "recommend to a friend" frame doesn't match reality. On top of that, in B2B the likelihood to recommend differs sharply depending on whether the respondent is a day-to-day champion or a budget-holding decision-maker — so you pair the rating with a role question and a renewal-intent question. This article focuses only on wording.
For how NPS is calculated and operated overall, see the NPS complete guide; for choosing between NPS and CSAT, see NPS vs CSAT. If that's your intent, go there. Here we dig only into "how to ask in B2B."
B2C wording vs B2B wording
Even for the same NPS, B2B and B2C should be phrased differently.
| Dimension | B2C wording | B2B wording |
|---|---|---|
| Recommend to whom | "friends or colleagues" | "a peer at another company," "another team in your org" |
| Subject | you, personally | your company / your team |
| What is judged | the product / experience | product + ROI + support + contract terms |
| Context | right after purchase / use | the contract period and renewal timing |
| Respondent's stance | uses it for themselves | answers on behalf of the company |
| Companion questions | reason (open text) | reason + role + renewal intent |
The key move is dropping "friend." A B2B buyer can't picture recommending the product to a friend. Replace it with "a peer at another company facing the same problem" and the act of recommending gains real-world, professional meaning.
The core B2B NPS question (recommended wording)
Q1. How likely are you to recommend {product} to a peer
at another company facing the same problem?
(0 to 10. 0 = not at all / 10 = extremely likely)
It's only a swap of "friends or colleagues" for "a peer at another company," but in B2B the quality of answers changes. If you want to measure internal expansion, you can add "another team or department inside your own company."
Reason (open text) — more important than the score
The comment behind the score, not the score itself, is the improvement material. In B2B, push specifically into realized value.
Q2. Why did you give that score?
(What has worked well, or fallen short, since you adopted it?)
(open text)
The role question — the key to reading recommendation intent
This is the B2B-specific point. Within the same account, the day-to-day champion and the budget-watching decision-maker score differently. Champions tend to score high on usability; decision-makers tend to score harshly on ROI and contract terms. Average them without asking role, and the two cancel out into a meaningless number.
Q3. Which best describes your relationship with {product}?
□ Hands-on user / champion who uses it daily
□ Decision-maker / admin who owns adoption or contracts
□ Occasional or view-only user
When you analyze, segment NPS by this role. If "hands-on users have many promoters but decision-makers skew neutral or detractor," that points to a concrete action: the value lands, but the ROI story is weak.
Renewal intent — always pair it with B2B NPS
In B2B, recommendation intent ties directly to revenue through contract renewal. Asking NPS and renewal intent side by side gives you early churn detection.
Q4. Which is closest to your current thinking on renewal?
□ Want to continue
□ Would continue depending on terms
□ Considering switching to another vendor
□ Undecided / not sure
The full B2B NPS question set (English sample)
When you deploy, make Q1–Q4 one set. In one to two minutes and four questions, you capture recommendation intent, reason, role, and renewal intent at once.
| Question | Role | Format |
|---|---|---|
| Q1 Recommendation | The NPS core | 0–10 |
| Q2 Reason | Improvement material (the real body) | Open text |
| Q3 Role | Read champion vs decision-maker | Single choice |
| Q4 Renewal intent | Churn-risk detection | Single choice |
If you want more decision-maker responses, don't leave distribution to the champion. Set up a separate route that sends to decision-makers directly once a quarter, and the role skew shrinks.
How to read responses by respondent type
In B2B, the reading goes a level deeper too.
- Segment NPS by role. Calculate hands-on users and decision-makers separately. Don't average.
- Look at the account level. B2B gets multiple responses from one company. Rather than summing individual votes, summarize the "company-level temperature" per account.
- Cross-reference with renewal intent. A promoter who is also "considering switching" is a sign the champion is happy but the decision-maker is drifting away. Contact them first.
- Classify detractor reasons. Sorting open text into "price," "missing features," "support," and "vendor comparison" makes the next action obvious.
If you specifically want to measure how much effort it took to get the job done, CES (Customer Effort Score) can predict churn better than NPS in some cases. NPS measures overall relationship loyalty; CES measures effort on a specific interaction — different jobs.
FAQ
Q1. What is the right b2b nps question to ask?
Drop "How likely are you to recommend us to a friend or colleague?" Ask "How likely are you to recommend {product} to a peer at another company facing the same problem?" on a 0–10 scale, and pair it with a role question (champion vs decision-maker) and a renewal-intent question.
Q2. How should nps question wording for b2b differ from B2C?
Change the subject and the target from "you, personally, to a friend" to "your company or team, to a peer at another company." Signal that what's judged is not the product alone but the combination of ROI, support, and contract terms — that improves answer accuracy.
Q3. How many questions should a B2B NPS survey template have?
Four is standard: recommendation (0–10), reason (open text), role (single choice), and renewal intent (single choice). It takes one to two minutes and collects everything you need to segment the score and detect churn risk in one pass.
Q4. Can you give a sample B2B NPS survey question?
Core: "How likely are you to recommend {product} to a peer at another company facing the same problem? (0–10)." Follow with reason (open text), role (hands-on user / decision-maker / view-only), and renewal intent (continue / depends on terms / considering switching / undecided). Use the set in this article as-is.
Q5. What do I do when champions and decision-makers score differently?
Don't average. Segment by the role question and read each NPS separately. If hands-on users are high and decision-makers are low, the value lands but the ROI story is weak; if it's the reverse, the contract makes sense but day-to-day usability has issues — and the fix differs in each case.
Deploying B2B NPS with Repoan
Repoan's B2B NPS template ships with the recommendation, reason, role, and renewal-intent set built in. Combine it with the B2B customer satisfaction template to track loyalty and per-interaction satisfaction together. The AI report feature auto-classifies detractor open text into "price / features / support / vendor comparison," so role-segmented analysis and comment reading run at a realistic level of effort.
That said, while you have very few responses (single digits), the NPS number won't be stable. At that stage, we'll say it honestly: you'll learn more from reading the Q2 open text one by one than from chasing the score.
Related articles
- The full calculation and operation picture: NPS complete guide
- Choosing the metric: NPS vs CSAT
- A different metric for effort: The complete guide to CES
- Employee version: eNPS — measuring and improving employee NPS