Can a prompt replace Savio?

Build a feature-request tracker that ranks by revenue rather than by votes.

Three tables: accounts (name, monthly revenue, plan, renewal date), requests (title, description, status), and asks (which account asked for which request, when, and a link to where it was said). The ask table is the whole design — a request is not an object with a vote count, it is a set of asks from named accounts.

Rank by revenue at stake: the sum of monthly revenue across the accounts that asked. Show alongside it the raw account count and the largest single account's share, because one big customer and fifteen small ones produce the same total and mean entirely different things about the product.

Ingest deliberately generically: one webhook endpoint that takes a title, a body, an account identifier and a source URL. Then write thin adapters — a Zapier or n8n workflow, an email address, a bookmarklet — that post to it. Adapters to specific vendors are what rot; a stable inbound contract with disposable adapters in front of it is what survives.

Sync accounts and revenue from one source you already have — Stripe is the honest choice for most people, since it is where the money actually is — on a nightly job. Store the fetch date next to the figure and show it in the interface, because stale revenue silently produces a confidently wrong ranking, which is the specific failure this tool invites.

Give each account a page listing everything it has ever asked for and the status of each, so a renewal conversation can be prepared in thirty seconds.

Out of scope: vendor-specific connectors, a public voting board, a browser extension, and any notification back to end customers.