download dots

💡 Take Feature Requests Without a Spreadsheet

Turn the app you built for yourself into something other people pay to use. These prompts add the parts that make a tool into a product: customer sign-in, plans and trials, limits that mean something, a billing lifecycle that handles the awkward cases, and an admin view so you can see who is actually using it. The unglamorous half nobody enjoys assembling.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Take Feature Requests Without a Spreadsheet

Copy

Feature requests reach me by email, chat and in calls, and I lose most of them. Build me a feature request app. Capture each request with the customer, their plan and value, the request in their words, the date, and the channel it arrived through. Let me merge duplicates into one canonical request, carrying every requester and their weight across so the count is not lost. Score requests by number of requesters, total account value behind them, and whether any requester is at risk of leaving, rather than by raw votes alone. Track a status of Under Review, Planned, In Progress, Shipped or Declined, with a public reason on anything declined. Add an AI agent that reads new requests and suggests which existing request they duplicate even when the wording is completely different, and that summarises the themes across the last quarter. Automate two things: notify every requester when a request they asked for is shipped, and a scheduled monthly summary of the top requests by weighted score. Two logins: a customer who can submit and see status, and an owner who merges, scores and decides.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Take Feature Requests Without a Spreadsheet

Collect feature requests in one place, merge duplicates, weight by account value, and notify requesters when something ships.

// the spark catches · intelligence awakens · the answer unfolds

Feature requests arrive in five channels and are read once. This collects them, merges duplicates, weights by who is asking, and closes the loop when something ships.

What's Included

  • Requests in one place from every channel they arrive through.
  • Duplicates merged with the votes carried across.
  • Weighted by account value not just by count of requests.
  • An assistant that spots the same request in different words.

How To Use

  1. Weight by account value and churn risk, not by raw vote count.
  2. Merge duplicates aggressively or the board becomes unreadable.
  3. Tell people when their request ships. It is the cheapest goodwill available.
  4. Say no clearly. An indefinite maybe is worse than a decline.

Feed it from customer support prompts, and plan the work with product management prompts.