DocChat - AI-Powered Customer Support Bot That Learns Your Docs Automatically

Drop a script tag on your docs site, it auto-indexes your documentation with Claude, and customers get an AI chat widget that answers questions straight from your docs — reducing support tickets by 40%.

𝕏 Post Reddit HN

Difficulty

low-code

What is it?

Every SaaS spends 30–50% of support volume on questions answered in their docs. A customer asks 'How do I reset my password?' instead of reading the 2-minute guide. Support team answers the same question 50 times per day. DocChat auto-indexes your entire documentation site, embeds a chat widget on your docs, and uses Claude to answer questions directly from your docs (with citations). No setup required — just add a script tag. The bot learns your docs' structure, keeps a conversation history per user, and escalates to human support only when a question isn't covered. For a $5M ARR SaaS with 10 support reps, this saves 2–3 rep-years, cuts support costs by $200k+, and reduces doc read time. Why 100% buildable right now: Claude's retrieval API is mature. Web embedding is simple (Hotjar/Intercom precedent). Supabase handles the vector search. Documentation crawling is stable. Every founder on ProductHunt and SaaS communities says 'our team gets hammered with support tickets we could deflate with better docs.' This solves that at 1/10th the cost of hiring support.

Why now?

Claude's embedding and QA capabilities are now production-ready (2025). Supabase pgvector made vector search accessible to indie makers. Support automation is at peak demand post-2024 customer service cost explosion. Docs-based AI chat is trending hard (ChatGPT on docs use case is huge).

▸Auto-crawl documentation site and index pages (Implementation: Cheerio + Supabase pgvector for embeddings)
▸Chat widget embeddable via script tag
▸Claude-powered QA with doc citations
▸Conversation history per user session
▸Admin dashboard to manage crawls and view analytics

Target Audience

SaaS companies and developer tools with 100–1,000 support tickets per month and 500+ pages of documentation. Estimated 200,000 such companies globally. Initial target: US/EU SaaS with 5+ support staff, active documentation. ICP: support manager or founder frustrated with repetitive questions.

Example Use Case

Jordan, a founder of a $3M ARR developer tools SaaS with 1,500 monthly support tickets, adds DocChat's script tag to his docs site. The bot auto-crawls 300 doc pages, indexes them with Claude embeddings. First week: 400 of 1,500 tickets are now answered by the widget (27% deflation). Jordan's 4-person support team now handles only complex issues. Support satisfaction improves (users get answers instantly), rep burnout decreases. By month 2, support load is down 45%, equivalent to hiring 2 full-time support reps at $150k/year.

User Stories

▸As a support manager, I want to deflate repetitive questions with an AI chatbot, so that my team can focus on complex issues and reduce burnout.
▸As a customer, I want instant answers to docs questions without waiting for support, so that I can unblock myself quickly and feel supported.
▸As a founder, I want to see which questions aren't covered in my docs, so that I can prioritize doc improvements based on real gaps.

Acceptance Criteria

Crawl Setup: done when user inputs doc site URL and crawler successfully indexes 100+ pages in under 5 minutes. Embedding Generation: done when pages are split into chunks and Claude API generates embeddings stored in pgvector. Chat Widget: done when script tag embedded on docs site displays chat widget without errors. QA Response: done when user asks a question and Claude returns answer with citations to original docs pages in under 3 seconds. Analytics: done when dashboard shows total chats, deflected tickets estimate, and top questions.

Is it worth building?

$49/month for up to 500 monthly support queries × 100 companies = $4,900 MRR at month 3. $199/month for 5,000+ queries × 50 companies = $9,950 MRR by month 5.

Unit Economics

CAC: $45 (ProductHunt launch + Reddit + direct cold outreach). LTV: $588 (12 months × $49/month, assumes 65% retain 1 year). Payback: ~1.5 months. Gross margin: 80% (after API and hosting).

Business Model

SaaS subscription

Monetization Path

Free tier: 100 monthly chats, basic indexing. Paid at $49/month (unlimited chats, auto-crawl updates, analytics), $199/month (custom branding, priority support, API access).

