COMPANY SIZE: 5–500 employees, Seed–Series C, $500K–$50M ARR IDEAL ROLE: Software Engineer, Senior Engineer, Engineering Manager, or CTO at product-led SaaS companies where engineering velocity is a direct competitive advantage INDUSTRY: Developer tools, B2B SaaS, AI-native startups, any company shipping software with a lean eng team TRIGGER SIGNALS: Engineering team under headcount pressure, recently cut eng team size, writing velocity is a bottleneck, new engineering manager trying to increase team output
POSITIONING ANGLE Don't pitch an "AI tool" — pitch recovered engineering hours. Engineering managers and CTOs at lean teams aren't buying software; they're buying capacity. The frame is: what would you do with 30% more engineering output this quarter without hiring? Lead with the throughput story, not the AI features. SUBJECT LINE 30% more output from the same eng team — what would you ship first? OPENING (first 2 sentences) Noticed your team just shipped X features with a 6-person eng org — that's the exact inflection point where AI-assisted development stops being a nice-to-have and starts being a force multiplier. Teams at your stage typically see a 25–40% reduction in time-to-PR for new features within the first two weeks, which compounds fast when your roadmap is measured in sprints not quarters.
1. LINKEDIN: "Senior Engineer" or "Staff Engineer" hire with "AI tools" mentioned in JD → normalizing AI coding workflow 2. JOB BOARDS: Eng team posting for roles where "familiarity with AI coding assistants" is listed → team already evaluating tooling 3. TWITTER/X: Developer or CTO tweets a Cursor or Copilot workflow tip, thread, or result → active user and potential champion 4. GITHUB: Commit frequency increase on a small team → productivity spike often correlates with AI tooling adoption 5. COMPANY BLOG: "How we ship fast with a small team" post → velocity-at-scale story usually reveals the tooling stack