Feedback that stays connected to what ships
A feedback product for B2B teams, connecting customer requests to product decisions, what gets shipped and what happens after launch.

What happened after launch Each shipped feature keeps the revenue or churn target attached to it, so the team can compare what was expected with what actually happened.


From request to shipped Requests keep their history as they move through the product process, while the inbox groups work by where each request currently stands.


Different roles, same system Leadership sees product impact and roadmap movement, while customer-facing teams get a faster way to submit feedback with account context attached.
The problem
Sales, Support and Success collect customer feedback in different places. Requests lose context, get grouped manually and rarely make their way back to the person who raised them.
There was also no connection between what shipped and the result it was expected to create.