Revenue Timeline

First dollar: week 2 (beta upgrade). $1k MRR: month 2. $3k MRR: month 4. $8k MRR: month 6.

Estimated Monthly Cost

Claude API: $30 (assume 500 chats × $0.06 per chat for analysis estimate). Supabase: $25. Vercel: $20. Stripe: ~$15. Total: ~$90/month at launch.

Profit Potential

Full-time viable at $3k–$10k MRR. Potential exit value $5M–$15M (support software 3–5x ARR).

Scalability

Very high — can expand to Slack integration (sync FAQs to Slack), Salesforce sync (log chats as cases), multimodal docs (video indexing), analytics dashboard, feedback loop for doc gaps.

Success Metrics

Week 1: 50 signups. Week 2: 12 paying customers. Month 2: 45 paying. Retention: 88% at 30 days (high because immediate ROI is clear).

Launch & Validation Plan

Interview 20 support managers. Show landing page with 'reduce support tickets by 40%' pitch. Ask: 'Would you pay $49/month to deflate 30% of your support volume?' If 12+ say yes, build. Recruit 3 beta customers with live support teams and >500 docs pages.

Customer Acquisition Strategy

First customer: Post on r/SaaS and r/startups with 'we get 50 'how do I reset my password' tickets per day' narrative, offer $49/month for $0 for 3 months to first 5 signups. Then: ProductHunt launch, direct outreach to 100 support managers on LinkedIn, Slack communities (Founder, Support Engineer), G2 reviews.

What's the competition?

Competition Level

Medium

What's the roadmap?

Feature Roadmap

V1 (week 2): Auto-crawl docs, Claude QA, embedded widget, basic analytics, Stripe billing. V2 (month 2–3): Slack integration, feedback loop for doc gaps, chat quality scoring, custom widget branding. V3 (month 4+): Salesforce sync, multimodal docs, team collaboration on widget settings, API for third-party access.

Milestone Plan

Phase 1 (Week 1): Crawler working, embedding generation via Claude tested locally, Supabase pgvector schema ready. Done when: founder can crawl a test docs site and see 50+ embeddings in Supabase. Phase 2 (Week 2): Chat endpoint working, widget iframe built, Stripe checkout wired. Done when: founder can ask a question in widget and receive answer with citations. Phase 3 (Month 1–2): ProductHunt launch, 3 beta teams onboarded, analytics dashboard live. Done when: 10+ paying customers, zero critical bugs on live sites.

How do you build it?

Tech Stack

Next.js for admin dashboard, Claude API for QA, Supabase for vector search and conversation history, Vercel for hosting — build with Lovable for widget UI, Cursor for backend and crawling logic, v0 for dashboard.

Time to Ship

2 weeks

Required Skills

Claude API, web crawling (Cheerio or Playwright), vector embeddings (Supabase pgvector), Next.js dashboard, iframe embeds.

Resources

Claude API docs, Supabase docs, Cheerio docs, Next.js tutorials, iframe embedding guides.

MVP Scope

Next.js admin dashboard for doc site URL input and crawl status. Supabase schema for doc pages, embeddings, conversations, user sessions. Crawler (Cheerio-based) triggered on setup and weekly. Claude API integration for chat responses. Embedded chat widget (iframe-based). Stripe billing. Analytics page showing deflected tickets. Must-have files: /pages/api/crawl, /pages/dashboard, /lib/doc-crawler, /lib/claude-qa, /public/widget.js (iframe loader), /pages/api/chat, database migrations.

Core User Journey

Architecture Pattern

Doc site URL -> Cheerio crawler fetches pages -> Claude API generates embeddings -> stored in Supabase pgvector -> user asks question in widget -> widget sends query to /api/chat -> Claude searches pgvector and generates response with citations -> returned to widget.

Data Model

Company has one DocsIndex. DocsIndex has many Pages (indexed docs). Page has many Embeddings (vector chunks). Chat has many Messages. Message belongs to one Company and one User (session-based).

