Cherry — name a product or paste feedback, get the issues worth acting on

Stays in your browser → backend → Claude.
Sample: this week's feedback— sorting —
extra sour96
Billing surprise hits accounts at renewal
3 enterprise · severity 4
Billing
71
Auth tokens expire early, breaking CI
7 reports · severity 4
Core API
44
Docs examples fail to run
4 reports · severity 2
Docs
Reaching for the feedback…

Results for

the point

Top issues, ranked by signal

Cherry proposes, you decide. Confirm a call, or tell Cherry what's off and it re-ranks.
View for
Signal = reset
0 corrections — Cherry will re-rank with your judgment.

What they love

    Do next

    How Cherry works

    01 / Gather

    Reads the web

    Cherry searches reviews, forums, Reddit, social posts and news, and keeps a source link for every issue.

    02 / Read

    Groups the duplicates

    People describe the same problem a hundred different ways. Cherry names each theme and merges them into one issue.

    03 / Rank

    Ranks by signal

    How severe an issue is and how many people report it combine into one score, which sets the order of the list.

    04 / Learn

    You correct, it adapts

    If you disagree with a call, tell Cherry. It re-ranks using your correction and remembers it for next time.

    The same process in eight stages. The last stage feeds back into the first.

    RAW FEEDBACK many channels NORMALIZE + enrich DEDUPE + cluster EXTRACT use case · problem severity · evidence RANK + ROUTE weigh the axes HUMAN verification DECIDE product or research CLOSE THE LOOP field + customer closing the loop produces new feedback, which starts the next pass

    Where Cherry connects

    Cherry sits between the places customers talk and the places teams work. It pulls feedback in from tools you already use and sends work out to the ones where your teams track it. It doesn't replace any of them.

    Feedback in
    Slack Gong CRM Warehouse
    Cherry
    Work out
    Slack Linear / Jira

    ● Live today: Slack routing. The rest is designed but not built yet. Each source gets a small adapter into the same triage core, and issue status syncs back from the linked ticket, so nobody has to update it by hand.

    Scaling notes · v1 → v2 Where Cherry breaks at scale, and what v2 changes → Ten breaks and their fixes, including what happens when two reviewers disagree, cost limits that survive a server restart, staged prompt rollouts, data permissions set by contract, and what it takes for someone else to run it.

    The operating theory

    Most feedback tools focus on collecting feedback. Whether one is useful depends on the other end: who reads the output, and what each reader needs. The diagram shows Cherry's answer: five sources, each with its own bias; three jobs in the middle; five different views on the way out; and the return arrows that turn it into a loop.

    SIGNAL IN — every window has a tint FIELD & SALES CALLS why buyers hesitate SUPPORT TICKETS where it hurts today COMMUNITY & SOCIAL loud, self-selected EARLY-ACCESS COHORTS designed signal TELEMETRY what users do, not say THE TRIAGE CORE — one system of record SCREEN real people? representative? — bots, astroturf, venting bias CLASSIFY bug or tradeoff? one-off ticket or capability gap? use case? WEIGH severity · reach · recency · $ at stake — no mystery number PRODUCT goal: what to build next cut: ranked by user pain, by use case RESEARCH / MODEL goal: capability gaps cut: systemic, authentic patterns — not tickets GTM & SALES goal: renew & expand cut: breadth, recency, $ at stake — get ahead SUPPORT goal: respond now cut: sharpest current pain + reply drafts LEADERSHIP goal: strategy calls cut: deliberate trade- offs, cost of keeping permission gate — default-deny MODEL DEVELOPMENT capability signals → training priorities USERS the loop's fuel the silent no voice ≠ no problem "you said, we did" the product changes… …which generates new signal LOOP HEALTH — how you know it's alive: time-to-triage (median and p90) · correction rate falling · roadmap citations at decision time · repeat submitters A funnel moves signal one way and goes quiet. A loop returns something at every edge — closure to users, priorities to builders, new signal to the top. If any return arrow goes dark, the loop is dying and the metrics above will say so before people do.

    An internal tool has product-market fit when teams can't make decisions without it. Cherry's bet is that feedback gets there by being cut for each reader, because what counts as high-signal depends on who's reading. Read the full essay →

    Why a human stays in the loop

    Cherry drafts every ticket but never sends one by itself. The model does the repetitive first pass, a person makes the calls that need context the model doesn't have, and Cherry measures whether each correction actually improved the next result.

    WITHOUT CORRECTION — a line: tomorrow is exactly as good as today FEEDBACK MODEL OUTPUT WITH CORRECTION — a loop: the human improves tomorrow, not just today FEEDBACK MODEL proposes HUMAN edits MEASURE did the edit help? what helped becomes tomorrow's behavior — prompts, retrieval, evals

    A correction on its own is just a data point. Measuring its effect is what turns it into learning. Read: why the human stays in the loop →