
Nº 02/Revenue Operations
GTM Automation Lead
- Team
- Revenue Operations
- Location
- Paris
- Type
- Full-time
- Reports to
- VP of Sales
The builder behind Scenario's commercial engine. You take our solid foundation, a modern CRM, Stripe billing, Clay for enrichment and the usual workspace tools, and scale it into a self-updating, self-growing system. You own the CRM and the revenue-operations layer: custom enterprise plans, reconciled revenue dashboards, and every automation that makes the sales team faster. A deeply AI-native operator who pairs daily with the VP of Sales so people spend their time on judgment, not data entry.
01 Mission
- Keep a live, accurate map of the commercial world: people, companies and buying signals captured automatically.
- Expand the automation layer using AI agents and orchestration tools, all documented and version-controlled.
- Own billing as a commercial system: custom enterprise plans, recurring-revenue dashboards, and full reconciliation between billing and the CRM.
- Ship AI agents for prospecting, enrichment, expansion and churn-risk, with reliability as the first priority.
- Hold the line on pipeline hygiene with the VP of Sales, and feed structured signal to product and marketing as the customer base diversifies beyond gaming.
02 Scope of ownership
Owns
- The CRM as a product: data model, automations and integrations
- Billing as a commercial system: custom plans, revenue reporting and reconciliation
- Sales reporting and dashboards, including the board-ready view, generated from the system
- AI agents, data enrichment and the relationship graph
Does not own
- Deal strategy or quotas (Sales)
- Which accounts we chase: Sales sets the profile and tier
- Customer-facing documentation (Knowledge Architect)
- The product roadmap
03 What we look for
- A revenue-operations or GTM-engineering background. You have built sequences, lead scoring and enrichment pipelines.
- Deep fluency with modern CRMs: you can critique our actual setup live in the interview.
- Billing and Stripe literacy. You build something working in the interview, such as a churn-signal or custom-plan tool.
- Engineering discipline: documentation, runbooks and versioning as a habit.
04 Disqualifiers
- An "I'll brief an engineer for that" mindset.
- No-code-only, with no real engineering instinct.
- Wants to rebuild what already works rather than scale it.
- Treats the role as IT support for Sales; ships tickets, not systems.
05 How we hire2-3 weeks
- 01Intro call30 min
- 02Product session60 min
- 03Build live60-90 min
- 04Written POVAsync, 48h
- 05ReferencesParallel
- 06Founder conversation45 min