01 / PLANNED
Retain the original problem
Planned request records would separate the customer wording, desired outcome, and current workaround.
Product feedback · Early research
See the request behind the vote.
A planned feedback triage workspace for small B2B products: preserve customer context, review duplicate requests, and record product decisions. Join the research waitlist.
Get early access ↗In research · Join the waitlist · No payment required
Designed around founders and product teams reviewing customer requests from support and sales.
Concept preview · fictional example
| Request | Underlying need | Decision |
|---|---|---|
| Export history | Audit a past change | Explore |
| Team folders | Separate client work | Clarify workflow |
| Mobile widget | Review alerts on the go | Deferred |
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION
Two customers can vote for the same label while needing different outcomes. A popularity count does not explain the workflow, the workaround, or the decision your team already made.
THE PRODUCT WE’RE EXPLORING
RequestLedger, in three parts.
RequestLedger would group requests without discarding the original customer problem. A reviewer would confirm duplicates and leave a decision note that can be revisited later.
Three planned capabilities we want to validate with early users.
02 / PLANNED
Review duplicate suggestions
Proposed grouping would let a person merge related requests while preserving distinct use cases.
03 / PLANNED
Make the decision visible
Planned decision notes would record why an idea is being explored, deferred, or declined without promising delivery.
AN INTENDED WORKFLOW
A clearer next step.
Less work around it.
A focused approach for founders and product teams reviewing customer requests from support and sales.
- 01
Bring a permitted request
A pilot would begin with redacted request text and source links your team is allowed to process.
- 02
Compare the underlying need
Review suggested groups and keep separate requests separate when their workflows differ.
- 03
Record the next decision
Assign an owner and a review date, then export an approved response to your existing support workflow.
HELP SHAPE THE FIRST VERSION
A better workflow starts with your experience.
Join the RequestLedger waitlist for early-access updates and an optional research conversation.
This product is in research. Planned features and integrations are not available yet.
NO PAYMENT · NO COMMITTED LAUNCH DATEYOU’RE ON THE LIST
Thanks for raising your hand.
Your signup has been received for RequestLedger. There is no confirmation email to look out for.
Manage your data ↗GOOD TO KNOW
A few useful answers.
Is a voting board available now?
No. This is an early research waitlist. Request imports, voting, grouping, and decision records are not available yet.
Does a vote promise that a feature will ship?
No. The proposed product would treat votes as one signal. Product teams would keep ownership of prioritization and any customer commitments.
Which support tools will connect?
No integrations are confirmed. We would start with a narrow import workflow and select official connections based on pilot demand and access requirements.