Clave Product · Branding

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.

RoleIdea · Branding · Product design
Built withReact · TypeScript
Clave's Impact screen in dark theme: four portfolio stat cards above per-feature charts where a realised revenue curve rises through a dashed expected-target line, each with an analyst note.

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.

A Clave request detail: a ten-node status rail running from Submitted through linked, reviewed, accepted, on roadmap, in development, Shipped, to Being tracked, beside the PM's written status update.
Clave's Insights Inbox: eighteen requests needing triage grouped by lifecycle state, with source filter chips and account context on each row.

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.

Clave's leadership dashboard: expansion revenue, churn movement and features shipped, above a needs-attention queue and a Now / Next / Later roadmap snapshot.
Clave's submit form: a rich-text editor with a dictate option, type and priority pickers, attachable account context and a live preview of the resulting request card.

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.