Heads-down senior ICs do 95% of team output but get no credit because they lack visibility with management, while less productive but more visible people get promoted
Connects to git, CI/CD, project management tools and auto-generates impact reports showing code contributions, mentoring activity, project ownership, and business outcomes — formatted for non-technical managers
Freemium — free personal dashboard, $15/mo for automated weekly reports and promotion-ready summaries, $49/mo team tier
The pain is real, deeply felt, and career-defining. Senior ICs consistently report being passed over for promotion while less productive but more visible peers advance. The Reddit thread (67 upvotes, 58 comments) shows strong resonance. Performance review season is universally dreaded. However, the pain is episodic (peaks at review time) not daily, and some ICs solve it through soft skills rather than tooling.
TAM is narrower than it appears. Target is senior ICs at companies with non-technical engineering leadership — a meaningful but specific segment. Estimated 2-4M senior ICs in the US, maybe 20-30% at companies with this dynamic, ~500K-1M addressable users. At $15/mo, that's $90M-180M TAM. Decent for a bootstrapped business, small for VC-scale. The team tier ($49/mo) could expand TAM if managers buy it as a retention tool.
This is the biggest risk. Developers are notoriously reluctant to pay for personal productivity tools (see: the graveyard of dev tools with great free tiers and terrible conversion). $15/mo is reasonable but competes with 'I could just keep a Google Doc.' The value proposition is strongest right before promotion/review cycles — usage may be highly seasonal. The team tier is more promising because companies have budgets for retention tools, but requires a different sales motion.
Git integration is straightforward (GitHub/GitLab APIs are mature). Jira/Linear integration is doable. The hard part is the AI narrative generation — turning raw metrics into compelling, manager-readable impact stories that don't feel generic. Also: correlating code changes to business outcomes requires either manual tagging or sophisticated inference. An MVP with git + project management integration and templated reports is buildable in 6-8 weeks by a solo dev. The 'magic' of great narrative generation may take longer.
This is the strongest dimension. Every tool in the $500M+ engineering analytics market is built for managers looking down. Zero automated tools exist for ICs looking up. Bragdocs.com is manual-only. The perspective flip (from surveillance to self-advocacy) is a genuine white space. However, incumbents like LinearB or Swarmia could add an 'IC view' as a feature, and GitHub/AI assistants could commoditize basic contribution summaries.
Challenging. The core value proposition (promotion-ready summaries) peaks at review cycles — typically twice a year. Weekly automated reports help justify subscription but may become background noise. Monthly active usage could be low between review cycles. To sustain subscriptions, the product needs to deliver ongoing value: weekly manager updates, 1:1 prep, or continuous career-arc tracking. Without this, expect high churn after each review season.
- +Genuinely unserved niche — no automated tool exists for IC self-advocacy despite a $500M+ adjacent market
- +Anti-surveillance positioning ('your data, your career') is a powerful differentiator that resonates with developers
- +Clear emotional trigger — being passed over for promotion while doing most of the work is a deeply felt, career-defining pain
- +Low CAC potential — the concept of 'brag documents' already has strong organic awareness in the dev community (Julia Evans, etc.)
- +Can start B2C (individual ICs) and expand to B2B (team tier as a retention/equity tool for engineering orgs)
- !Willingness to pay is unproven — developers resist paying for personal tools, and the value is episodic (review cycles), creating high seasonal churn
- !Incumbents (LinearB, Swarmia, GitHub itself) could add an IC-facing view as a feature with minimal effort since they already have the data
- !AI coding assistants (Copilot, Cursor) or AI doc tools (Notion AI) could auto-generate contribution summaries as a built-in feature, commoditizing the core offering
- !Metrics without context can be misleading or gameable — if managers distrust the reports, adoption stalls
- !The product works best when the problem is cultural (bad management), which the tool can't actually fix — risk of disappointed users who get passed over despite great reports
Engineering metrics platform connecting Git, CI/CD, and project management. Tracks DORA metrics, cycle time, PR velocity, and team-level benchmarks with workflow automation.
Engineering management platform that maps engineering work to business outcomes. Targets VP/Director level to align engineering investment with business strategy.
Engineering effectiveness platform with working agreements, investment tracking
Code-level analytics using a proprietary 'Line Impact' metric that measures meaningful code changes, discounting whitespace, auto-generated, and AI-generated code.
Simple web app and community templates
GitHub/GitLab OAuth login → pull commit history, PR reviews, and linked Jira/Linear tickets → auto-generate a formatted weekly impact summary email and a quarterly 'promotion packet' PDF. Start with git-only (no CI/CD), use GPT/Claude API for narrative generation, and provide a simple web dashboard showing contribution trends. The killer feature for MVP is: paste this into your next performance review and it's 80% done.
Free: personal dashboard with basic git stats and contribution graph → $15/mo Pro: automated weekly impact emails, quarterly promotion-ready summaries, AI-generated narratives, multi-tool integration (Jira, Linear, Slack) → $49/mo Team: manager buys for team as a retention/equity tool, aggregated team view with individual opt-in sharing, 1:1 meeting prep → Enterprise ($X/seat): SSO, compliance, org-wide deployment positioned as 'developer retention and equitable promotion infrastructure'
8-12 weeks to MVP with git integration and basic report generation. First paying users likely within 3-4 months if launched ahead of a common review cycle (Q4 or Q2). Seasonal spikes expected around performance review periods. Reaching $5K MRR could take 6-9 months given the B2C motion and developer reluctance to pay.
- “I didn't always create enough visibility for myself because I was heads-down”
- “doing ~95% of the team's output for a long time”
- “Then they hired my manager's son-in-law into the role”