SUPPORTING DOCUMENT CASE FILE // APPENDIX

PRD Summary

Short product and reporting requirements summary reconstructed from the beverage commercial performance case study.

Product Intent

This MVP was designed as a reporting product for commercial decision-making, not just a dashboard. The goal was to give teams a practical view of what was changing and where intervention was needed.

User Types

  • Commercial managers reviewing business performance
  • Sales teams preparing weekly channel and account reviews
  • Finance teams checking definition consistency and margin logic

Product Requirements

  • Users must be able to review pricing, channel, and promotion performance from one view.
  • The dashboard must support period comparison and identify change clearly.
  • The reporting layer must use shared product and channel definitions.
  • Users should be able to move from top-level KPI review into more detailed views.
  • Dashboard notes should help guide account-level review rather than leaving interpretation entirely open.

Reporting Workflow

  1. Source data is aligned into one commercial model.
  2. Core KPIs are calculated from shared definitions.
  3. Teams review performance by period, geography, product, and promotion.
  4. Commercial managers use the output to decide where follow-up is needed.

Acceptance Criteria

  • KPI definitions are consistent across the reporting views.
  • Users can compare periods without manual spreadsheet work.
  • Promotions can be reviewed before campaign windows fully close.
  • Sales and finance can work from the same baseline.

Product Measures

  • Report usage for weekly review
  • Time to produce a review-ready output
  • Number of manual reconciliations avoided
  • Promotion review timeliness
SYSTEM ONLINE // KM.III.IV 00:00:00 SAST CASE FILE // ACTIVE