43 lines
No EOL
3.3 KiB
Markdown
43 lines
No EOL
3.3 KiB
Markdown
# 2025-01-29 - Data Planning
|
||
|
||
### General Updates
|
||
|
||
- 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.
|
||
|
||
### Done
|
||
|
||
- January invoicing incident resolution - [Incident Report](20250124-01%20-%20Booking%20invoicing%20incident%201880446ff9c9803fb830f8de24d97ebb.md)
|
||
- Bugfix - Guest KPIs reporting has a strange connectivity issue - [Incident Report](20250122-01%20-%20Power%20BI%20Main%20Guest%20KPIs%20Bug%201840446ff9c980249355f34c58c4686e.md)
|
||
- Finance - Check in Hero API reporting for invoicing purposes - [Link](https://app.powerbi.com/groups/me/apps/043c0aec-20b8-4318-9751-f7164b3634ad/reports/ca328a93-8d9d-431c-ac01-c646c81ba421/285e358d70a0c9155b23?experience=power-bi)
|
||
- 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](https://www.notion.so/Confusion-over-Fixed-vs-Relative-on-A-B-test-results-Incident-report-1850446ff9c9804f9fd7e004ed47d095?pvs=21)
|
||
- Data - Fixed alerts that failed on Jan 29th
|
||
|
||
### In Progress
|
||
|
||
- 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)
|
||
|
||
### To Do (does not include critical subjects)
|
||
|
||
- 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) |