SourceDocs.ai — I got tired of writing READMEs, so I built an AI to do it
Hey IH! 👋
Launching my latest project today: SourceDocs.ai
The problem: Every side project I start, the README is either embarrassingly bare or something I keep putting off until "later." And let's be honest — later never comes.
The solution: Paste a GitHub URL, get a professional README in seconds. Plus CHANGELOG, CONTRIBUTING, LICENSE, and CODE_OF_CONDUCT if you need them.
How it works:
- AI scans your repo — file structure, package.json, code patterns
- Generates documentation that actually reflects what your project does
- Outputs clean markdown with proper badges and formatting
The tech behind it:
- Next.js + Vercel for the frontend
- Supabase for auth and data
- Claude AI for generation
- Stripe for payments
Business model:
- 1 free doc generation per month
- Web Pro: $8/mo for unlimited web generations
- API Pro: $15/mo for 100 API calls
- Bundle: $20/mo for both
I'm a solo founder building this in public. Revenue so far: $0. Users so far: just me testing obsessively.
Looking for brutally honest feedback:
- Would you actually use this?
- What's missing that would make you pay for it?
- Is the pricing way off?
Check it out: https://www.sourcedocs.ai
Thanks for reading — happy to answer any questions about the build!
Hey IH! 👋
Quick update on SourceDocs, the AI documentation tool I've been building. Just shipped v1.0.3 with two major features:
1. Class Diagram Generation
You paste a GitHub URL, and it generates a Mermaid class diagram showing your code's structure. Classes, interfaces, inheritance, composition - all visualized and ready to embed in your README.
This took about 2 days to build end-to-end. The hardest part wasn't the AI generation - it was figuring out which files to analyze in large repos. I ended up building a priority scoring system based on directory patterns and file naming conventions.
2. One-Click PR Creation
This is the feature I'm most excited about. Instead of copying the generated docs and manually creating a PR, you just click "Create PR" and SourceDocs:
- Creates a branch
- Commits the file
- Opens the PR
- Gives you the link
It sounds simple, but this is the kind of "last mile" automation that turns a utility into a workflow tool.
The numbers (being transparent):
- Users: 1 (signed up but hasn't generated yet 😅)
- Revenue: $0
- MRR: $0
- Time invested: ~3 months part-time
What I'm trying next:
I'm doing a soft launch this week - Reddit, Twitter, here on IH. Want to get real user feedback before attempting Product Hunt or HN.
Questions for the community:
1. How do you get your first 10 paying customers for a developer tool?
2. Is $8/month too much? Too little?
3. Would you use this? Why or why not?
Appreciate any feedback, even harsh criticism. Building in public means being open to it!