SpecDrift: Product Requirements Doc vs. Shipped Feature Diff Tracker for Solo Builders

The Problem

Solo developers and indie founders on HN consistently report a painful gap between what they spec'd in Notion or a GitHub issue and what actually shipped — scope creep, mid-build pivots, and 'we changed this in Slack' decisions accumulate invisibly until a customer complains or a refactor reveals the drift. SpecDrift connects to a founder's GitHub PRs, Notion docs, and Linear tickets, then runs a weekly diff that highlights where the shipped code diverges from the original spec — flagging undocumented behavior changes, missing acceptance criteria, and features that shipped without a spec at all. This is distinct from SprintDebt (workaround log) and SpecLock/SpecDiff already in the catalog — SpecDrift is specifically about spec-to-reality divergence detection, not debt logging.

Target Audience

Solo developers and 2–5 person teams building SaaS products who write specs before building but lose track of how reality diverged from the plan

Monetization Angle

$15/mo for solo; $39/mo for teams up to 5; free tier for public GitHub repos only

Recommended Tech Stack

Why Now

The rise of AI-assisted vibe coding means developers are shipping features faster than ever, making spec-to-code drift a more acute problem — code that took a week now takes a day, and the documentation discipline hasn't kept pace.

MVP Scope

Connect one GitHub repo + one Notion doc → parse merged PRs from last 30 days → LLM compares PR description to linked Notion spec → output a simple 'matched / drifted / no spec' table per PR.

AI Angle

LLM semantic comparison between natural-language specs and PR descriptions/commit messages is the core technical unlock — without AI, this would require structured spec formats nobody actually uses.

Primary Risk

Integration surface area (GitHub + Notion + Linear) means setup friction is high enough that many solo founders will bounce before seeing value, requiring an exceptionally smooth onboarding flow.

Validation Checklist

• Post 'How do you track when your shipped code diverges from your original spec?' on HN and r/indiehackers and catalog every workaround mentioned
• Manually run the diff for 5 GitHub repos using Claude and a Notion export, share results with the owners, and ask if they'd pay $15/mo for this automatically
• Build a GitHub-only MVP (no Notion/Linear) first and validate that the diff output is useful before adding integration complexity
• Measure activation by tracking whether users who complete GitHub + Notion setup return within 7 days to check their first drift report

Who Would Pay For This

Likely buyers are engineering teams, platform leads, developer-experience teams, and technical founders. Start with Solo developers and 2–5 person teams building SaaS products who write specs before building but lose track of how reality diverged from the plan and look for teams already spending time or money on this workflow.

First 10 Users

Find the first 10 users by searching for recent complaints around "developer tools SaaS" in Hacker News, developer communities, GitHub issues, and niche Slack or Discord groups. Offer a concierge version first: manually solve the workflow for a few users, then automate only the repeated steps.

More Developer Search Paths

Why This Idea Has Legs

• Sourced from real discussions and complaints across Reddit and social media
• Cross-checked against recurring demand signals in the IdeaGenius archive
• Difficulty rated Medium — buildable by a solo developer or small team
• Clear monetization path from day one

Generate Your Full Project Spec

Get a complete blueprint for building this app — tech stack, database schema, API endpoints, go-to-market plan, and more. Generated by AI in seconds. Download as Markdown.