Engineers lose promotion opportunities because they can't recall or articulate months of accumulated work when review season arrives, and managers default to recency bias or salary-based judgments.
Runs in the background, pulling commits, PRs, deploys, incident responses, and ticket completions into a structured achievement log. Before reviews, generates a polished self-assessment document with quantified impact statements.
Freemium — free basic log, $8-15/mo for AI-generated summaries, promotion-ready docs, and manager-facing reports
This is a genuine, recurring pain felt by millions of engineers every 6-12 months. The consequences are real — missed promotions worth $20-50k+ in compensation. Engineers universally acknowledge they should keep a brag doc but almost nobody actually does it consistently. The pain is acute during review season and chronic the rest of the year (guilt of not tracking). Reddit threads about promotion frustration are extremely common and emotional.
~30M professional software developers globally, ~5-8M in the US. Target is IC engineers at companies with formal review cycles (Series B+ startups and enterprises), likely 3-5M addressable. At $10/mo average, TAM is ~$360-600M/year. Not a billion-dollar market as a standalone tool, but very healthy for a bootstrapped or small-team SaaS. Could expand to PMs, designers, data scientists.
Mixed signal. Engineers are notoriously reluctant to pay for personal productivity tools (they'll build their own or use free alternatives). BUT: this is tied to a $20-50k+ promotion outcome, so the ROI framing is strong. $8-15/mo is impulse pricing for someone earning $150k+. Risk: seasonal usage — people may only want it 1-2 months before reviews, leading to high churn. The strongest WTP signal will come from engineers who just got burned in a review cycle.
Very buildable as an MVP. Git and Jira APIs are well-documented. OAuth flows for GitHub/GitLab/Bitbucket are standard. LLM APIs (Claude/GPT) handle the narrative generation. MVP scope: connect GitHub + Jira, pull last 6 months of data, generate a structured brag doc with AI. A solo dev with API experience can ship this in 4-6 weeks. Complexity increases with more integrations (PagerDuty, Datadog, Slack, etc.) but MVP doesn't need them.
This is the strongest signal. Nobody owns the 'IC engineer self-advocacy' space. Jellyfish/Pluralsight serve managers. Lattice/CultureAmp serve HR. Julia Evans' template is manual. There is genuinely no automated tool that pulls engineering data and generates a promotion-ready narrative for the individual engineer. The gap is clear and the reason it exists is that companies buy tools for managers, not for ICs — meaning this must be a bottoms-up, IC-purchased product.
This is the biggest concern. The core value proposition is seasonal — reviews happen 1-2x per year. Engineers may subscribe for 1-2 months, export their doc, and cancel. To justify year-round subscription: weekly/monthly achievement digests, 1:1 prep docs, continuous career narrative, LinkedIn post drafts, or a 'career portfolio' angle. Without solving the seasonality problem, expect high monthly churn and consider annual pricing or a per-generation model instead.
- +Clear competition gap — no one owns the IC self-advocacy automation space
- +High pain intensity tied to real financial outcomes ($20-50k+ promotion impact)
- +Strong cultural tailwind — 'brag doc' is now mainstream engineering vocabulary
- +Technically straightforward MVP with well-documented APIs
- +Low price point ($8-15/mo) relative to buyer income ($150k+) makes conversion easier
- +Bottoms-up adoption model — no enterprise sales needed to start
- !Seasonal usage pattern could cause extreme churn — engineers may only need this 1-2 months per year, making MRR unstable
- !Engineers are DIY-oriented and may build their own scripts rather than pay, especially after seeing the concept
- !GitHub Copilot or similar AI tools could add 'summarize my work' as a free feature, commoditizing the core value prop overnight
- !Data sensitivity — engineers may hesitate to grant OAuth access to their company's Git and Jira to a third-party startup
- !Company IT/security teams may block OAuth integrations, limiting adoption at larger enterprises where the pain is greatest
Engineering management platform that connects Git, Jira, and CI/CD data to show engineering investment, team performance, and business alignment. Primarily targets engineering leaders, not ICs.
Popular open-source template/concept where engineers manually maintain a running document of accomplishments. Popularized by Julia Evans' blog post. Google Docs or Notion templates.
Developer analytics platform that tracks code-level metrics like commit frequency, review cycles, and rework rates from Git data.
Performance management platforms that handle review cycles, goal tracking, 1:1s, and engagement surveys for HR/People teams.
Tools like GitHub Wrapped, git-stats, or contrib-readme that generate visual summaries of your GitHub activity over a time period.
Web app with GitHub OAuth + Jira OAuth. User connects accounts, selects a time range (last 3/6/12 months), and the app pulls PRs, commits, code reviews, and Jira tickets. AI generates a structured brag doc with sections: Key Projects, Technical Impact, Collaboration & Leadership, Quantified Metrics. User can edit, export to Google Docs/PDF. No background daemon needed for MVP — on-demand generation is sufficient and avoids the always-running complexity. Add a 'review season reminder' email to re-engage churned users.
Free tier: connect 1 repo, generate 1 brag doc per quarter with basic formatting. Paid ($12/mo or $99/year): unlimited repos, Jira integration, AI-powered impact quantification, manager-facing summary, multiple export formats, weekly achievement digest emails. Scale: team plans where managers can see aggregated team achievements ($25/seat/mo), API for integration into existing review platforms (Lattice, Culture Amp).
6-8 weeks to MVP launch, 8-12 weeks to first paying customer. Revenue will spike around common review seasons (Q4 for calendar-year companies, Q2 for fiscal-year companies). Expect $1-5k MRR within 6 months if marketed well on dev Twitter/Reddit/HN. Key growth hack: generate a free 'preview' brag doc that's impressive enough to convert, gated behind paywall for full version and ongoing tracking.
- “4-5 months ago I asked for a promotion from senior title to staff title”
- “he started to his sentence with expectations from high salary like you”
- “3 years of solo experience usually equates to a significant wage increase when switching”