We got tired of dashboards that report the drop and stop there.
KPI Prism started as an internal tool for weekly revenue reviews across a handful of stores. The recurring question was never 'what happened' — it was 'which part'. So we built the decomposition first and the interface around it.
Four principles, applied literally
Every view exists to end an argument about why a number moved. If a view can't do that, it doesn't ship.
Attribution models, data minimums and cost assumptions are printed on the analysis, not buried in docs.
Revenue is the number people celebrate. Contribution margin is the number that decides whether growth is affordable.
Muted contribution colours, one accent, tabular numerals. An operator reading about their own margin should not be shouted at.
Atlas is breadth. Prism is depth.
Atlas reports across clients, channels and time for people who send reports. Prism takes a single business apart for people who own the number. Many teams run both — which is why Prism is $99/mo as an Atlas add-on rather than a second full subscription.
Small team, direct contact
There is no support tier where you talk to a bot. Questions about data requirements, attribution or whether your store is big enough go to the same people who build the analysis.
Want the tour on your own numbers?
Send us a note — we'll tell you honestly whether Prism fits.