How we assess each Savencia playbook visual for implementation readiness in the SKAI Growth platform
Each visual receives a readiness score from 0 to 100. The score reflects how much of the required infrastructure already exists in the SKAI Growth platform. A higher score means less effort is needed to deliver the visual.
Each dimension is evaluated on a 3-level scale. Available means the capability exists today, Partial means it exists but needs adaptation, and Not Available means it would need to be built from scratch.
Can the platform store and process the data required for this visual? This covers the database structure and data pipelines. It carries the highest weight because without the right data, nothing else can function.
| Available | 1.0 | The data is already captured and stored in the platform (e.g. sales transactions, product hierarchy) |
| Partial | 0.5 | Some of the required data is present, but gaps remain that need to be filled with additional configuration |
| Not Available | 0 | The data does not exist in the platform today and would require a new data pipeline or external data source |
Are there server-side services that can retrieve and prepare this data for display? APIs act as the bridge between stored data and what the user sees on screen.
| Available | 1.0 | A working API endpoint exists and already delivers real data for each client |
| Partial | 0.5 | A related API exists but needs to be extended to support the specific data points required |
| Not Available | 0 | No API exists; the entire server-side service would need to be developed |
Does the user-facing chart or dashboard component already exist in the application? Components that only run on sample data (not connected to real client data) are scored as Partial at best.
| Available | 1.0 | The visual component exists and is connected to real client data |
| Partial | 0.5 | A similar component exists but needs adaptation (e.g. different chart type, layout changes, or runs on sample data only) |
| Not Available | 0 | No visual component exists; it would need to be designed and built from scratch |
Priority reflects how urgently a visual is needed. It combines two factors: whether the visual was flagged as must-have by the client, and whether it belongs to an early-delivery workstream. Strategic Pricing and Promo Excellence are delivered first (weeks 2-8), while Trade Terms and Channel & Customer Mix come later (weeks 9+).
| Must-have + early delivery | 1.0 | A must-have visual in an early workstream (Pricing or Promo) — highest delivery priority |
| Must-have only | 0.7 | A must-have visual in a later workstream (Trade Terms or Mix) — important but not immediate |
| Early delivery only | 0.4 | A nice-to-have visual in an early workstream — benefits from the early timeline |
| Standard | 0 | A nice-to-have visual in a later workstream — standard priority |
After calculating the readiness score, each visual receives a verdict that summarizes the recommended next step. The verdict is determined by walking through the following rules in order — the first rule that matches is applied.
Think of it as a checklist: we first look for hard blockers, then for gaps, and finally at the overall readiness level.
Data Model = Not Available→Requires product team alignmentBackend OR Frontend = Not Available→Requires client discussionAll dimensions are at least Partial AND Score >= 70%→Ready to implementAll dimensions are at least Partial AND Score < 70%→Requires client discussionEvery assessment is backed by a reason code — a short tag that explains why a dimension received its rating. These codes provide traceability: they link each verdict back to specific capabilities (or gaps) in the SKAI Growth platform.
In practice, you can use reason codes to quickly understand what would need to change to move a visual from "Partial" to "Available".
DM_READYThe platform already stores and processes all required dataDM_ADAPTThe data structure exists but needs to be extended (e.g. adding new data fields)DM_REBUILDSome data exists but requires significant restructuring to support this visualDM_MOCKData is only available as sample/placeholder values, not connected to real client dataDM_NEWNo data exists in the platform; a new data pipeline would need to be createdAPI_READYA working API endpoint exists and serves real client dataAPI_EXTENDAn API exists but needs to be extended to include the specific metrics requiredAPI_MOCKAn API exists but currently returns sample data instead of real client dataAPI_NEWNo API exists; the entire server-side service would need to be builtFE_READYThe visual component exists and displays real client dataFE_ADAPTA similar component exists but needs changes (different chart type, layout, or data mapping)FE_MOCKThe component exists but is only connected to sample data, not live dataFE_NEWNo visual component exists; it would need to be designed and built from scratchAll assessments are based on the actual deployed codebase of the SKAI Growth platform — not mockups, documentation, or roadmap items. This means every rating reflects what the platform can do today.
skaix-client-app/ — the user-facing application (React components, dashboards, charts)svc-skaix/ — the server-side services (API endpoints, business logic, data models)skaix-pipeline/ + skaix-etl/ — the data processing layer (pipelines, algorithms, data transformations)Note: Some modules (Trade Terms, Channel & Customer Mix) currently operate on sample data rather than live client data. For these modules, the frontend and backend dimensions are capped at Partial, since they are not yet connected to real APIs.