Integration Points

Claude API for QA, Supabase for embeddings and vector search, Stripe for billing, Resend for email (optional).

V1 Scope Boundaries

V1 excludes: Slack/Discord integration, Salesforce case logging, multimodal docs (video), feedback loop for doc improvements, team collaboration on widget settings, SSO/enterprise auth.

Success Definition

A support manager finds the product via ProductHunt, adds the script tag to their docs site, sees the crawler auto-index docs, receives first chat from a customer, and upgrades to paid because support tickets dropped measurably.

Challenges

Indexing large docs sites (5,000+ pages) gets slow. Embedding drift over time requires re-crawling. False positives in QA are trust-killers. Distinguishing 'doc says X' from 'not covered in docs' is hard. Vector search quality depends heavily on embedding model and chunking strategy.

Avoid These Pitfalls

Do not index every sentence as a separate embedding — chunk by section/heading to avoid token explosion. Do not show raw similarity scores to users — always use Claude to synthesize answers. Do not assume docs never change — implement weekly re-crawl by default. Do not force users to manually map docs — auto-crawl is the whole value prop.

Security Requirements

Auth: Supabase Auth with email/Google OAuth. RLS: company_id filters all queries, users see only their company's chats. Rate limiting: 100 req/min per IP via Vercel middleware. Input validation: sanitize all doc content before embedding. GDPR: data deletion endpoint removes company data, chats, and crawl history. PII: prompt Claude to avoid logging customer emails or phone numbers from chats.

Infrastructure Plan

Hosting: Vercel (Next.js). Database: Supabase (Postgres with pgvector). CI/CD: GitHub Actions. Environments: local dev, staging (Vercel preview), prod. Monitoring: Sentry for errors, Vercel Analytics. Cost: Vercel $20, Supabase $25 (includes pgvector), Sentry $29 = $74/month. Scale: if docs exceed 10,000 pages, add dedicated pgvector instance ($100/month).

Performance Targets

Expected load at launch: 30 DAU (3 beta teams × 10 users). Chat response time target: under 3 seconds. Widget load time: under 2s (lazy-loaded iframe). Embedding generation: under 5 minutes for 300-page site. Caching: Supabase caches pgvector queries, Claude responses cached per identical question.

Go-Live Checklist

☐Crawler tested on 5 real docs sites (100–500 pages), zero missed pages confirmed
☐Embedding quality tested on 50 sample Q&As, 85%+ accuracy
☐Claude QA tested on 100 questions with citations working correctly
☐Widget tested on 3 browsers (Chrome, Firefox, Safari) and multiple doc site types
☐Stripe payment flow tested end-to-end
☐Error tracking (Sentry) live and alerts configured
☐Custom domain set up (e.g., docchat.ai) with SSL
☐Privacy policy and terms published (note: doc indexing disclosure)
☐3 beta teams tested live for 1 week, zero critical bugs
☐Rollback plan: disable crawler job, disable API
☐ProductHunt, Reddit, and direct outreach launch posts drafted.

How to build it, step by step

1. npx create-next-app docchat --typescript. 2. npm install supabase @anthropic-ai/sdk cheerio stripe pg. 3. Set up Supabase with pgvector extension, create tables (companies, doc_pages, embeddings, conversations). 4. Write /lib/doc-crawler.ts using Cheerio to fetch and parse doc site. 5. Write /lib/embedding-generator.ts using Claude API to generate embeddings for chunks. 6. Create /pages/api/crawl endpoint (user submits doc URL, crawler runs async). 7. Write /lib/claude-qa.ts with prompt for answering from docs. 8. Create /pages/api/chat endpoint (receives user query, searches embeddings, returns Claude response). 9. Build /public/widget.js as iframe loader script (users add <script> tag to their site). 10. Create /pages/dashboard for companies to see crawl status and analytics. 11. Add Stripe billing in /pages/api/stripe. 12. Deploy to Vercel and test with 1 real docs site.

Generated

March 24, 2026

Model

claude-haiku-4-5-20251001

← Back to All Ideas