Turn what a customer said into evidence, then into what we build
Evidence quoted from meetings, roadmap requests with votes and comments, open questions, and experiments that are honest about what they test.
Your role
Where this work lands
How it goes now
A customer asks for something on a call. It becomes a line in private notes, maybe a message, and the next time it comes up we argue about how often we have heard it. The quote that would have settled it is gone.
How it goes now
The work already exists. It is just scattered.
A customer asks for something on a call. It becomes a line in private notes, maybe a message, and the next time it comes up we argue about how often we have heard it. The quote that would have settled it is gone.
- 01
Evidence carries an exact quote from a linked meeting in the same project, long enough to be a quotation. A claim that cannot be located in its source never becomes a record.
- 02
The evidence explorer clusters observations by theme and claim type and expands every count into the accounts and quotes behind it, so the path from a number back to the transcript is never broken. Below a declared floor of five dated observations it withholds a trend instead of drawing one.
- 03
Roadmap requests separate a new feature from an improvement, carry a quarter, progress, status and an owner, take one reversible vote per person, and keep comments with their author and time. Revisions let you read the earlier wording rather than argue about it.
- 04
Open questions record what we do not know yet, next to the experiments testing it. An experiment with no stopping rule is filed as exploration, because that is what it is.
- 05
Ask Growth Kit answers from the records in this project and cites the records it used. It reads what we wrote down. It does not browse, and it does not save anything as research.
In the product
The screens you will open.


Where this lives in Growth-OS
Read the feature page, or go straight to the page in Growth-OS. The app asks you to sign in.
Meetings and evidence
Reviewed observations, the exact quote behind each one, and the explorer that clusters them.
Roadmap
Requests with a quarter, an owner, one vote per person and comments that keep their author.
Open questions and experiments
What we do not know yet, what is testing it, and where the constraint actually sits.
Ask Growth Kit
A question answered from our own records, with every citation checked.
Open Evidence
Cluster what customers told us and open the quotes.
Open Roadmap
See what is requested and what is already running.
Something missing for your role?
Tell us what your week actually looks like and which page you cannot make work yet. Your message opens as an email draft; nothing is sent in the background.
Your message
Tell us what you need
This reaches the people who build and run Growth-OS. A written question beats one asked in a corridor and forgotten by lunch.