COMPANY SIZE: 20–500 employees, Series B–C, $5M–$50M ARR IDEAL ROLE: Design Manager, VP of Design, Head of Design, or Product Design Lead at SaaS and tech companies running design as a first-class function INDUSTRY: B2B SaaS, consumer apps, developer tools, e-commerce platforms TRIGGER SIGNALS: Design team headcount growing, moving from Sketch/Adobe to Figma, hiring design ops role, building design system at scale
POSITIONING ANGLE Don't lead with collaboration features — lead with the cost of design fragmentation at scale. When a design team grows from 3 to 15, the real cost isn't the tool, it's the hours lost to version conflicts, off-brand assets, and review cycles that happen in Slack instead of in the tool. The pitch is: make your design org a force multiplier, not a bottleneck. SUBJECT LINE Your design team is about to double — your tool stack should keep up OPENING (first 2 sentences) Noticed you're growing your design team from 5 to 12 — that's usually when Sketch files start getting messy, Figma migrations become urgent, and design system debt becomes a blocker for shipping. The teams we work with at your stage use the transition to Figma as a forcing function to build the design infrastructure (components, tokens, rituals) that lets a doubled team actually ship faster.
1. LINKEDIN: "Design Manager" or "Head of Design" hire → design function is formalizing, tooling upgrade likely 2. JOB BOARDS: "Design Systems" or "Design Ops" role listed → design infrastructure is a priority for the first time 3. TWITTER/X: Design leader posts about Sketch fatigue or "we moved to Figma" → migration intent is active 4. COMPANY BLOG: "How we built our design system" post → investment in design infrastructure is public and ongoing 5. BEHANCE/DRIBBBLE: Portfolio activity from a company showing design team growth → team is active and hiring