Engineers — especially solo practitioners — fail to document and advocate for their own contributions, leading to denied promotions and undervaluation despite strong output
Connects to Git, ticketing systems, cloud dashboards, and on-call tools to continuously build a structured accomplishments log with quantified impact. Generates promotion packets and 1:1 prep docs on demand
Freemium — free basic log, $10/mo for AI-generated narratives, promotion packet templates, and manager-facing summaries
The pain is real and emotionally charged — denied promotions, feeling undervalued, comp stagnation. The Reddit post you cited is textbook: an engineer with 3 years of solo output getting called 'junior-level.' This pain directly costs people $20-50K+ in missed promotions. However, it's episodic (peaks around review cycles) not daily, which slightly reduces urgency to adopt a continuous tool.
~5M professional software engineers in the US, maybe 25M globally. The acute target is ICs at mid-to-senior level preparing for promotion — roughly 30-40% of that base at any given time. At $10/mo that's a theoretical TAM of $150-500M. But willingness to pay for career tools with personal funds is historically low. Realistic serviceable market is much smaller — maybe $10-30M. This is a solid niche, not a venture-scale market.
This is the biggest risk. Engineers are notoriously reluctant to pay for career/soft-skill tools with their own money. They'll drop $20/mo on a JetBrains IDE but resist $10/mo for self-advocacy. The value is real but abstract — 'maybe this helps my next promo' vs 'this makes my code compile.' Conversion to paid will require nailing the 'aha moment' — likely the first generated promotion packet. Expense reimbursement through L&D budgets could help but adds sales friction.
Git and GitHub API integration is straightforward. Jira/Linear APIs are well-documented. The hard parts: (1) Transforming raw activity into meaningful narratives requires good prompt engineering and context-awareness — a commit message like 'fix bug' needs enrichment. (2) Understanding impact (not just activity) requires correlating across systems. (3) OAuth flows for multiple integrations add onboarding friction. A solo dev can build a solid Git+Jira MVP in 6-8 weeks, but the AI narrative quality will make or break the product and needs ongoing iteration.
This is the strongest signal. Nobody is doing this for the individual IC engineer. Enterprise analytics tools serve managers. HR tools have blank text boxes. Templates are manual. There is a clear, unoccupied product gap between 'raw engineering activity data' and 'promotion-ready narrative.' The concept is validated by the cultural momentum of brag docs but nobody has automated it. First-mover advantage is real here.
The continuous logging aspect supports subscription, but the core value spikes around review cycles (typically 2x/year). Risk of subscribe-generate-cancel pattern. To drive retention: weekly email digests of accomplishments, 1:1 prep docs, manager-facing dashboards, and team features. Without these, expect high churn between review seasons. Annual billing with a discount could mitigate.
- +Massive competition gap — nobody automates brag docs for individual ICs despite the concept being mainstream in engineering culture
- +Emotionally resonant pain point with real financial consequences ($20-50K+ in missed promotions)
- +AI narrative generation is a genuine 10x improvement over manual documentation — this is the right moment for this product
- +Low-cost distribution via engineering communities (Hacker News, Reddit, Twitter/X engineering) where this exact pain is discussed daily
- +Natural viral loop — engineers who get promoted will credit the tool, and promotion packets are shared with managers who see the output
- !Willingness-to-pay risk: engineers may love it free but resist paying $10/mo for a career tool — conversion could be painfully low
- !Seasonal churn: value spikes around review cycles, leading to subscribe-cancel-resubscribe pattern that kills MRR predictability
- !Narrative quality bar is extremely high: a generated promotion packet that sounds generic or robotic will destroy trust instantly — this needs to be shockingly good
- !Integration onboarding friction: asking users to OAuth into Git + Jira + PagerDuty + AWS before seeing value creates a cold-start problem
- !Platform risk: GitHub Copilot, Atlassian, or Lattice could add 'auto-generated self-review' as a feature and instantly own the distribution
Engineering analytics platforms that connect to Git, Jira, CI/CD to measure developer productivity with dashboards for engineering leaders
Julia Evans' popular 'brag document' template and various Notion/Google Docs templates that engineers manually fill in to track accomplishments
Calendar and time management tools that auto-categorize how engineers spend their time across meetings, focus work, and collaboration
GitClear analyzes Git activity to produce developer contribution metrics like code churn, impact scores, and commit summaries. GitHub Copilot Workspace summarizes PRs
HR performance management platforms where employees write self-reviews, set goals, and get manager feedback during review cycles
GitHub-only integration (skip Jira/infra for v1). User connects GitHub, selects a time range, and gets an AI-generated accomplishments summary grouped by theme (features shipped, bugs fixed, code reviews, team contributions). One-click export to Google Docs. The magic moment is: connect GitHub → see 6 months of your work beautifully summarized in 60 seconds. Add Jira/Linear in v2 once you validate people actually use and pay for the core narrative generation.
Free: GitHub-connected activity log with basic weekly summaries (this is the hook — let them see their own data) → $10/mo Pro: AI-generated promotion narratives, 1:1 prep docs, impact quantification, multiple integrations (Jira, PagerDuty, etc.) → $20/mo Teams: Manager-facing summaries, team accomplishment dashboards, review cycle sync (this is where the real money is — selling to eng managers who want their whole team using it) → Enterprise: SSO, compliance, integration with Lattice/Culture Amp for direct self-review population
8-12 weeks to MVP with GitHub integration, another 4 weeks to polish AI narratives. First paying users within 3-4 months if you launch on Hacker News / engineering Twitter with a compelling 'I built my promotion packet in 60 seconds' demo. Expect slow initial conversion (1-3% free-to-paid) until narrative quality is exceptional. Could hit $1K MRR within 6 months with aggressive community marketing timed to promotion cycle seasons (typically Q4 and Q1).
- “4-5 months ago I asked for a promotion from senior title to staff title”
- “he said he cant give me promotion”
- “this week he set a meeting and started that my outputs are like a junior”
- “3 years of solo experience usually equates to a significant wage increase when switching”