Customer interview notes with pain-point tagging
Customer interview notes with pain-point tagging is a SaaS idea for founders and small product teams who talk to customers weekly, priced to test at $19 a month per founder, $49 for teams. Interview notes end up in scattered docs. With it, founders keep every customer call in one place, tag the pains, and see which problems come up most.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
Interview notes end up in scattered docs. When it’s time to decide what to build, nobody can say how many customers raised a problem, or in what words.
Why now: Call recordings and AI transcripts are everywhere, but turning them into decisions is still done by hand.
What do they use today?
Most founders type notes into whatever is open and keep recordings in a folder they rarely replay. To find a pattern they reread old files, or go with the last few calls they remember.
How does it work?
After a customer call, a founder pastes in the notes or uploads the transcript. The product suggests tags for pains, requests and quotes, and the founder confirms or changes each one. Over time a board ranks the pains by how many customers raised them, and a read-only view lets the team see what customers said instead of one person’s memory of it.
What goes in the first version?
- Paste notes or upload a transcript per interview
- Tag pains, requests and quotes
- Tag suggestions from AI that you confirm
- A board of pains ranked by how many customers raised them
- A read-only view to share with the team
Who pays, and how much?
- Who pays
- Founders and small product teams who talk to customers weekly
- Price to test
- $19 a month per founder, $49 for teams
A per-founder price suits the solo founder who runs every call, and a flat team price suits a small group sharing one board. Both are simple enough for a founder to buy without anyone else signing off.
How to test it in 7 days
- 1Ask in r/startups and r/ProductManagement how people organise interview notes.
- 2Interview five founders about their last build decision.
- 3Tag ten of your own interviews by hand and share the board.
Where to find the first customers
- r/startups and r/ProductManagement
- Indie Hackers
- Founder groups at accelerators
What are the risks?
- Research tools for bigger teams exist, so stay simple and founder-priced.
- Transcripts hold personal data, so privacy matters.
How to build it on shipanysaas
4 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.
- Already in the kit
- Sign-in
- Teams and roles
- Billing
- Emails
- You build
- Notes and transcript upload
- Tagging with AI suggestions
- Pain-point board
See the starting prompt
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase. Help me build the first version of Customer interview notes with pain-point tagging. Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it. ## The product - What it does: Founders keep every customer call in one place, tag the pains, and see which problems come up most. - Who pays: Founders and small product teams who talk to customers weekly - Their problem: Interview notes end up in scattered docs. When it’s time to decide what to build, nobody can say how many customers raised a problem, or in what words. - Price to test: $19 a month per founder, $49 for teams (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. Paste notes or upload a transcript per interview 2. Tag pains, requests and quotes 3. Tag suggestions from AI that you confirm 4. A board of pains ranked by how many customers raised them 5. A read-only view to share with the team ## Already in the kit: reuse it, never rebuild it - Sign-in: email and password or Google, plus magic links and passkeys you can switch on - Teams and roles: team accounts with members, roles and invitations - Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments - Emails: transactional email through Resend or Nodemailer ## New code it needs - Notes and transcript upload - Tagging with AI suggestions - Pain-point board ## How to work 1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK. 2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files. 3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next. ## Rules - Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel. - Leave the parts of the kit this product doesn't use as they are. Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
Guides for the parts it uses
Want ideas for your own skills?
The free generator writes three while you watch, each with a plan and a starting prompt. Or paste this idea into it for two sharper versions.
More ideas: Developer and AI
Safe AI-agent access to internal tools
Small software teams give AI agents read access to internal data through one gateway, with keys they can revoke and a log of every call.
Security questionnaire answers for small SaaS teams
Founders keep approved security answers in one library, and AI drafts each new questionnaire from them for a person to check.
Thumbs-down feedback inbox for AI product teams
Small AI product teams get every thumbs-down with its conversation, grouped with similar complaints and ready to become a test.