Which of your products should get a feedback widget first?
Give the product with the most revenue at risk, the highest churn risk or the most important launch the first feedback widget. Score each product on revenue, churn risk, launch stage and how easily you can reach its users, add the scores up, and install the widget in the highest-scoring product first.
By Rafael Thayto 路 Published 路 Last updated
What should decide which product gets feedback first?
Four things matter most: how much revenue depends on the product, how likely its customers are to leave, whether it is in a launch that needs fast signals, and how easily you can reach its users. A product that scores high on several of these is the one where a widget earns its keep fastest. The order you install widgets should follow those scores, not the order you built the products or the one you talk about most.
Feedback is only useful if someone reads it. Pick the product where reading it will change a decision this month, and install there first. The other products can follow once the routine for the first one is running smoothly.
How do you build a simple scoring sheet?
A scoring sheet needs one row per product, one column per criterion, and a total. Score each criterion from 1 to 3, where 3 means the strongest case for feedback now. Keep the scale the same for every product so the totals compare fairly.
| Product | Revenue | Churn risk | Launch stage | Reach | Total |
|---|---|---|---|---|---|
| Product A | 3 | 2 | 1 | 3 | 9 |
| Product B | 1 | 1 | 3 | 2 | 7 |
| Product C | 2 | 1 | 1 | 1 | 5 |
These numbers are an example, not a benchmark. Product A has the most revenue at stake and easy reach to its users, so it goes first. Product B is a new launch that needs early signals, so it is a close second and could go first if its launch is this month. Product C can wait.
Equal weights are fine to start. Every criterion counts once, and the sheet stays easy to explain to a teammate. If your business clearly depends on one criterion, such as revenue, you can double that column, but write the reason next to the change so the sheet does not drift into a result you chose in advance.
Revisit the sheet every quarter. Scores move as products grow, as churn signs appear and as launches come and go. Keep the old sheet, so you can see which product moved up and why. A product that stays at the bottom for a year is a useful signal too, because it may be a candidate for less attention or for retirement.
How do you score revenue and churn risk?
Score revenue by asking how much income depends on the product working as expected. A product that brings in most of your billing scores 3, a product with a small paying base scores 2, and a free or experimental product scores 1. Use your own numbers from your own accounts, not estimates from a forum.
Score churn risk by asking how likely a customer is to leave soon. Signs include a rising number of support messages, a recent price or policy change, or a competitor that customers mention. A product with several of those signs scores 3. A product with no sign of trouble scores 1. Churn scoring is a judgment call, so write down the reason for each score in a short sentence. That note is what you will argue with later, and it makes the scores honest.
When does launch stage change the order?
A product in a launch is a special case. Early users form their opinions quickly, and a widget at launch can catch problems that would otherwise surface in reviews weeks later. Score launch stage 3 when a release is within the next month, 2 when the product is in a beta or early access period, and 1 when it has been stable for a long time.
Launch stage can override the total. If a product scores 7 but has a launch next week, and a product scores 9 with a stable release calendar, the launch deserves the widget first, because its feedback arrives in a window that closes quickly. Note the override in your sheet so the reason is visible.
What about a tie, or a product with no users?
A tie is a sign the criteria are too coarse. Break it with reach: install the widget where you can reach users most easily, because you will need to reply, and replies are part of the routine. Only then consider which product you care about most personally, and say so in the notes, so the choice is honest.
A product with no users does not need a widget. Use a hosted feedback page link in its beta invitation instead, which gives you the same inbox without a script on the site. Install the full widget once the product has real traffic and a routine to feed.
Applying the score with Escuta Produto
Once you have the order, add the first product to Escuta Produto with its accent color, origins and webhook. Install the widget there, run the routine for two or three weeks, then add the next product from the top of your sheet. The widget guide covers the snippet and the trigger options, and the hosted feedback page guide covers the link for products that are still in beta.
The scoring sheet and the choice of product are separate questions from how you read the feedback afterwards. Using feedback to choose which product to work on covers how to rank products by what their feedback says, once the widgets are running. Adding a new product to your feedback routine gives the checklist to follow for each product you add to the list.
Frequently asked questions
Which product should get a feedback widget first?
Start with the product that scores highest on revenue at risk, churn risk, launch timing and reach to its users. Install the widget there first, run a weekly routine for two or three weeks, then move down the list in the same order.
Should a product with no paying users get a widget?
Not a full widget yet. Share a hosted feedback page link in beta invitations instead, which collects feedback in the same inbox without a script on the site. Add the widget once the product has real traffic and someone who will read the feedback each week.
What if two products get the same score?
Break the tie by reach, meaning which product's users you can contact and reply to most easily. Then note your own reason in the sheet, so the choice is recorded and you can revisit it when the next scoring round comes around.
Related
- One feedback inbox for many productsWhy one feedback inbox beats a separate tool for each app, how per-product keys keep feedback apart, and what you give up by reading it all in one place.
- A feedback routine for running five productsA weekly feedback routine for five products: a daily count check, one fixed review slot per product, a bugs-first triage order and a list of what to skip.
- Using feedback to choose which product to work onHow to use unique customers, rating direction and revenue fit to pick the product that gets your next week of work, and avoid the loudest-product trap.
- How to organize Slack channels for product feedbackHow to set up Slack or Discord channels for product feedback: one webhook per product, a channel per product or a shared one, and ways to keep alerts quiet.