Intelligence
Reports
Scheduled exports, audit-ready summaries, and operational report packs that turn Otto’s live workspaces into artifacts teams can circulate.
Otto
Reports should come later than the core workspaces, but not last. Once Billing, Analytics, and Exceptions settle on their source-of-truth metrics, this is where we package them for finance, ops, and leadership without making people screenshot the dashboard.
Best after
Core flows
depends on stable definitions
Consumers
Ops + finance
audit and scheduled exports
Implementation risk
Low
mostly aggregation + export surfaces
What Lives Here
Operational report packs for fleet health, exceptions, complaints, field work, and billing summaries.
Scheduled exports and reusable templates so the same numbers can leave the console cleanly.
Download history and audit visibility for who generated which report and when.
Dependencies
Needs Analytics and Billing metrics to stabilize so exported values match live console numbers.
Should pull from shared query contracts rather than bespoke one-off SQL per report.
Works best with role-aware access rules because finance, support, and operations need different packs.
Suggested Build Order
Begin with on-demand exports for the queues operators already use every day.
Then add scheduled report delivery and archival history once teams agree on cadence and ownership.
Reserve highly formatted executive packs for after the operational metrics are trusted in production.