2025-02-19 - Data Planning

KPIs - New Dash vs. Old Dash (vs. API) category (Main KPIs report)
KPIs - Implement Live Deals (Main KPIs report)
KPIs - Implement Billable Booking KPI for new dash after definition (Main KPIs report)
Product/RevOps - Include a user adoption funnel per service for New Dash, to identify adoption/upsell possibilities (New Dash - Offered Services report)
Ad hoc requests, specially on Home Team Vacations Rentals (Kayla) → Risk of losing Booking fees after decrease from 10 USD to 6 USD
Guests - Align for Illustrations A/B test launching next week
Resolutions - Ingest Resolution Centre Data into DWH
Data internal - Fixed CPU consumption
Data internal - Fixed New Dash Reporting being down after release

Finance - Screen and Protect API reporting for invoicing purposes
Other - Excel tips and best practices documentation (reviewed) - How do you want to proceed? Share resources and/or schedule session? → Session + Resources
KPIs - Main KPIs overview (YTD+MTD) - First partial delivery

KPIs/New Dash/AM reporting - Exclude known test accounts to increase data quality (won’t remove all of them) - Engineering to built it properly for us to exclude it properly
Guests - Start discussing on the implementation for Guest Products and Single Payment - Multi Service refactor. (No further news)

Report to support Pass The Keys migration to New Dash
Resolutions - DWH modelling
KPIs - Main KPIs overview (YTD+MTD) - Second delivery
- Creation of APIs KPIs (for Bookings mostly)
- Revenue Churn & MRR metrics
- Targets
Guests - Adapt A/B test monitoring with specs of Illustrations A/B test
Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price + Deal id
Resolutions - Reporting
Invoicing Incident - Further automation improvements: Xero (for source of truth in actual invoiced amount) + Hubspot (for churn/onboarding/AM info) + Backend (for what we should have invoiced, New Dash mostly)
KPIs - Payment Count and Average Amount per Payment Count (Waiver/Deposit Fee/etc)
RevOps (Kayla) - Churn prevention: alerting system if user had a PMS and no longer has it, if recent created bookings per account is decreasing, display last time account was contacted. This could be potentially the first step towards a “Account Manager KPIs” for AM teams
RevOps (Kayla) - Churn tracking: see if we can automate manual monthly Churn reports and enhance it with other data (revenue last 12 m, etc)
RevOps (Alex) - Client Cohorts: explore retention + key metrics to understand if it’s valuable for further client understanding