7.2highGO

Promo Packet Builder

An AI-powered tool that helps engineers build and maintain their promotion case with continuous evidence collection.

DevToolsSenior engineers at large tech companies targeting staff+ promotions
The Gap

Engineers working toward promotion (esp. senior-to-staff) struggle to document impact, track project ownership, and build a compelling narrative, often losing months of work to organizational politics.

Solution

Connects to work tools (GitHub, Jira, Slack, docs) to automatically collect evidence of impact, leadership, and technical contributions. Generates promo packet drafts, identifies gaps in the case, and coaches engineers on what staff-level work looks like.

Revenue Model

Subscription $15-30/mo for individual engineers, enterprise tier for eng orgs wanting to standardize promo processes

Feasibility Scores
Pain Intensity8/10

This is a deeply emotional, high-stakes pain point. Engineers spend 1-3+ years targeting staff promotions that come with $50-150K+ comp increases. The Reddit thread (256 upvotes, 99 comments) shows real frustration. People lose promotions to politics despite strong work. The pain is acute but episodic — it peaks during promo cycles and during the months of preparation. The 'been trying to make staff for a few years' signal is telling — this is a prolonged, frustrating journey.

Market Size6/10

Narrow but valuable. ~500K-1M senior+ engineers at large tech companies in the US alone. At $20/mo avg, TAM is ~$120-240M/year for the individual tier. However, the addressable market at any given time is smaller — only a fraction are actively pursuing promotion in a given year. Enterprise tier (standardizing promo processes for eng orgs) could expand TAM significantly but is a different sales motion. This is a niche product, not a massive market — but the niche is affluent and willing to invest in career growth.

Willingness to Pay7/10

Engineers targeting staff promotions are high-income ($200-400K+) and the promotion itself is worth $50-150K+/year in additional comp. $15-30/month is trivial relative to the outcome — less than a single nice lunch. Engineers already pay for career coaching ($200-500/hour), Levels.fyi Premium, Blind Premium, and interview prep tools. The mental model of 'invest in career advancement' exists. The risk: some will feel they can DIY it with templates and ChatGPT for free.

Technical Feasibility7/10

MVP is buildable in 6-8 weeks by a strong solo dev, but integration complexity is real. GitHub API is straightforward. Jira and Slack APIs require OAuth flows and careful permissions handling. The hard part is not the integrations — it's the AI layer that meaningfully synthesizes raw signals (PRs, tickets, messages) into promotion-relevant narratives aligned to leveling rubrics. A basic version (manual input + AI narrative generation + gap analysis) is very feasible in 4 weeks. The full 'auto-collect from all tools' version is more like 8-12 weeks.

Competition Gap9/10

This is the strongest signal. No existing product combines automatic engineering signal collection, AI narrative generation, promotion rubric alignment, and individual self-serve access. Jellyfish has the integrations but serves managers. Lattice has the review process but is generic. Brag docs are manual. LLMs are powerful but have no persistent context or integrations. The white space is clear and well-defined. The risk is that Lattice/15Five could add an AI promo packet feature, but their DNA is HR/manager-facing, not engineer-facing.

Recurring Potential6/10

Promotion prep is inherently a 6-18 month journey, which supports subscription. Ongoing evidence collection and gap analysis provide continuous value. However, there's a natural churn risk: once promoted, the engineer may cancel until their next promotion cycle (2-4 years away). Mitigation: position as continuous career development, not just promo prep. Enterprise tier has stronger recurring dynamics. Realistic retention: 8-14 months per subscriber on average.

Strengths
  • +Clear white space — no product combines auto evidence collection + AI narrative generation + leveling rubric alignment for individual engineers
  • +Affluent target audience where the product cost is trivial relative to the promotion's financial impact ($50-150K+/year)
  • +Strong organic pain signals visible on Reddit, HN, and engineering blogs — people are actively struggling with this and cobbling together manual solutions
  • +The 'brag document' concept is already well-understood by the audience, reducing the need for education — this is the AI-powered version of something they already want
  • +Network effects possible: anonymized data on what successful promo packets look like at specific companies becomes a powerful moat
Risks
  • !Narrow activation window — engineers only care intensely during active promo prep, creating a feast-or-famine demand cycle and natural churn
  • !Integration permissions are sensitive — engineers may hesitate to grant access to their Slack messages, PR comments, and Jira tickets to a third-party startup, especially at security-conscious companies
  • !Enterprise IT/security teams may block OAuth integrations, limiting the auto-collection value prop to companies with permissive tool policies
  • !DIY competition from general-purpose LLMs is strong — a savvy engineer with a good prompt and a Google Doc can get 70% of the value for free
  • !Promotion processes vary wildly across companies — Google, Meta, Amazon, Stripe all have different rubrics, formats, and political dynamics, making it hard to build a one-size-fits-all product
