ReplyMap - AI Agent That Maps Every Email Thread to a Next Action

Your inbox is full of threads where someone is waiting on you and you have absolutely no idea who. ReplyMap is an AI agent that connects to Gmail, scans every open thread, extracts the required next action and deadline, and surfaces a prioritized action map every morning — zero manual tagging.

𝕏 Post Reddit HN

Difficulty

intermediate

What is it?

Gmail power users on HN and r/productivity repeatedly describe inbox paralysis: hundreds of threads, no visibility into which ones require action, and the cognitive tax of re-reading every thread to reconstruct context. Existing tools like SaneBox or Superhuman sort by recency or priority labels but do not extract what specifically needs to happen next. ReplyMap is an AI Agents and RAG idea: a background agent that runs on a schedule, retrieves unresolved email threads via Gmail API, chunks thread content, passes it through a LangChain extraction chain backed by Claude, and classifies each thread into: waiting-on-me, waiting-on-them, or no-action-needed — with a one-sentence next action extracted. A morning digest email and a live web dashboard surface the action map. This is fully buildable with existing Gmail API, LangChain, Claude API, and Supabase scheduled functions.

Why now?

LangChain MapReduce chains over long email threads became reliable in 2025 and Claude's context window expansion makes full-thread analysis cost-effective at $19/month price points — this accuracy level was not achievable cheaply before.

▸Background Gmail agent that runs every 24 hours scanning all threads with activity in the last 14 days (Implementation note: LangChain MapReduce chain over thread message list, Claude extracts next-action sentence and classification).
▸Three-bucket thread classification: waiting-on-me, waiting-on-them, no-action-needed — displayed as a prioritized action map dashboard.
▸Morning digest email via Resend listing top 5 waiting-on-me threads with one-line next actions and direct reply links.
▸Snooze and mark-done actions from the dashboard that update Supabase state without touching Gmail labels.

Target Audience

Founders, freelancers, and consultants managing 50+ active email threads — estimated 5M+ knowledge workers in the US who use Gmail as their primary work tool.

Example Use Case

Tom, a freelance consultant juggling 8 active client projects, opens his ReplyMap morning digest, sees 3 threads flagged as waiting-on-him with extracted next actions, replies to all 3 in 12 minutes, and never misses a client follow-up deadline again.

User Stories

▸As a freelance consultant, I want a daily digest of email threads that need my reply, so that I never miss a client waiting on me.
▸As a founder, I want each open thread classified as waiting-on-me or waiting-on-them, so that I can process my inbox in under 15 minutes each morning.
▸As a knowledge worker, I want to mark a thread as done from my dashboard without touching Gmail, so that my action map stays clean without manual label management.

Done When

✓Thread classification: done when dashboard shows all scanned threads sorted into 3 labeled buckets with a one-sentence next action visible on each card.
✓Morning digest: done when user receives an email by 7am listing top 5 waiting-on-me threads with working reply links that open Gmail directly.
✓Snooze: done when user clicks Snooze on a thread card, enters a date, and the card disappears from the active list and reappears on the snoozed date.
✓Payment gate: done when user hits 30-thread free limit, sees upgrade prompt, completes $19 Stripe checkout, and agent immediately scans all threads without limit.

Is it worth building?

$19/month x 60 users = $1,140 MRR at month 3. $19/month x 250 users = $4,750 MRR at month 8.

Unit Economics

CAC: $8 via Reddit organic seeding. LTV: $228 (12 months at $19/month). Payback: under 1 month. Gross margin: 83%.

Business Model

SaaS subscription

Monetization Path

Free: 7-day trial, 30 threads analyzed. Paid $19/month: unlimited threads and daily digest. Upgrade triggered at trial end.

Revenue Timeline

First dollar: week 3 via first beta-to-paid conversion. $1k MRR: month 3. $5k MRR: month 9.

Estimated Monthly Cost

Claude API: $35, Gmail API: $0, Vercel: $20, Supabase: $25, Resend: $10, Stripe fees: ~$10. Total: ~$100/month at launch.

Profit Potential

Full-time viable at $5k-$10k MRR with 260-525 paying users.

Scalability

High — expand to Outlook, add Slack thread scanning, team shared action maps, and CRM sync.

Success Metrics

Week 1: 20 beta users connected. Week 3: 12 paid conversions. Month 2: 60 paying users, 80% 4-week retention.

Launch & Validation Plan

Post in r/productivity with a free beta offer — target 20 signups who connect Gmail before writing the full agent logic.

Customer Acquisition Strategy

First customer: post in Indie Hackers Show HN thread and r/productivity offering free lifetime access to first 10 beta users who write a review. Ongoing: SEO on 'inbox zero tool Gmail', ProductHunt launch, Twitter/X productivity community.

What's the competition?

Competition Level

Medium

What's the roadmap?

Feature Roadmap

V1 (launch): Gmail connect, 3-bucket classification, morning digest, snooze, Stripe billing. V2 (month 2-3): reply suggestions per action card, thread snooze reminders via email. V3 (month 4+): Outlook support, team shared action maps, Notion sync.

Milestone Plan

Phase 1 (Week 1): agent pipeline working end-to-end on test Gmail account — done when 10 threads classify correctly. Phase 2 (Week 2): dashboard, digest email, Stripe — done when first $19 payment processed. Phase 3 (Month 2): 60 paying users, ProductHunt — done when retention above 80% at week 4.

How do you build it?

Tech Stack

