ReplyForge — The AI Email Answering Layer That Actually Reads Context Before It Hits Send
Every SMB owner has tried to automate email replies and ended up with a bot that sends the wrong template to their most important client. ReplyForge connects to Gmail or Outlook, classifies each inbound email by intent, drafts a context-aware reply from the business's own knowledge base, and holds it for one-click human approval before sending.
Difficulty
intermediate
Category
Business Automation
Market Demand
Very High
Revenue Score
8/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
6/10
Validated by Real Pain
— sourced from real community discussions
SMB owners and automation enthusiasts report that existing email automation tools send wrong template replies or break on threaded conversations, making them too risky to trust for real client emails.
What is it?
The r/n8n thread on automated email answering reveals the real failure mode: generic Zapier templates send wrong replies, custom scripts break on forwarded threads, and LLMs hallucinate business policies they were never given. ReplyForge fixes this by grounding every reply in a business knowledge base the owner builds in 10 minutes — services offered, pricing, FAQs, tone of voice. It then classifies inbound emails into buckets (inquiry, complaint, booking request, invoice question) and drafts a reply per bucket, delivered to a review queue before any email leaves the account. The human approval step is the killer feature — it is what makes SMB owners trust it enough to turn it on for real clients. Fully buildable in 2 weeks with Gmail API, Claude API, and a Supabase review queue.
Why now?
Gmail API push notifications are stable and free, Claude's context window in May 2026 handles full email threads reliably, and the r/n8n community is actively failing to self-build this — making it a validated pain with no polished solution at SMB pricing.
- ▸Gmail OAuth connection with secure token storage and intent classification on inbound emails
- ▸Business knowledge base builder: 10-minute setup with services, pricing, FAQs, and tone guide
- ▸One-click approval queue: drafted replies held for human review before sending
- ▸Weekly digest email showing emails handled, time saved, and approval rate
Target Audience
SMB owners handling 20-80 inbound emails per day — freelancers, consultants, home service businesses, and e-commerce operators. Estimated 4M businesses in the US in this tier.
Example Use Case
A home cleaning business owner opens ReplyForge at 8am, sees 12 overnight emails pre-drafted as replies, approves 9 with one click and edits 3, clears her inbox in 4 minutes instead of 40.
User Stories
- ▸As an SMB owner, I want AI-drafted replies waiting for my approval each morning, so that I clear my inbox in under 10 minutes instead of 40.
- ▸As a home service business operator, I want the AI to know my pricing and services before it drafts replies, so that it never quotes the wrong number to a client.
- ▸As a freelance consultant, I want to see which emails the AI struggled to classify, so that I can improve my knowledge base and reduce the edit rate over time.
Done When
- ✓Gmail connection: done when user clicks Connect Gmail, completes OAuth, and sees their inbox name appear on the dashboard.
- ✓Knowledge base: done when user adds 5 FAQ entries and the system confirms they will be injected into future drafts.
- ✓Approval queue: done when an inbound test email appears as a draft card with approve, edit, and reject buttons within 2 minutes of arrival.
- ✓Send: done when user clicks approve and receives a sent confirmation, and the email appears in Gmail Sent folder within 30 seconds.
Is it worth building?
$39/month × 80 SMBs = $3,120 MRR by month 2. $89/month × 20 agencies = $1,780. Combined $4,900 MRR. $5k MRR assumes 130 total paying accounts from Reddit and ProductHunt launch — realistic given the active pain signal in r/n8n and r/smallbusiness.
Unit Economics
CAC: $12 via Reddit posts and Facebook group outreach at 6% conversion. LTV: $468 (12 months at $39/month). Payback: 1 month. Gross margin: 80%.
Business Model
$39/month for up to 3 connected inboxes. $89/month for up to 10 inboxes (agency plan).
Monetization Path
14-day free trial with 50 AI draft credits. Upgrade triggered when credits exhaust or when user connects second inbox.
Revenue Timeline
First dollar: week 3 from first trial-to-paid conversion. $1k MRR: month 2. $5k MRR: month 5.
Estimated Monthly Cost
Claude API: $55, Supabase: $25, Vercel: $20, Resend: $10, Stripe fees: $30, Google API: free tier. Total: ~$140/month at launch.
Profit Potential
$8k-$20k MRR within 9 months targeting SMB owners via Reddit and agency reselling.
Scalability
High — add Outlook support, team inboxes, CRM sync, and vertical-specific knowledge base templates.
Success Metrics
Week 2: 10 beta SMBs connected inbox. Month 1: 75% approval rate on AI drafts. Month 2: 40 paying accounts.
Launch & Validation Plan
Post in r/smallbusiness asking how many hours per week they spend on email — gather 30 responses before building.
Customer Acquisition Strategy
First customer: post in r/n8n and r/automation offering free 60-day beta to anyone actively trying to automate email replies — this community is already proven to be in pain. Ongoing: r/smallbusiness, Facebook groups for home service businesses, ProductHunt, cold email to Yelp-listed local service businesses.
What's the competition?
Competition Level
Medium
Similar Products
Zapier email automation (no AI drafting, template-only), SaneBox (filters not drafts), Front (team inbox, enterprise pricing) — none combine intent classification with a knowledge-base-grounded human approval queue at SMB pricing.
Competitive Advantage
Human approval queue prevents the trust-destroying wrong-reply problem that kills every other email automation tool. Knowledge base grounding stops hallucinated policies.
Regulatory Risks
Gmail API requires Google OAuth verification before accessing user email data — apply for verification on build day one. GDPR: email content is PII and must be encrypted at rest and deletable on request. Do not store full email bodies longer than 30 days.
What's the roadmap?
Feature Roadmap
V1 (launch): Gmail connect, knowledge base, approval queue, one-click send. V2 (month 2-3): Outlook support, edit-and-learn from rejections. V3 (month 4+): CRM sync, team inboxes, mobile approval notifications.
Milestone Plan
Phase 1 (Week 1-2): schema, Gmail OAuth, classify and draft routes ship. Phase 2 (Week 3-4): approval queue UI, Stripe billing, Resend digest live with 10 beta users. Phase 3 (Month 2): 40 paying accounts, $1k MRR hit.
How do you build it?
Tech Stack
Next.js, Claude API, Gmail API, Supabase, Stripe, Resend — build with Cursor for API routes, v0 for review queue UI, Lovable for onboarding flow.
Suggested Frameworks
LangChain for intent classification chain, Supabase Auth for OAuth token storage, Zod for reply schema validation
Time to Ship
2 weeks
Required Skills
Gmail API OAuth flow, Claude API, Supabase, Next.js API routes.
Resources
Google Gmail API docs, Anthropic docs, Supabase quickstart, r/n8n for beta user recruitment.
MVP Scope
app/page.tsx (landing + hero), app/dashboard/page.tsx (reply approval queue), app/setup/page.tsx (knowledge base builder), app/api/gmail/callback/route.ts (OAuth handler), app/api/classify/route.ts (intent classification), app/api/draft/route.ts (Claude reply drafter), app/api/send/route.ts (approved reply sender), lib/db/schema.ts (Inbox, Email, Draft, KnowledgeBase), components/DraftCard.tsx (approve/edit/reject UI), .env.example, seed.ts (demo inbox with 5 pre-classified emails).
Core User Journey
Connect Gmail -> build knowledge base in 10 min -> inbound emails appear as drafts in queue -> approve with one click -> email sends -> inbox stays clear.
Architecture Pattern
Gmail webhook -> Supabase inbox queue -> Claude classifies intent -> Claude drafts reply using knowledge base context -> Draft stored in Postgres -> Owner sees approval queue in dashboard -> One-click approve -> Gmail API sends reply.
Data Model
User has many Inboxes. Inbox has many Emails. Email has one Draft. Draft has a status (pending, approved, rejected, sent). User has one KnowledgeBase with many KnowledgeEntries.
Integration Points
Gmail API for inbox access and sending, Claude API for classification and drafting, Supabase for data and auth, Stripe for billing, Resend for weekly digest emails.
V1 Scope Boundaries
V1 excludes: Outlook support, team inboxes, mobile app, CRM sync, AI that learns from approval patterns, attachment handling.
Success Definition
An SMB owner discovers ReplyForge through Reddit, connects their inbox without founder help, approves their first AI draft within 10 minutes of setup, and upgrades to paid after the trial.
Challenges
Gmail API OAuth approval from Google requires a verification process that can take 2-4 weeks — start this on day one of the build. Distribution is the real challenge: SMB owners do not browse ProductHunt, so Reddit and direct outreach to small business Facebook groups is required.
Avoid These Pitfalls
Do not skip Google OAuth verification — without it you cannot access real user email and the product is dead on arrival. Do not auto-send without human approval in V1 — SMB owners will churn the moment one wrong email goes out. Finding first 10 paying SMBs takes longer than building — budget 3x time for Reddit and Facebook group outreach.
Security Requirements
Supabase Auth with Google OAuth, encrypt Gmail tokens at rest using Supabase vault, RLS on all user tables, rate limit draft generation to 200 per day per account, GDPR: email body storage capped at 30 days with deletion endpoint.
Infrastructure Plan
Vercel for Next.js and API routes, Supabase for Postgres and auth, Sentry for error tracking, GitHub Actions for CI, Vercel Analytics for traffic — estimated $140/month.
Performance Targets
200 DAU at launch, 3,000 req/day. Draft generation under 8 seconds. Dashboard queue load under 2s. Gmail webhook processing under 30 seconds end-to-end.
Go-Live Checklist
- ☐Gmail OAuth verification approved by Google.
- ☐Stripe payment flow tested end-to-end.
- ☐Sentry error tracking live.
- ☐Monitoring dashboard configured.
- ☐Custom domain with SSL active.
- ☐Privacy policy with email data retention clause published.
- ☐5 beta SMBs approved first AI draft in real inbox.
- ☐Rollback plan documented.
- ☐Reddit and Facebook group launch posts drafted.
First Run Experience
On first run: a seeded demo inbox with 5 pre-classified emails and AI-drafted replies appears in the approval queue. User can immediately click approve on a demo draft, see a mock send confirmation, and explore the knowledge base editor. No manual config required: demo data loaded via seed.ts, Gmail connection can be skipped in demo mode to see the full workflow.
How to build it, step by step
1. Define Drizzle schema for Inbox, Email, Draft, KnowledgeBase, KnowledgeEntry in lib/db/schema.ts. 2. Run npx create-next-app with TypeScript and Tailwind. 3. Set up Supabase Auth and apply for Gmail API OAuth verification immediately. 4. Build Gmail OAuth callback at app/api/gmail/callback/route.ts with secure token storage in Supabase. 5. Set up Gmail push notification webhook to trigger on new inbound emails. 6. Write Claude classification prompt in app/api/classify/route.ts returning intent bucket. 7. Write Claude drafting prompt in app/api/draft/route.ts injecting knowledge base context. 8. Build approval queue dashboard at app/dashboard using DraftCard component (approve/edit/reject per draft). 9. Wire app/api/send/route.ts to Gmail API for approved replies and Stripe for billing. 10. Verify: connect a real Gmail test account, send an inbound test email, confirm draft appears in queue within 60 seconds, approve and confirm the reply sends.
Generated
May 20, 2026
Model
claude-sonnet-4-6
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.