Wishlist

Let's build a prioritization framework. Here's what works for a 300-request backlog:

Step 1 — Categorize and deduplicate: Many of your 300 requests are probably duplicates or variations. Group them by theme:

• UI/UX improvements
• New features
• Integrations
• Performance
• Mobile

You'll likely end up with 80-100 unique requests.

Step 2 — Score each request (RICE framework):

1. Reach — how many users/accounts request this per quarter? (1-10)
2. Impact — how much will this improve their experience? (0.25 = minimal, 3 = massive)
3. Confidence — how sure are you about reach and impact? (50%-100%)
4. Effort — engineering weeks to build (lower = better)

Score = (Reach x Impact x Confidence) / Effort

Step 3 — Add business context:

• Is this blocking a deal? Tag with deal size.
• Is this causing churn? Tag with churn risk.
• Is a competitor shipping this? Tag with competitive pressure.

Step 4 — Build a living dashboard:

• Top 10 by RICE score
• Top 5 deal-blockers
• Top 5 churn risks
• Review monthly with product + engineering leads

Quick win: Start by finding requests mentioned by 10+ users — those are your highest-confidence bets.

Share your backlog (even a CSV) and I'll categorize, deduplicate, and score the top 50.

Don't panic-build. Here's a structured approach:

Step 1 — Validate the threat:

• Is this a real churn risk or a negotiation tactic? Check: are they in an annual contract (when does it renew)? Have they evaluated competitors?
• How much revenue is at stake? If it's your largest customer, it demands attention. If it's 2% of revenue, the urgency is lower.
• Have other customers requested the same feature? If yes, it's strategic. If no, it might be a one-off customization.

Step 2 — Understand the real need: The requested feature is their proposed solution. The underlying problem might be solvable differently.

• Ask: "What workflow are you trying to accomplish? Walk me through what you do today."
• Often there's a workaround, configuration change, or simpler feature that addresses 80% of the need.

Step 3 — Decision framework:

Build it if:

• Multiple customers want it (validates demand)
• It aligns with your product roadmap
• The effort is reasonable (< 2 weeks)
• The customer represents strategic value (reference, brand, market segment)

Don't build it if:

• It's a one-off customization that adds maintenance burden
• It conflicts with your product vision
• The customer is likely to churn anyway (check other health signals)

Step 4 — Respond to the customer: "We've prioritized this based on your feedback. Here's our timeline: [specific date]. In the meantime, here's a workaround that covers the core need."

A specific date, even if it's 6 weeks out, is better than a vague "we'll look into it."