SaaS Feedback Form Template
A product-market-fit pulse for software teams — the disappointment question, a recommend score with promoter and detractor branches, and the benefit in the user’s own words.
Four questions, no fluff — your answers steer what we build next quarter and what we leave alone.
For a SaaS product, the most valuable feedback question ever devised is not about satisfaction at all — it is "how disappointed would you be if you could no longer use us?". The share answering "very disappointed" is the classic product-market-fit benchmark, with forty percent as the famous threshold, and it belongs at the top of this form because it measures dependence, which is what subscription revenue actually rests on.
Why these fields. The disappointment question and the 0–10 recommend score are both required and deliberately adjacent: disappointment measures whether users need you, recommendation measures whether they will say so out loud, and products routinely score high on one and low on the other — each combination prescribing a different strategy. The main-benefit field, answered in the user's own words, is your positioning department working for free; when "very disappointed" users describe the same benefit in the same words, that is your homepage headline. Role matters because PMF is segment-specific — fit among engineers with none among marketers is focus guidance, not failure. The two branch questions keep the form short for everyone: scores of 6 and below reveal "what's holding back a higher score", 9 and up reveal "what makes it a 9 or 10", and passives in between are respectfully left alone.
What we left out. Feature-satisfaction checklists (a pulse instrument must stay under a minute or the sample skews to superfans), usage-frequency questions (your analytics know), and contact fields — send this to a known user list and identity comes free.
Who uses this. Early-stage teams run it monthly while hunting fit, growth-stage products run it quarterly by cohort, and product managers run it before roadmap planning to weight the loudest requests against the silent middle.
Make it yours. Segment sends by cohort and compare disappointment shares in the CSV export — fit trend by signup quarter is the chart your investors want anyway. Webhook responses into your warehouse to join against usage data. Keep the wording stable across runs; the value of a pulse is the delta, and rewritten questions reset the series.
Mine the middle. The "somewhat disappointed" group is where the growth work lives. Very-disappointed users already need you; not-disappointed users were probably never yours to keep; the middle chose you and remains unconvinced, which makes their answers the cheapest expansion market you own. Compare their main-benefit wording against the very-disappointed group's: when the middle names a shallower version of the same benefit, the product is underdelivering its own promise to them, and when they name a different benefit entirely, they are using you for a side job — either build that job out or accept the segment as passing traffic. Role answers anchor the read, showing whether your middle is a stage of adoption or simply the wrong audience.
Frequently asked questions
What is a good "very disappointed" percentage?
The traditional benchmark is forty percent of respondents — below it, fix retention before growth. Compute it from the CSV export: very-disappointed answers over total responses.
Why do promoters and detractors see different questions?
Two Logic rules branch on the recommend score — 6 and below asks what is holding it back, 9 and above asks what makes it great. Both thresholds are editable in the Logic panel.
How often can we send this without fatigue?
Quarterly for a stable base, monthly during heavy iteration — but sample different user slices each time rather than blasting everyone repeatedly.
Can responses flow into our data stack?
Yes — a webhook delivers each response as signed JSON in real time, and CSV export covers batch pulls into your warehouse or spreadsheet models.