Next.js, LangChain, Claude API, Gmail API, Supabase Edge Functions, Resend — build with Cursor for agent pipeline, v0 for action map dashboard

Suggested Frameworks

LangChain for extraction chain, Gmail API (googleapis npm), Supabase Edge Functions for scheduled runs

Time to Ship

2 weeks

Required Skills

Gmail OAuth, LangChain extraction chains, Claude API, Supabase Edge Function cron scheduling.

Resources

Gmail API Node.js quickstart, LangChain extraction chain docs, Claude API docs, Supabase Edge Functions cron guide.

MVP Scope

app/page.tsx (landing + Gmail connect CTA), app/dashboard/page.tsx (action map with 3 buckets), app/api/auth/gmail/route.ts (OAuth handler), app/api/agent/run/route.ts (trigger agent manually), lib/agent/thread-scanner.ts (Gmail API fetch + LangChain extraction), lib/agent/classifier.ts (Claude classification chain), lib/db/schema.ts (users, threads, actions, snoozes), components/ActionCard.tsx (per-thread action display), seed.ts (10 mock threads with actions), .env.example (Gmail client ID, Claude API key, Supabase URL, Resend key, Stripe key)

Core User Journey

Connect Gmail -> agent scans threads overnight -> morning digest email arrives -> click action card -> reply -> mark done.

Architecture Pattern

Supabase Edge Function cron (daily) -> Gmail API fetches recent threads -> LangChain MapReduce extracts next-action per thread -> Claude classifies bucket -> results written to Supabase -> dashboard reads Supabase -> Resend sends morning digest email.

Data Model

User has one GmailConnection. GmailConnection has many Threads. Thread has one ActionClassification and one ExtractedNextAction. User has many Snoozes tied to Threads.

Integration Points

Gmail API for thread retrieval, LangChain for extraction chain orchestration, Claude API for classification and next-action extraction, Supabase for state and scheduling, Resend for morning digest emails, Stripe for billing.

V1 Scope Boundaries

V1 excludes: Outlook support, team shared action maps, calendar integration, CRM sync, mobile app.

Success Definition

A paying user wakes up, opens their morning digest email, clicks a thread link, replies, and marks it done — all without opening Gmail search or reading full thread history.

Challenges

Gmail OAuth app verification takes 2-4 weeks — apply for Google Cloud Console approval on day one. Churn risk is high if action extraction accuracy is below 80% — must batch-test on real thread samples before launch.

Avoid These Pitfalls

Do not request Gmail write scopes in v1 — read-only reduces OAuth verification friction dramatically. Do not over-extract: if Claude generates a next action longer than 15 words, the prompt needs tightening before users see it. Finding first 10 paying customers takes longer than building — seed Reddit and IH communities 2 weeks before launch.

Security Requirements

Supabase Auth with Google OAuth read-only Gmail scope. RLS on all thread and action tables. Gmail access tokens encrypted at rest in Supabase. Rate limiting: 1 agent run per user per hour. GDPR: email content not stored beyond classification result — only metadata and extracted next-action string retained.

Infrastructure Plan

Vercel for Next.js, Supabase for Postgres and Edge Function cron, GitHub Actions for CI/CD, Sentry for errors — estimated $100/month at launch.

Performance Targets

Expected 50 DAU at launch. Agent run completion under 60 seconds for 50 threads. Dashboard load under 2s. Claude API calls batched per thread to minimize latency.

Go-Live Checklist

☐Security audit complete.
☐Payment flow tested end-to-end.
☐Sentry error tracking live.
☐Supabase Edge Function cron verified in production.
☐Custom domain with SSL active.
☐Privacy policy documenting email data handling published.
☐10 beta users confirmed digest accuracy acceptable.
☐Rollback: Vercel previous deployment.
☐Launch post drafted for r/productivity and Indie Hackers.

First Run Experience

On first run: 10 seeded mock email threads are pre-loaded into the dashboard showing all 3 classification buckets with sample next-action cards. User can explore the full action map and snooze flow without connecting Gmail. No manual config required: demo mode reads from seeded Supabase data with no Gmail OAuth needed until user clicks Connect Gmail.

How to build it, step by step

1. Define Supabase schema for users, gmail_connections, threads, action_classifications in lib/db/schema.ts. 2. Register Gmail OAuth app with read-only scopes in Google Cloud Console and submit verification. 3. Run npx create-next-app with Tailwind, install googleapis, LangChain, and Resend SDK. 4. Build Gmail thread fetcher in lib/agent/thread-scanner.ts returning last 14 days of threads with message content. 5. Build LangChain MapReduce chain in lib/agent/classifier.ts that classifies each thread and extracts one next-action sentence via Claude. 6. Wire Supabase Edge Function cron to run the agent daily at 6am user local time. 7. Build 3-bucket action map dashboard in app/dashboard/page.tsx using v0 components. 8. Build Resend morning digest email template listing top 5 waiting-on-me threads with direct Gmail reply links. 9. Add Stripe $19/month checkout with thread scan gate after 30 free threads. 10. Verify: connect real Gmail, run agent manually, confirm threads classified into 3 buckets, confirm digest email received, confirm Stripe payment unlocks full scan.

Generated

April 24, 2026

Model

claude-sonnet-4-6

← Next

PriceDrop - A/B Price Testing Engine for Shopify Stores Under $1M Revenue

ClauseScan - NLP Contract Clause Risk Ranker for Freelancers

Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.