Before you begin
Start with one workflow, one source of information, and a named reviewer.
Use sanitized sample data while you are testing the structure and review loop.
Build the workflow
Here is a useful first app for a founder or product team
A customer interview analyzer.
The user pastes notes or uploads a transcript.
The app
1. Identifies the customer’s current process
2. Extracts problems, requested outcomes, objections, and urgency
3. Groups repeated themes across interviews
4. Keeps direct evidence linked to each theme
5. Lets a reviewer correct the classification
The result is a table with
Customer
Problem
Current workaround
Requested outcome
Urgency
Evidence
Reviewer correction
Starter prompt
“Build an internal customer interview analyzer for a product manager. Accept pasted notes or transcripts. Extract the fields above, group repeated problems, preserve evidence, and let the manager correct the result. Do not create a CRM or roadmap yet.”
It is small enough to build quickly and useful enough to return to after every interview.
Common mistakes
Summarizing interviews without preserving evidence.
Turning the first version into a CRM or roadmap tool.
Removing the reviewer’s ability to correct classifications.
Frequently asked questions
Can I use this template for a different industry?
Yes. Replace the role, input, rule set, output, reviewer, and prohibited actions. Keep the first workflow bounded and inspectable.
When should I use production data?
After the structure works with safe examples and the required permissions, security, retention, and review controls are in place.