RepLens — AI Sales Call Analyzer for Diarized Transcripts

Core User Journey

1. User lands on homepage and sees pre-loaded demo transcript in paste box → 2. User clicks 'Analyze Free' with no signup required → 3. Claude processes transcript and Scorecard.tsx renders talk ratio, objections, buying signals, and coaching checklist within 30 seconds → 4. User clicks 'Save and Sign Up' after seeing value → 5. Google OAuth creates account and redirects to /dashboard showing saved scorecard → 6. User pastes a second real transcript and runs analysis → 7. User hits the 5-analysis free limit and sees upgrade modal → 8. User enters card via Stripe checkout, plan tier updates instantly → 9. Zapier webhook is configured via the Settings page to connect Fireflies → 10. Manager receives automated scorecard email in inbox before next morning standup.

Architecture Pattern

User pastes or uploads a transcript in the Next.js front end, which sends the text to the /api/analyze serverless route; that route calls the Claude API with a strict JSON system prompt, validates the response with Zod, persists the scorecard to Supabase Postgres with RLS, and simultaneously triggers a Resend email to the team manager — Stripe middleware checks the team's plan tier and analysis count before the Claude call executes to enforce usage gating.

Data Model

User has fields: id, email, created_at, google_id. Team has fields: id, name, owner_user_id, plan_tier (free/starter/growth), analysis_count, stripe_customer_id, stripe_subscription_id. TeamMember has fields: id, team_id, user_id, role (owner/member). Transcript has fields: id, team_id, uploaded_by_user_id, raw_text, filename, created_at, status (pending/complete/error). Scorecard has fields: id, transcript_id, talk_ratio (jsonb with per-speaker percentages), objections (jsonb array of objects with quote and timestamp), buying_signals (jsonb array), competitor_mentions (jsonb array), coaching_checklist (jsonb array of 5 items), created_at. Relationship: one Team has many Transcripts; one Transcript has exactly one Scorecard; RLS policies enforce team_id isolation on all tables.

Integration Points

Anthropic Claude API for transcript analysis and structured scorecard generation, Stripe for subscription billing and usage gating, Resend for transactional scorecard email delivery, Supabase for Postgres database and Google OAuth, Zapier webhook receiver for Fireflies and Otter auto-trigger, Sentry for error monitoring on the /api/analyze route, Vercel Edge CDN for static asset delivery.

V1 Scope Boundaries

V1 includes: text transcript paste, .txt and .docx file upload, Claude JSON scorecard generation, Scorecard UI, Google OAuth, Stripe billing with free tier gating, Resend email digest, Zapier webhook endpoint, Supabase persistence with RLS. V1 excludes: audio or video file processing, direct Fireflies or Otter OAuth integration, CRM integrations, Slack delivery, team leaderboards, trend dashboards, mobile app, white-label portal, bulk CSV upload, and rep-facing login or rep-initiated uploads.

Success Definition

A paying sales manager uploads a transcript, receives a scorecard email, uses specific timestamp-backed coaching points in a 1:1 with their rep, and renews their subscription the following month — all without contacting the founder.

Challenges

Distribution is the hard part — sales managers don't browse ProductHunt. First 20 customers must come from cold DMs on LinkedIn to VP of Sales titles at 20–200 person SaaS companies, plus targeted posts in r/sales and r/salestechniques offering free transcript reviews. Retaining customers beyond month 3 requires the product to surface measurable rep improvement over time, which means investing in trend dashboards by month 2 or churn will spike.

Avoid These Pitfalls

Do not let Claude return free-form prose — enforce a strict JSON schema in the system prompt with an example output block and validate every response with Zod before saving; if validation fails, retry once with a 'your previous response was not valid JSON, here is the schema again' correction prompt, otherwise scorecards will be inconsistent and the Scorecard.tsx component will throw rendering errors in production. Do not target enterprise buyers on launch — Gong and Chorus own that space with deep procurement relationships; stay laser-focused on the 10–50 person SaaS company where the sales manager is also doing RevOps and needs a $29 tool that works today, not a $50k contract with a 3-month implementation. Do not skip Supabase RLS verification before launch — test explicitly that user A cannot retrieve user B's transcripts or scorecards via a direct Supabase REST API call with user A's JWT, because a data leak of a customer's sales call content would be an immediate trust-destroying incident.

Security Requirements

All routes require Supabase Auth JWT verification; Google OAuth is the only V1 login method to reduce credential attack surface. Supabase Row Level Security policies restrict all transcript and scorecard reads and writes to the owning team_id, verified by automated tests in CI. Rate limiting of 20 analyses per hour per team is enforced at the /api/analyze route using an in-memory Supabase counter to prevent API cost abuse and denial-of-wallet attacks.

Infrastructure Plan

Next.js app deployed on Vercel with serverless API routes for all backend logic, Supabase hosted Postgres for database and auth with daily automated backups enabled, GitHub Actions CI pipeline running Zod schema unit tests and Supabase RLS integration tests on every pull request before merge, Sentry integrated on /api/analyze specifically to capture Claude timeout and validation failures with full request context for fast debugging.

Performance Targets

Target 200 DAU at month 3. Claude API call must return a complete structured scorecard within 30 seconds for a 10,000-token transcript at the 95th percentile. Dashboard page must load under 2 seconds on a cold Vercel serverless start. Scorecard email must be delivered to inbox within 60 seconds of analysis completion. Vercel Edge CDN serves all static assets with under 100ms TTFB globally.