Features

Saved Views and Receipts

Use dashboards as context, not as the core promise

Dashboard Role

Saved views can help teams scan data, but they are not the differentiated product wedge.

The marketable workflow is:

  • Ask a business data question
  • Get a clear answer
  • Inspect the calculation and source context
  • Export a receipt
  • Reproduce the answer later

When a View Is Not Proof

A chart or saved dashboard is not proof by itself.

Treat a view as unverified unless it includes:

  • Calculation used
  • Source context
  • Row counts where available
  • Metric definition or source path
  • Evidence hash
  • Generated time
  • Assumption boundary

Sharing

When sharing a business data answer, prefer the receipt or evidence pack over a screenshot.

The receipt should travel with the answer so finance, RevOps, executives, or analysts can review how the explanation was produced.