lodgify - Director of Retention & Monetisation

• The "Builder" Mindset: Your default mode is to build a prototype, not a slide deck. You get frustrated by slow feedback loops and use AI tools (n8n, Zapier, Claude, etc.) to break them. • The "Builder" Mindset: • Hard Requirement: You haven’t just "used" AI; you have shipped an AI-native automation or workflow that is currently in production. • Hard Requirement: • Monetization Fluency: You understand value metrics, tier design, and willingness-to-pay research. You can talk NRR and LTV with a CFO, and "API architecture" with a CTO. • Monetization Fluency: • Technical Stack: Expertise in CRM orchestration (HubSpot/Braze), product analytics (Amplitude/Mixpanel), and SQL. You pull your own data; you don’t wait for a ticket. • Technical Stack: • Statistical Rigor: You understand ICE prioritization, cohort analysis, and statistical significance. You know when a result is a signal and when it’s just noise. • Statistical Rigor: • ⭐ The First 6 Months • Month 1 — Audit & Ship: Complete a full CRM debt audit and ship your first monetization experiment. Deliver one tangible AI automation into the hands of your team. • Month 1 — Audit & Ship: • Month 3 — Compound: Live behavioral segmentation is active. Your first AI agent is in production. You've delivered a concrete recommendation on team structure and talent gaps to the CGO. • Month 3 — Compound: • Month 6 — The Engine is Humming: Experimentation velocity has tripled. Retention, CRM, and Monetization are a single integrated system where signals in one automatically inform the others. NRR is measurably improving. • Month 6 — The Engine is Humming: • ⭐ What makes this hard (and why it’s exciting)! • The Player-Coach Paradox: You must lead two squads while simultaneously acting as the IC lead for monetization. You aren't just a manager; you are a builder. • The Player-Coach Paradox: • High-Volume, Low-ACV: With ~1,000 new customers a month, you can’t "white glove" your way to retention. This is a systems and architecture problem that requires scale-thinking. • High-Volume, Low-ACV: • No Playbook: We are defining what an AI-native growth org looks like. You’ll be building the plane while flying it, often influencing cross-functional teams (Product/Data) without direct authority. • No Playbook: • The Clock is Running: We are at a critical scaling inflection point. The decisions you make on pricing and retention in the next 12 months will define the company’s trajectory for the next 5 years. • The Clock is Running: