# 2025-03-12 - Data Planning

## General Updates

- Performance review - how is it going to happen?

### Done

- Guests - Further discussion on the implementation for Guest Products and Single Payment - Multi Service refactor.
- RevOps - Churn tracking - automate manual monthly Churn reports and enhance it with other data (revenue last 12 m, etc) - Report available [here](https://app.powerbi.com/groups/me/apps/bb1a782f-cccc-4427-ab1a-efc207d49b62/reports/d4955aad-1550-46c7-9549-2bdeebb99286/3555842421d87b032c4e?experience=power-bi)
- RevOps - Churn prevention - display last time account was contacted
- RevOps - Account Management - Include API/Platform Deal category
- Bugfixes - Active PMS & New Dash offered services
- Other - Slides for TMT Data deep-dive
- Other - General support
    - Support Finance on Invoicing subjects
    - Follow up HTVR
    - Follow up data drift due to user migration old dash → new dash - We loose history on Price Plans…
    - Couple of data quality alerts
    - Other Data Captain ad-hoc requests as usual

### In Progress

- TMT - Targets for FY2026
    - Adapt based on Financial model almost ready - no stretch. Concern on Billable Bookings/Live Deals figure
    - Data quality improvements in PBI
        - Deal metrics to align with RevOps KPIs
        - Platform Billable Bookings (est.) - Understand if there’s better ways to track this figure
    - We need to adapt the metric names on PBI to align with Finance’s naming. I agree, but it requires quite a bit of work.
- RevOps - Churn prevention - forecast created bookings per account to the end of the month and alert if there’s a decrease. Booking projection needed for Revenue projection too.
- Product - Guest Journey New Illustrations A/B test monitoring ongoing (launched 25th Feb) - Looking very good
- Product - Guest Products - Single Payment / Multi Service refactor
    - DWH modelling
    - Old Dash Waiver Extracts for invoicing purposes
- Other - Excel training session (scheduled for today)
- Other - Power BI Truvi Rebranding - rest of reports (low prio)

### Stopped / No advancement

- 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
- RevOps - Update automation project backbone data - Need further input
- Finance/Resolutions - Automate manual tasks for Finance (waiting for specs)

### To Do (does not include critical subjects)

- ~~Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price + Deal id~~ Discussed with Nathan, no longer needed.
- RevOps (Kayla) - Churn prevention: alerting system if user had a PMS and no longer has it
- Idea - Improvements on AM reports
    - Rework Score so it captures projected revenue rather than last month revenue (i.e., gain ~1 month trend visibility). In other words - be able as of 1st of March to detect that February was bad for HTVR, instead of 1st of April as is now.
    - Add a per Account Manager “welcome” page with the main indicators / alerts of the accounts per Account Manager.
    - Include Price Plans / Offering - New Dash vs. Old Dash
    - Include rank and share per Revenue Retained Post Resolutions
- API KPIs
    - We need at least bookings to compute Total Bookings (Platform Billable Bookings + API Bookings)
- Idea - Resolutions KPIs
    - Blocked - We need to capture all Resolutions to be able to build proper metrics
    - Modelling KPIs data
    - Main KPIs exposure
    - Specific 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 (Alex) - Client Cohorts - explore retention + key metrics to understand if it’s valuable for further client understanding
- RevOps (Alex) - RevOps KPIs - Automate RevOps KPIs sheet in PBI and add additional content (revenue, etc). Similar approach as for Churn.
- Product (Daga) - New Dash - Differentiate OSL/Manual/PMS bookings
- Idea - Guest Journey A/B test report
    - Avoid manual runs on Data side
    - Provide deeper level of detail