COMPANY SIZE: 20–500 employees, Series A–C, $3M–$50M ARR IDEAL ROLE: Operations Manager, RevOps Lead, PMO, or Marketing Ops Manager at SaaS companies that use Airtable or are evaluating relational database tools INDUSTRY: B2B SaaS, marketing agencies, operations consulting, creative and media companies TRIGGER SIGNALS: Company using Airtable at scale and hitting limits, migrating from spreadsheets to relational tools, building project tracker or CRM, ops team needs more flexibility than Notion or Asana
POSITIONING ANGLE Don't sell a spreadsheet — sell a relational operating system for ops teams. Airtable users are usually past spreadsheets and into "this is becoming our ops backbone." The pitch is about the jump from "personal database" to "team-wide ops system" — data integrity, automation, and cross-functional visibility at scale. SUBJECT LINE Your Airtable setup probably breaks when your whole team needs it OPENING (first 2 sentences) Noticed you've been building in Airtable for a while — the transition from "personal tool" to "team-wide ops system" is where most users hit friction. The teams we work with at your stage say Airtable's automation limits and sync issues start showing up exactly when 10+ people need consistent data at once.
1. LINKEDIN: "Airtable Pro" user posts about scaling usage → high intent, expansion conversation is timely 2. JOB BOARDS: "Airtable" mentioned in RevOps or Operations job description → team is standardizing on the tool 3. TWITTER/X: "Airtable is getting too complex" or "we outgrew Airtable" → migration signal, alternative evaluation window 4. COMPANY BLOG: "How we run our operations in Airtable" → public investment in the tool, potential champion identification 5. GITHUB: Sync scripts or API integrations with Airtable → advanced usage, enterprise expansion signal