with the skill
# Recommendation: start with reconciling bank feeds
I scored each problem with the Opportunity Score, Importance × (1 − Satisfaction), after normalizing the 1-10 ratings to 0-1 by dividing by 10.
| Rank | Problem | Importance | Satisfaction | Opportunity Score |
|---|---|---|---|---|
| 1 | **Reconciling bank feeds** | 0.92 | 0.34 | **0.61** |
| 2 | **Sending payment reminders** | 0.70 | 0.30 | **0.49** |
| 3 | Exporting data for accountant | 0.75 | 0.50 | 0.38 |
| 4 | Custom invoice themes | 0.31 | 0.20 | 0.25 |
| 5 | Finding past invoices | 0.89 | 0.86 | 0.12 |
## Reading the results
- **Bank feed reconciliation** is the top opportunity. It has the highest importance of any problem and low satisfaction, so it sits in the upper-left "sweet spot" of the Importance vs Satisfaction chart.
- **Payment reminders** come second. They matter less than reconciliation, but current solutions are about as poor.
- **Accountant export** is a solid third, with moderate importance and mediocre satisfaction.
- **Finding past invoices** is important but already well served (0.89 importance, 0.86 satisfaction). It has little room to create value, so don't invest further.
- **Custom invoice themes** rank low because customers rate them as unimportant (3.1/10). Satisfaction is also low, but that doesn't matter much when the problem isn't important to them.
Show the rest (16 more lines)
## On the sales note
Fourteen requests is about 7% of your 200 surveyed customers. It's a signal worth noting, but it is a request for a solution (themes), not a validated problem. The survey shows the broader base doesn't rate the underlying need as important. Before dismissing it, check two things:
- Are those 14 customers disproportionately high-value, or a distinct segment such as agencies or brands that care about presentation? Averages can hide segments.
- What problem are they trying to solve (professional look, brand consistency, winning clients)? That may be addressable more cheaply than with full theming.
## Caveats and next steps
1. **Averages hide variance.** If you have the raw responses, check the distributions and segment by customer type. A problem with a polarized rating can rank differently.
2. **This ranks problems, not solutions.** The next step is to generate solution options for bank feeds and reminders, then compare them with ICE or RICE. For that you'd need:
- Reach: how many customers are affected
- Confidence in each solution
- Effort estimates from engineering
3. **Effort could change the order.** If reminders is a quick win and bank feed reconciliation is a multi-quarter build, you might ship reminders first while starting discovery on reconciliation. Opportunity Score alone doesn't account for that.
If you share reach and effort estimates, I can run a RICE comparison.