Use case

Insights

Reports that stay correct after the data moves.

A chart pasted into a document is a screenshot of a moment. It is wrong the day after the pipeline next runs, and nobody can tell by looking. Insights is the practice of publishing the arrangement of a report separately from its numbers, so the two can move independently.

What makes this hard

Charts baked into documents are stale on arrival and give no sign of it.
Rebuilding the same monthly report by hand is where the transcription errors come from.
Deleting the data behind a published report silently breaks it.

How we approach it

Composed, not coded
A report is an arrangement of blocks bound to dataset columns, with no embedded numbers and no embedded markup.
Numbers at read time
Charts resolve against whatever the dataset currently holds, so a re-run updates every story that reads it.
Traceable dependencies
Every dataset knows which stories depend on it, so nothing is deleted out from under a published page.

What you should expect

Published pages that keep telling the truth without anyone editing them.
A clear answer to “what breaks if we change this”, before the change is made.

Where this shows up

Guido

The agentic orchestrator the other products run on.

Guido is the workspace where the agents, tools and data behind every Trazup product live. Discovery, analysis, planning and reporting sit in one place, with the same permissions, datasets and audit trail underneath.