2025-01-29 - Data Planning

Start weekly syncs with Guy / Finance on KPIs - Suzannah
Engineering - Ingestion of backend data to billing db
- Data POV: It’s supposed to be carried out on Engineering side.
- Engineering POV: It’s supposed to be carried out in Data side.
- Pending discussion to clarify Uri x Ben on Wed 29th
- Uri’s POV: This is a Engineering architectural decision and implementation. This is a big no-no on our side, specially if Pablo is not here. It would take me several days, for a not robust implementation, for a critical project as invoicing - and we already had some issues on this regard. Might need your support on this.

January invoicing incident resolution - Incident Report
Bugfix - Guest KPIs reporting has a strange connectivity issue - Incident Report
Finance - Check in Hero API reporting for invoicing purposes - Link
KPIs/RevOps (Chloe) - Track Revenue Retained ratios in Main KPIs for graphical display over time
Guesty Invoicing - Data quality issues misunderstanding for invoicing on Finance/APIs side
Other - Fix Data Request workflow
Guest Squad - A/B test mess fixed + retrospect upon - Post mortem here
Data - Fixed alerts that failed on Jan 29th

Guesty - Resolutions payouts analysis
KPIs - Rework Onboarding MRR (avg per client + actual revenue expected)
Finance - Accounting aggregations reporting → This goes in line with improving Revenue accuracy in KPIs
Other - Understand Booking Fees / Cancelled Bookings decay in Dec 2024
KPIs - Propose Billable Booking KPI definition for New Dash: 1 Booking can have multiple services invoiced in different times, how do we attribute them?
Finance - Screen and Protect API reporting for invoicing purposes (currently stopped since there’s no clients)
Other - Discontinue Superhog Reporting (legacy Power BI)
Other - Excel tips and best practices documentation (low prio)

KPIs - Implement Billable Booking KPI for new dash after definition
KPIs - Rework Revenue display in Main KPIs
KPIs - OKR, target-based reporting
KPIs - New Dash vs. Old Dash category
Product/RevOps - Include a user adoption funnel per service for New Dash, to identify adoption/upsell possibilities
Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price
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)