Competition
Jellyfish

Engineering management platform that connects engineering work

Pricing: Enterprise SaaS, ~$15-30+/seat/month, custom pricing. Minimum 50+ engineers.
Gap: Built for engineering managers, not individual ICs. No promotion narrative generation, no brag doc, no self-serve for individual engineers. Cannot generate a promo packet. Way too expensive for an individual.
Lattice

People management platform with performance reviews, goals/OKRs, engagement surveys, career tracks, and compensation management. Used by 5,000+ companies.

Pricing: $6-11/person/month depending on modules, enterprise tiers higher.
Gap: Completely generic across all roles — no engineering-specific promotion criteria. No integration with GitHub/Jira/Slack. No AI-driven narrative generation. Engineer still manually writes everything. Company-purchased, not individual-accessible.
Brag Document Tools (BragDoc.io, Notion templates, Julia Evans-inspired tools)

Lightweight tools and templates for maintaining a running log of accomplishments throughout the year. Based on Julia Evans' popular 'brag document' concept. Includes BragDoc.io and dozens of Notion/Google Docs templates.

Pricing: Free to $10/month. Most are free templates or abandoned indie side projects.
Gap: 100% manual entry — no automatic signal collection from engineering tools. No AI synthesis into promotion-ready narratives. No alignment to company leveling rubrics. Just a list, not a structured packet. Most are unmaintained side projects, not real products.
15Five / Culture Amp / Leapsome

Performance management platforms with continuous feedback, 1:1 meeting tools, OKRs, engagement surveys, and review cycles. 15Five emphasizes manager-employee check-ins; Culture Amp focuses on people analytics.

Pricing: 15Five: $4-14/user/month. Culture Amp: custom enterprise. Leapsome: ~$8+/user/month.
Gap: Not engineering-specific at all. No integration with engineering tools. AI features are generic 'help me write' — not promotion-specific. Company-purchased and HR-driven. Don't understand engineering leveling rubrics or what staff-level work looks like.
ChatGPT/Claude (used manually by engineers)

Engineers already use general-purpose LLMs to help draft promotion packets, self-reviews, and peer feedback. This is the de facto 'competitor' — the DIY approach of pasting accomplishments into a chat and asking for a polished narrative.

Pricing: Free to $20/month for ChatGPT Plus or Claude Pro.
Gap: No persistent context — engineer must manually re-paste everything each session. No automatic evidence collection from work tools. No structured gap analysis against leveling criteria. No longitudinal tracking. No coaching or strategic guidance on what to work on next. Requires significant prompt engineering skill to get good results.
MVP Suggestion

Start with the simplest version that delivers immediate value: a web app where engineers manually input key accomplishments, select their current and target level, and choose their company (pre-loaded rubrics for Google, Meta, Amazon, Microsoft, Stripe). AI generates a structured promo packet draft, identifies gaps in their case against the rubric, and provides specific coaching ('You have strong technical complexity evidence but weak cross-team influence examples — here is what that looks like at staff level'). Skip integrations for MVP. Add GitHub integration as the first post-MVP feature since it has the lowest permission friction.

Monetization Path

Free tier: 1 promo packet draft with basic gap analysis, limited to 5 accomplishments. Paid individual ($20/mo): unlimited accomplishments, all company rubrics, continuous gap tracking, GitHub integration, AI coaching on what to work on next. Enterprise ($8-15/seat/mo): admin dashboard for eng managers to track team career development, standardized rubrics, aggregate analytics on promotion readiness across the org. Long-term: anonymized benchmarking data ('engineers who got promoted to staff at Google typically had X design docs and Y cross-team projects') becomes a premium data product.

Time to Revenue

4-6 weeks to MVP launch with manual input + AI narrative generation. First paying customers within 2-3 weeks of launch if marketed on Reddit/HN/Twitter engineering communities during a promotion cycle (typically Q3-Q4 at big tech). Realistic path: $1K MRR within 3 months, $5-10K MRR within 6 months if execution is strong and the product genuinely helps people get promoted (word of mouth in this community is powerful).

What people are saying
  • been trying to make staff for a few years
  • We agreed to make it the foundation of my case for a staff promotion
  • working on the project more or less solo for about nine months
  • Why does implementing a project mostly solo qualify you for a staff promotion