COMPANY SIZE: 50–500 employees, Series A–C, $5M–$50M ARR IDEAL ROLE: Head of Operations, Chief of Staff, RevOps Manager, or IT/Ops Lead who owns internal tooling INDUSTRY: B2B SaaS, professional services, remote-first tech companies TRIGGER SIGNALS: Company recently went remote or hybrid, scaling headcount rapidly, existing wiki/docs scattered across 3+ tools
POSITIONING ANGLE Don't lead with features — lead with the operational cost of having knowledge in 4 places. Ops leads feel this daily. The pitch isn't "better docs," it's "one place where new hires can actually find what they need on day one without asking a senior employee." SUBJECT LINE Your onboarding doc is probably 4 tools wide right now OPENING (first 2 sentences) Noticed your headcount doubled last quarter — which usually means onboarding documentation is somewhere between Confluence, a shared Drive, and Slack channels nobody can find. The teams we work with at your stage say new hire time-to-productivity drops by 30% when they consolidate into a single connected workspace.
1. LINKEDIN: "Operations" or "Systems" hire posted → company investing in ops infrastructure for the first time 2. JOB BOARDS: Multiple job postings mention different internal tools (Confluence, Asana, Jira, Google Drive) → tool sprawl is visible externally 3. COMPANY BLOG: Post about remote work challenges, onboarding issues, or "how we run X" → operationalizing their own process publicly 4. TWITTER/X: CTO or ops lead vents about tribal knowledge or "stuff in people's heads" → active pain being voiced 5. CRUNCHBASE/TECHCRUNCH: Series B+ announced with remote team growth angle → ops infrastructure investment typically follows funding