Feature Request Board.
Collect requests with votes, status, and effort, then show customers what shipped.
About this template
A board of customer feature requests with vote counts, status, and an effort estimate on every card. Requests move from new through planned, in progress, and shipped, and a running shipped log shows customers exactly what you delivered. Filter by customer segment or effort to pick next quarter's roadmap in one meeting.
The live demo ships with sample data: About 70 requests for a fictional B2B app spread across new, planned, in progress, and shipped statuses, with vote counts from 1 to 40, effort sizes, requesting customer segments, and a shipped log covering two quarters.
The prompt behind this template
This is the exact description the Prized agent built it from. Yours can be one sentence: the agent fills in the rest, and you refine from there.
Show the full prompt
Build a feature request board for the product team at Slatebridge, a fictional B2B procurement platform serving SMB, mid-market, and enterprise customers. Layout: a slim header strip with four inline stats: open requests (50), total votes (about 640), shipped last quarter (11), in progress right now (8). Below it a view toggle between Board and Shipped log, with Board the default. The Board is a four column kanban: New, Planned, In Progress, Shipped (this column shows only the 5 most recent, with a link to the Shipped log). Each card carries the request title, a vote count pill, an effort badge (S, M, L, XL), a segment badge (SMB, Mid-market, Enterprise), and how long ago it was filed. Cards sort by votes descending within each column. Above the board: a segment filter, an effort filter, and a text search. Members see a vote button on each card that adds one vote, a stage menu on each card to move it forward, and a New request button that opens a side panel form capturing title, a one paragraph description, segment, and effort. Visitors see none of these and the board must read perfectly without them. The Shipped log is a chronological list covering the last two quarters, grouped by month: title, ship date, effort, votes at ship time, and a one line customer facing note describing what it does. Data to seed: about 70 requests total with believable B2B titles (Approval workflow API, Bulk PO import, Custom fields on vendors, SSO via SAML, Slack notifications for approvals), spread roughly 30 in New, 12 in Planned, 8 in In Progress, and 20 in Shipped across the last two quarters, exactly 11 of them inside the most recent quarter. Votes range 1 to 40, weighted so most requests sit under 10. Plant this story: the single highest voted request, Approval workflow API at 40 votes from Enterprise, still sits at the top of the New column while several requests with fewer than 5 votes have already shipped, an obvious prioritization miss a visitor should spot in ten seconds. Behavior: header stats compute from the cards. Effort badges use one muted color family, segment badges a second, and vote pills stay high contrast. Empty filter results show a friendly zero state. Visual identity: a forest green accent on a paper-white base for vote pills, primary buttons, the Shipped column header, and active filters, giving the board a calm roadmap-review feel.
More like this
All templatesSaaS MRR Dashboard
Track MRR, new business, expansion, contraction, and churn in one revenue view.
Customer Churn Tracker
Log every cancellation with reason and MRR lost, then see what is actually driving churn.
User Engagement Dashboard
Daily and monthly active users, stickiness, and retention curves for a consumer app.
