FieldPath - Curated Learning Paths for Any Technical Field in 60 Seconds
Developers waste hours stitching together Google Scholar tabs, Reddit threads, and Notion docs just to onboard into a new field. FieldPath takes a topic input and spits out a structured, AI-curated reading list with summaries, community signals, and export-to-Notion — in under a minute. It's the research rabbit hole, minus the hole.
Difficulty
beginner
Category
Education
Market Demand
Very High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
⚡ YesHackathon Score
🏆 7/10
Validated by Real Pain
— seeded from real developer complaints
Developers asking how they research and onboard into new technical fields consistently report fragmented workflows — bouncing between Google Scholar, Wikipedia, Reddit, and manually curated Notion docs with no structured path tying it together. Multiple commenters expressed willingness to pay for a tool that automates this curation.
What is it?
Every developer who's tried to learn Rust, DevOps, or LLM architecture from scratch knows the pain: 14 browser tabs, 3 YouTube playlists, and a half-finished Notion doc that never gets finished. FieldPath solves this by accepting a field name and returning a tiered learning path — beginner to advanced — with AI-summarized resources, curated links, and community insight snippets pulled from Reddit and HN. Users can export the full path to Notion or PDF, share a public link, and track their progress. Built on Claude API for summarization and path structuring, with a Next.js frontend and Supabase backend, this ships fast because the core loop is literally: input -> Claude -> structured JSON -> render. Comparable to Roadmap.sh but dynamic and AI-personalized, it monetizes at $25/month with a free tier of 3 paths.
Why now?
Claude API's structured JSON output mode and the April 2026 vibe-coding wave make this a one-weekend build. Notion's API OAuth is stable and widely used, removing the last integration barrier.
- ▸Dynamic path generation: Claude structures any field into beginner, intermediate, advanced tiers in one API call.
- ▸AI resource summaries: each link gets a 2-sentence summary so users know what they're clicking into.
- ▸Notion export: one-click push of the full path to user's Notion workspace via OAuth.
- ▸Progress tracker: users check off completed resources and see completion percentage per tier.
Target Audience
Self-taught developers and career-switchers, estimated 2M+ active on r/learnprogramming and Twitter tech communities.
Example Use Case
Maya, a backend dev switching into ML, types 'MLOps' and gets a 3-tier learning path with 12 summarized resources, 4 community-validated projects, and exports it to her Notion workspace in one click.
User Stories
- ▸As a self-taught developer, I want to enter a field name and get a curated learning path instantly, so that I stop wasting hours assembling resources manually.
- ▸As a career-switcher, I want to export my learning path to Notion, so that I can track progress in the tool I already use daily.
- ▸As a paid user, I want unlimited path generation, so that I can explore multiple fields without hitting a paywall every week.
Acceptance Criteria
Path Generation: done when entering any field returns a structured 3-tier path in under 15 seconds. Notion Export: done when clicking export pushes the full path to the user's connected Notion workspace without errors. Stripe Paywall: done when free users hitting path limit 4 are redirected to Stripe checkout and gain access immediately after payment. Progress Tracking: done when checking off a resource persists across sessions and updates completion percentage visibly.
Is it worth building?
$25/month x 40 users = $1,000 MRR at month 2. $25/month x 200 users = $5,000 MRR at month 6. Math: 5% conversion on 4,000 free signups via ProductHunt and r/learnprogramming.
Unit Economics
CAC: $8 via Reddit community seeding. LTV: $225 (9 months at $25/month). Payback: 1 week. Gross margin: 88%.
Business Model
SaaS subscription
Monetization Path
Free tier: 3 paths lifetime. Paid: unlimited paths, Notion export, progress tracking, community insights layer.
Revenue Timeline
First dollar: week 2 via early beta upgrade. $1k MRR: month 3. $5k MRR: month 7.
Estimated Monthly Cost
Claude API: $35, Vercel: $20, Supabase: $25, Notion API: free, Stripe fees: $15. Total: ~$95/month at launch.
Profit Potential
Part-time viable at $2k–$5k MRR, full-time at $8k+ MRR.
Scalability
High — paths are cacheable, community layer adds UGC moat, team plans unlock B2B.
Success Metrics
Week 1: 200 signups. Week 2: 20 paid conversions. Month 2: 80% month-1 retention.
Launch & Validation Plan
Post a free path for 'Rust for backend devs' on r/learnprogramming, measure upvotes and DMs, then DM top commenters offering beta access.
Customer Acquisition Strategy
First customer: post a manually-generated sample path for LLMs on r/learnprogramming and Twitter, link to waitlist, DM the 10 most engaged commenters with free beta codes. Ongoing: ProductHunt launch, SEO on long-tail 'how to learn X' queries, weekly Twitter threads showcasing a new field path.
What's the competition?
Competition Level
Medium
Similar Products
Roadmap.sh is static and not AI-powered. Obsidian Publish lacks curation. ChatGPT can generate lists but has no structured path UI, no progress tracking, no Notion export, and no community signals.
Competitive Advantage
Roadmap.sh is static. This is dynamic, AI-personalized, and exports to Notion — the tool every dev already lives in.
Regulatory Risks
Low regulatory risk. GDPR data deletion endpoint required for EU users.
What's the roadmap?
Feature Roadmap
V1 (launch): path generation, AI summaries, Notion export, progress tracker. V2 (month 2-3): community upvotes on resources, shareable public path links. V3 (month 4+): team plans, custom path editing, API access.
Milestone Plan
Phase 1 (Week 1-2): Claude path gen + Supabase auth ships, 5 beta users onboarded. Phase 2 (Week 3-4): Notion export + Stripe billing live, first paid user. Phase 3 (Month 2): ProductHunt launch, 50 paid users target.
How do you build it?
Tech Stack
Next.js, Claude API, Notion API, Supabase, Stripe, Resend — build with Cursor for backend logic, v0 for UI components, Lovable for dashboard
Suggested Frameworks
LangChain, Supabase JS, Notion SDK
Time to Ship
2 weeks
Required Skills
Claude API prompt engineering, Next.js routing, Supabase auth, Notion API OAuth.
Resources
Anthropic docs, Notion API docs, Roadmap.sh as UX reference, Supabase quickstart.
MVP Scope
pages/index.tsx (input form), pages/path/[slug].tsx (path display), api/generate.ts (Claude call), api/export-notion.ts (Notion push), components/PathCard.tsx, components/ResourceItem.tsx, lib/supabase.ts, lib/claude.ts — all generated with Cursor + v0.
Core User Journey
Enter field name -> receive structured path in 10 seconds -> export to Notion -> upgrade to paid for unlimited paths.
Architecture Pattern
User inputs field -> Claude API generates structured JSON path -> stored in Supabase -> rendered in Next.js -> user triggers Notion API export -> Stripe gates paid features.
Data Model
User has many Paths. Path has many Resources. Resource has one AISummary. User has one ProgressRecord per Path.
Integration Points
Claude API for path generation, Notion API for export, Stripe for payments, Supabase for user data, Resend for welcome emails.
V1 Scope Boundaries
V1 excludes: team collaboration, custom path editing UI, mobile app, white-label, third-party API access, video resource integration.
Success Definition
A paying stranger Googles a learning topic, lands on FieldPath, generates a path, exports to Notion, and renews month two without any founder interaction.
Challenges
Distribution is the hardest problem — Roadmap.sh already owns SEO for 'learning roadmap' queries, so organic search won't work at launch. Must rely on community seeding in r/learnprogramming and Twitter tech circles.
Avoid These Pitfalls
Do not let Claude hallucinate resource URLs — validate every link before rendering or you'll destroy trust instantly. Do not build team features before hitting 50 solo paying users. Finding first 10 paying customers will take 3x longer than building — budget time for community seeding before writing code.
Security Requirements
Supabase Auth with Google OAuth, RLS on all user tables, 60 req/min rate limit per IP, input sanitization on field name input, GDPR data deletion endpoint required.
Infrastructure Plan
Vercel for frontend and API routes, Supabase for Postgres and auth, no file storage needed, GitHub Actions for CI, Sentry for error tracking, Vercel Analytics for traffic — total infra under $50/month at launch.
Performance Targets
100 DAU and 800 req/day at launch, Claude path generation under 8 seconds, page load under 2s LCP, CDN for static assets via Vercel edge.
Go-Live Checklist
- ☐Security audit complete
- ☐Payment flow tested end-to-end
- ☐Sentry error tracking live
- ☐Vercel Analytics dashboard configured
- ☐Custom domain with SSL set up
- ☐Privacy policy and terms published
- ☐5 beta users signed off
- ☐Rollback plan documented
- ☐ProductHunt and Reddit launch posts drafted.
How to build it, step by step
1. Run npx create-next-app fieldpath --typescript. 2. Install @supabase/supabase-js, @anthropic-ai/sdk, @notionhq/client, stripe. 3. Set up Supabase project with users and paths tables. 4. Build the path generation API route calling Claude with a structured JSON prompt. 5. Build the path display page with tier sections using v0. 6. Add Notion OAuth flow and export endpoint. 7. Add Stripe checkout for paid plan gating. 8. Add progress tracking with Supabase RLS. 9. Add Resend welcome email on signup. 10. Deploy to Vercel with env vars and test end-to-end.
Generated
April 11, 2026
Model
claude-sonnet-4-6