Colleagues ask the warehouse directly and get answers they can check. dbt work arrives as a branch and a diff. Nothing merges without you.
Or schedule a demo with the team.
Asked from
Chat, Slack or a ticket
Used for
Requests and dbt changes
You get
Answers, and diffs to review
In one audit, tvaras found 17 issues across 42 dbt models.
“Can you pick up DATA-412 and add customer lifetime value to the customer mart?”
tvaras: Reads the ticket and your existing models, proposes a plan, then writes the change on its own branch with tests. You get a diff to review.
“Why is `mart_orders` running twice as slow as last week?”
tvaras: Reads the dbt run log, finds the slowest step and suggests a fix. It comes back as a proposed diff, not an edit to main.
“Is this model counting some orders twice?”
tvaras: Checks for repeated order IDs and for joins that multiply rows, then shows you what it found and the SQL it used.
“Marketing wants a weekly dashboard. Can you build it?”
tvaras: Drafts a Playground with date filters and channel toggles. It ships behind your permissions, and the charts stay editable.
A sortable, filterable table with a slider for the discrepancy threshold. The kind of internal tool that takes a sprint to build by hand. This one took two sentences.
See it live