Engineers ship major projects but their value becomes invisible over time, especially during leadership changes or political reshuffles. When layoffs come, there's no objective record of what they delivered.
Integrates with Git, CI/CD, JIRA, and production monitoring to automatically build a living portfolio of your shipped work — including before/after metrics, system uptime improvements, deployment frequency changes, and business outcomes. Generates shareable impact reports for performance reviews or job searches.
Freemium — free tier tracks basic commits/PRs, paid tier ($12/mo) adds metric integrations, auto-generated impact narratives, and exportable portfolio
834 upvotes on that Reddit post is a strong signal. The pain is visceral and universal among senior ICs — nearly every engineer has a story about shipped work becoming invisible. However, it's episodic pain (spikes during reviews, layoffs, reorgs) not daily pain, which slightly reduces urgency to pay right now. The fear of layoffs keeps it simmering though.
~5M senior/staff engineers in US + Europe at mid-to-large companies. At $12/mo, even 1% penetration = $7.2M ARR. TAM is probably $500M-1B if you include adjacent use cases (job search portfolios, contractor proof-of-work, freelancer case studies). Not a massive market but very defensible and underserved. Could expand into manager-facing tools later.
This is the biggest risk. Engineers are notoriously resistant to paying for career tools — they'll spend $0 on career but $500 on a mechanical keyboard. $12/mo is cheap but the value is insurance-like: you pay monthly for something you need 1-2x per year (reviews, job searches). Many will think 'I should just maintain a brag doc' and never do it. Conversion from free to paid will be a grind. The bright spot: senior/staff engineers at FAANG-level comp can easily afford it and have the most to lose.
Git and GitHub/GitLab API integration is straightforward. Jira API is well-documented. The hard parts: (1) connecting production metrics (Datadog, New Relic, PagerDuty) to specific engineer contributions is genuinely difficult attribution problem, (2) generating meaningful narratives from raw data requires good LLM prompting and likely iteration, (3) enterprise security/SSO requirements will slow you down. A solo dev can build the Git+Jira MVP in 4-6 weeks, but the production metrics integration that makes this truly differentiated is more like 3-4 months.
This is the strongest dimension. Every existing tool in this space is built for managers to monitor engineers. NOBODY has built for the individual engineer to advocate for themselves. It's a complete blind spot because the buyers in enterprise are managers, not ICs. But in a B2C/prosumer model where the engineer pays, you sidestep this entirely. The brag doc is the only 'competitor' and it's a Google Doc — the bar to beat is incredibly low.
The data pipeline naturally accumulates over time, creating switching costs and increasing value — your 2-year ShipLog is worth more than a fresh one. However, active engagement may be low between review cycles. Risk of 'set it and forget it' which leads to churn when the credit card statement reminds them. Need to create regular value touchpoints — weekly digests, monthly impact summaries, alerts when metrics cross thresholds. Without active engagement features, expect high churn.
- +Massive competition gap — individual engineer advocacy is a completely unserved market while all competitors focus on management
- +Emotional resonance is off the charts — every senior engineer has felt this pain, and the Reddit engagement proves it
- +Natural data moat — the longer someone uses it, the more valuable their portfolio becomes, creating strong retention
- +LLM timing is perfect — auto-generating impact narratives from raw data was impossible 2 years ago and is now table stakes
- +Low CAC potential — this spreads virally in engineering communities (HN, Reddit, Twitter/X) because sharing impact stories is inherently social
- !Willingness to pay is unproven — engineers may love the concept and refuse to pay $12/mo for it, leading to a massive free tier that never converts
- !Enterprise security friction — connecting to company Git/Jira/CI requires OAuth or PATs that security teams may block, and engineers at paranoid orgs (banks, defense) may fear it looks like data exfiltration
- !Attribution problem is genuinely hard — linking a production metric improvement to a specific engineer's PR is an unsolved problem at scale, and incorrect attribution destroys trust
- !Episodic usage pattern — high engagement during review season and job searches, ghost town otherwise, which makes retention metrics look terrible even if the product is loved
- !If this works, GitHub/GitLab/Atlassian could build it as a feature in 6 months — you'd need strong brand and community moat before they notice
Engineering management platform that connects engineering activity to business outcomes using Git, Jira, and CI/CD data. Provides org-level visibility into engineering investment and delivery.
Developer productivity analytics platforms that measure engineering output via Git metrics — code churn, cycle time, review throughput. Gitclear specifically offers individual developer contribution scoring.
Engineering intelligence platform that visualizes coding patterns, review cycles, and team throughput from Git data.
GitHub's built-in contribution graph and profile features. Third-party tools like github-contributions-chart and resume generators that pull from GitHub activity.
The current industry-standard approach: engineers manually maintain a 'brag doc' — a Google Doc or Notion page where they log accomplishments throughout the year for performance reviews.
GitHub/GitLab OAuth integration only. Pull commits, PRs, and review data. Connect to Jira via API for ticket context. Use LLM to auto-generate weekly impact summaries and quarterly 'brag reports' with before/after framing. Skip production metrics entirely in V1 — the narrative generation from Git+Jira alone is the killer feature. Include a one-click 'Export for Performance Review' PDF. Launch on Hacker News with your own ShipLog as the demo.
Free tier: connect 1 repo, basic commit/PR timeline, monthly summary email. Paid ($12/mo): unlimited repos, Jira integration, AI-generated impact narratives, exportable PDF portfolio, custom branding. Future premium ($25/mo): production metric integrations (Datadog, PagerDuty), team-level reports for tech leads, interview prep mode that turns your portfolio into STAR-format answers. Enterprise ($): company-wide deployment where managers can see team ShipLogs (only with engineer consent — trust is the brand).
8-12 weeks to MVP launch, 12-16 weeks to first paying customer. The long pole is not building it — it's getting engineers to connect their work repos and trust you with the data. A viral HN launch could compress this significantly. First $1K MRR likely in 4-6 months.
- “once the fires are out, your value becomes invisible to everyone except the people who remember what it was like before”
- “I shipped three major projects... All three went to production, all three still running as far as I know”
- “How you do things and the sacrifices you made do not really matter, when a new manager comes, you are the old stuff”
- “career paths are more about the friends you make along the way rather than delivering value to the company”