sh-notion/notion_data_team_no_files/2025-02-12 - Data Planning 1970446ff9c980039759e389ac07cae9.md
Pablo Martin a256b48b01 pages
2025-07-11 16:15:17 +02:00

41 lines
No EOL
2.8 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 2025-02-12 - Data Planning
### General Updates
- Joaquin off on Monday 17th + Uri off on Friday 21st
### Done
- Other - Re-implement [Superhog Reporting](https://app.powerbi.com/groups/me/apps/86bd5a07-0cd9-40ab-9e97-71816e3467e8/reports/fe54c090-ae85-4cfd-9f28-3d31ab486bc3/dfc2fe95ee1672c1bbdc?experience=power-bi) reading from DWH
- KPIs - Propose Billable Booking KPI definition for New Dash: Agreed with Suzannah on 2 metric definition
- KPIs - Rework Cancellation rates (attribute them to Check-out + ratio)
- KPIs - [First draft of Main KPIs - Overview](https://app.powerbi.com/groups/me/apps/33e55130-3a65-4fe8-86f2-11979fb2258a/reports/5ceb1ad4-5b87-470b-806d-59ea0b8f2661/50c56def523c2003b054?experience=power-bi)
- Ad hoc requests - several completed on Finance/RevOps side
- Invoicing Incident finally closed after Post Mortem
### In Progress
- KPIs - New Dash vs. Old Dash (vs. API) category
- Product/RevOps - Include a user adoption funnel per service for New Dash, to identify adoption/upsell possibilities
- Guests - Start discussing on the implementation for Guest Products and Single Payment - Multi Service refactor. Likely work to start soon.
### Stopped / No advancement
- KPIs/New Dash/AM reporting - Exclude known test accounts to increase data quality (wont remove all of them) - Engineering to built it properly for us to exclude it properly
- Finance - Screen and Protect API reporting for invoicing purposes (currently stopped since theres no clients)
- Other - Excel tips and best practices documentation (no advancements, low prio)
### To Do (does not include critical subjects)
- KPIs - Implement Billable Booking KPI for new dash after definition
- KPIs - Rework Main KPIs overview (YTD+MTD)
- Might need creation of APIs KPIs (for Bookings mostly)
- Resolutions - Ingest Resolution Centre Data into DWH
- Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price + Deal id
- Resolutions - DWH modelling
- 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 its valuable for further client understanding