From a one-off score to a system that moves it
How to Build an NPS Program
A survey gives you a number. A program gives you a system that lifts the number over time.
An NPS program is the cadence, segmentation, routing, and closed loop around the score, not just the survey. Here is how to design and run one end to end, with every response linked to a real user.
An NPS survey is not an NPS program
Most teams run a survey, read the number, and stop. The program is everything that turns that number into retention.
A one-off survey
- ×Sent once or sporadically when someone remembers
- ×Produces a single number with no trend
- ×Responses sit in a spreadsheet, unrouted
- ×Detractors are never followed up
- ×Nobody owns the score or the actions
An NPS program
- ✓Relational and transactional surveys on a fixed cadence
- ✓Tracks the trend, segmented by plan, role, and cohort
- ✓Low scores routed to the right team in real time
- ✓Every detractor followed up inside the recovery window
- ✓A clear owner, a target, and a closed feedback loop
How to build an NPS program in 7 steps
A repeatable system you can stand up in a week and run indefinitely.
Pick an owner and a target
A program without an owner drifts. Assign one person accountable for the score and the actions behind it, usually in product or CS. Set a target based on your stage and segment, not a generic +50. Early-stage SaaS lands +20 to +45; use your own first reading as the baseline and aim to improve it quarter over quarter.
Choose relational and transactional NPS
Relational NPS runs quarterly and measures the overall relationship. Transactional NPS fires after key events (onboarding, a milestone, a renewal) and measures a specific moment. A complete program runs both: the relational trend tells you where you stand, the transactional signal tells you what moved it.
Trigger in-product, not over email
Email NPS gets 5 to 15% response rates and a sentiment-skewed sample. In-product surveys triggered on behaviour get 20 to 40% and a representative one. Fire the relational survey on a login after the cadence window opens, and the transactional survey on the event itself, so the answer is fresh and the sample is real.
Segment every score from day one
An overall NPS of +35 can hide an enterprise NPS of +5 that represents most of your revenue. Link every response to the user and their attributes so you can break the score down by plan tier, role, tenure, and cohort. The segment view is where the program becomes actionable; the overall number rarely is.
Route low scores in real time
A detractor is recoverable for a short window after they respond. Send every detractor (0 to 6) straight to the owner the moment they submit, with their identity and context attached, so follow-up happens within 48 hours. Routing is the single highest-ROI part of the program and the part most teams skip.
Close the loop and tell people
When feedback drives a fix, tell the customers who flagged it. Closing the loop publicly lifts the next round of scores across the whole base, not just the people who complained, and it teaches users that answering is worth their time. An unclosed loop trains your base to stop responding.
Review the trend on a cadence
Put the segmented NPS trend in front of the team every month. Watch for a drop of more than 10 points in any segment, investigate the open-ended responses behind it, and tie program changes to score movement. The number only matters as a trend you act on, not a snapshot you report.
Relational vs transactional NPS
The two halves of a program. Each answers a different question and runs on a different trigger.
Relational NPS
Transactional NPS
Suppress any user who responded in the last 30 to 90 days so the two streams do not fatigue the same people.
A sample NPS program cadence
One way to sequence the surveys across the customer lifecycle without over-surveying anyone.
Day 30
TransactionalFirst NPS after onboarding completes. Sets the earliest read on whether the product landed, segmented by plan and role.
Quarterly
RelationalThe recurring relationship survey for all active users. This is the trend line the program is built around.
After a milestone
TransactionalFire after a meaningful success event (first value, a power-feature adoption). Captures NPS at the peak of the experience.
60 days pre-renewal
TransactionalAn NPS read before the renewal decision, so detractors can be recovered while there is still time to act.
On every detractor
RoutingNot a survey but the most important step: route each 0 to 6 to the owner in real time for 48-hour follow-up.
Why most NPS programs stall
The patterns that turn a promising program into a number nobody trusts.
Anonymous responses
If you cannot tell who gave a score, you cannot follow up, segment, or close the loop. Anonymous NPS is a vanity number. Link every response to the user from the start.
Reporting the number, not acting on it
A score that goes into a slide and nowhere else changes nothing. The program lives or dies on routing and follow-up, not on the dashboard. If no action follows a low score, stop running it.
One overall number, no segments
An unsegmented NPS hides the segment that is actually churning. The program's value is in the breakdown by plan, role, and cohort, not the headline figure.
Survey fatigue
Running too many surveys at too many users trains your base to ignore you. Suppress recent responders for 30 to 90 days and keep each survey to the core question plus one follow-up.
Changing the question or scale
Rewording the question or switching the scale breaks comparability with your own history and with benchmarks. Lock the standard 0 to 10 wording and never touch it.
No owner
A program that belongs to everyone belongs to no one. Without a single accountable owner, the cadence slips, follow-up stops, and the score quietly dies.
Frequently asked questions
What is an NPS program?+
An NPS program is the full system around the Net Promoter Score, not just the survey. It includes a cadence of relational and transactional surveys, segmentation of every score by user attributes, real-time routing of low scores to an owner, a closed feedback loop, and a regular review of the trend. The survey produces a number; the program is what turns that number into retention.
What is the difference between relational and transactional NPS?+
Relational NPS runs quarterly and measures the overall customer relationship, giving you a trend line. Transactional NPS fires after a specific event, such as onboarding completion or a renewal, and measures that moment. A complete NPS program runs both: the relational survey tells you where you stand, and the transactional survey tells you what moved it.
How often should I run NPS surveys in a program?+
Run relational NPS quarterly (every 90 days) for all active users, and run transactional NPS continuously, triggered on key events. Suppress any user who responded in the last 30 to 90 days to avoid survey fatigue. The goal is enough signal to track a trend without training your base to ignore the surveys.
Who should own the NPS program?+
One accountable person, usually in product or customer success, should own the score and the actions behind it. A program without a single owner drifts: the cadence slips, low scores go unrouted, and follow-up stops. The owner sets the target, reviews the trend, and makes sure the loop gets closed.
How do I improve my NPS over time?+
Improvement comes from the program, not the survey. Route every detractor to follow-up within 48 hours, segment the score to find the at-risk group, fix the root causes the open-ended responses reveal (onboarding is usually the highest-leverage one), and close the loop publicly so the next round of scores rises across the whole base. Track the segmented trend monthly and tie changes to movement.
Can I run an NPS program in a spreadsheet or Google Forms?+
You can start one in Google Forms for your first batch of responses, but it breaks at scale. A spreadsheet cannot trigger surveys on behaviour, link responses to users for segmentation, or route detractors in real time, which are the parts of the program that actually move the score. Most teams graduate to a dedicated tool once they want segmentation and routing.