sh-notion/notion_data_team_no_files/2025-02-05 - Data Planning 1910446ff9c9803b8885da35ba2d9b71.md
Pablo Martin a256b48b01 pages
2025-07-11 16:15:17 +02:00

3.5 KiB
Raw Permalink Blame History

2025-02-05 - Data Planning

General Updates

  • Started weekly syncs with Guy / Finance on KPIs - Suzannah
  • Engineering - Ingestion of backend data to billing db
    • The proper solution has been delayed until Pablo is back to decide. In the meantime, one-short inputs carried out by Tech
  • Other - Discontinue Superhog Reporting (legacy Power BI)
    • Apparently it was more widely used than expected
    • The effort has shifted towards re-implementing the necessary bits (Listings, Bookings, Payments) but reading from DWH so Data has full control
  • On Waiver Payouts and Resolutions Payouts - Revenue Retained Post-Resolutions trends

image.png

  • I wonder if we should invest / start a working line on:
    • Resolutions claims data (still pending integration, no news)
    • Understanding client price plans / programs for upsell or detect edge cases

Done

  • Finance - Run Old Dash invoicing exports for January 2025
  • Guesty - Resolutions payouts analysis
  • KPIs - Invoiced data is now available on the 20th of the month for the previous month
  • KPIs - Rework Onboarding MRR (avg per client + actual revenue expected)
  • Finance - Accounting aggregations reporting (including client MoM comparison to spot incidents) - Report here
  • Other - Understand Booking Fees / Cancelled Bookings - First analysis completed
  • Other - Help Leo on potential future verification invoicing for historical client Operto
  • Other - Investigated issues raised on New Dash reporting with Gus
  • Other - Several small requests, mostly from Finance. Re-insisted on using Data Requests workflow to avoid constant context switching

In Progress

  • Other - Re-implement Superhog Reporting reading from DWH
  • KPIs - Propose Billable Booking KPI definition for New Dash: 1 Booking can have multiple services invoiced in different times, how do we attribute them?
  • KPIs/New Dash/AM reporting - Exclude known test accounts to increase data quality (wont remove all of them)
  • Product/RevOps - Include a user adoption funnel per service for New Dash, to identify adoption/upsell possibilities

Stopped / No advancement

  • 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 - New Dash vs. Old Dash category
  • Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price + Deal id
  • KPIs - Implement Billable Booking KPI for new dash after definition
  • KPIs - Rework Revenue display in Main KPIs
  • KPIs - OKR, target-based reporting
  • KPIs - Rework Cancellation rates (attribute them to Check-out + ratio)
  • 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)