# Product: feedback that stays data

> A scenario: a product manager asks their agent for a feature feedback survey anyone can answer, watches it on a dashboard and asks the agent for the themes.

*A scenario, not a customer story. No company, person or figure here is real; every step is something the product does today.*

## A product manager, after a launch

You shipped a feature and want to know how it landed. The usual route is a form tool, an export and a deck. Here, the answers stay data your agent can read.

## Where they are

A feature went out last week. You want ten minutes of honest feedback from the people using it, and then you want to know what it says without reading every answer twice.

## What they ask for

- A feedback survey for one feature
- What are users saying?

Each request is a Copy prompt button on the page.

## What the agent builds

A public survey whose answers only you can read, and a launch checklist beside it.

- What a user answers: How did it go?, What was confusing?, What would you change?
- Launch checklist: Survey written, Link sent to users, Dashboard built, Themes read back
- Answers by day, on your dashboard

## What happens next

1. **Start from a template.** The marketplace has survey templates. Install one and your agent builds from it rather than from a blank page: the structure and the data schema come with it, so the agent writes less and spends fewer tokens getting there.
2. **Share the link.** Anyone with the link can answer without an account. Each answer arrives as a row that only you — and your agent — can read.
3. **Watch the answers arrive.** Put a chart of the answers on a dashboard. Its widgets re-run their query on a short interval, so it fills in while the survey is open.
4. **Ask what it means.** Your agent reads the answers and counts them by theme. The question you would have built a pivot table for is one you ask in a sentence.

## What it replaces

- A form tool, a spreadsheet export and a deck of the results
- Reading every answer twice to find the pattern
- A launch checklist in a doc nobody updates

## What it does not do

- It does not email you when an answer arrives. The dashboard and your agent are where you look.
- Anonymous answers count one per browser, not one per person. A per-person count needs respondents to sign in.

## The same move, elsewhere

A roadmap review is the same shape turned around: the agent writes the page, and the team's votes are the form.

## The other case studies

- [Founders](https://superartifacts.app/case-studies/founders.md): A projection you can edit, and an update for investors that is a link rather than a deck.
- [Engineering](https://superartifacts.app/case-studies/engineering.md): A sprint review or a retrospective your agent assembles from the work it just did.
- [People](https://superartifacts.app/case-studies/people.md): A hiring board for one role, and an onboarding checklist for the person you hired.
- [Revenue](https://superartifacts.app/case-studies/revenue.md): An onboarding page for one customer, shared with the people on their side.