Founding GTM Engineer

Plato's first GTM Engineer — the person who brings RevOps to Plato as a discipline and builds the revenue engine as a product. You'll inherit real infrastructure (HubSpot, custom deal-scoring, call intelligence via Grain, company-wide AI access) but the layers underneath are still unbuilt: clean data, automated process, real forecasting rigor, AI-driven workflows. This is a team-of-one role with a direct line to the founders and a mandate to change how the revenue team works.

What you'll do

• Get the data foundation trustworthy: CRM hygiene, field governance, deduping, enrichment on create
• Automate the revenue process: lead routing, SLAs, stage criteria, clean handoffs across teams
• Build the pipeline generation stack: signal-based outbound (ICP scoring, enrichment waterfalls, orchestration)
• Bring AI into daily workflows: call-intelligence automation, research agents, health/churn scoring
• Get forecasting and reporting to a place leadership can steer from weekly
• Make sure what you ship gets used: instrument adoption, train the team, iterate

What you'll need

• Hands-on experience architecting a CRM like HubSpot from the ground up — how objects, properties, and data structure are set up
• Practical, production experience with outbound/enrichment tooling (e.g. Clay or similar)
• You've built with AI/LLMs — prompt design, agents, or AI-powered workflows — in real production work
• Strong data rigor: you can read a funnel, spot where the data is dirty, and quantify the impact of a fix before you build it
• You think in systems and sequencing, not tickets — and can defend your reasoning under real pushback

Nice to have

• Experience as an early GTM-Ops/RevOps hire at another startup
• Familiarity with Grain, Sales Navigator-style outbound tooling, or similar stack
• Comfort with unit economics (CAC, ACV, payback)
• Experience with mid-market, multi-stakeholder B2B deal cycles