Powering BI
Go back and forth with stakeholders without any worry.
Bring everything together in three easy steps
The Narrator difference is how we handle iterations
Slice anything by anything
Stakeholders want to see data sliced by an infinite list of features. For each new slice, you don't have to worry about joining in new columns. Narrator handles the added SQL complexity for you.
Add customer attributes
"Show me what this looks like by gender."
"Grab customers by city."
"Let's explore order status by age."
.gif)
Add features from other activities
"Please, add the first touch ad source."
"Add the contract value before that opportunity stage."
"Bring in the last email campaign"
Add features dependent on behavior
"Well, did this user call us before they converted?"
"What action did they take since their previous support ticket?"
"Have they ever met with sales?"
.gif)
Yes, you can still use dbt
In Narrator, you can materialize any query for BI or send it to dbt as a new model.
It's simple to iterate using Narrator's materialized view integration. Once you have something ready for production, you can trigger a pull request to your dbt project to have it be maintained there.
