Why did revenue change this month?
Revenue
$2.31MWhat changed
- Order volume−2.8%
- Customer mix−0.9%
- Refunds−0.5%
Use cases
Know why the numbers moved before the meeting.
Every team asks different questions of the same data. SenseBrew is being built to answer them in plain English, with your definitions and the records behind each answer.
−4.2%
Illustrative example with made-up numbers.
Finance
Explain why revenue moved, line by line.
Break a change into volume, mix and refunds, then follow each piece back to the orders behind it before the number goes in a report.
Revenue
Have a question like these? Tell us yours and help decide what we build first.
Same approach, every team
An answer you can check.
Your definitions, once
Tell it what “revenue” or “active” means for your team, and every answer uses the same meaning.
It shows its working
Each answer shows the period, the definitions and the records it used, so you can check before you share.
Keep watching Planned
Turn a useful question into a weekly summary or an alert, instead of asking it again every Monday.
Illustrative examples. SenseBrew is in development.
Why not a dashboard?
Dashboards show what. We’re building for why.
| Need | Dashboards | Chat tools | SenseBrew (what we’re building) |
|---|---|---|---|
| A new question | Needs a new report | Answers once | Ask it in plain English |
| Why it changed | Shows what, rarely why | Depends on what you paste in | Breaks a change into its drivers |
| Your definitions | Set up per report | Start fresh each time | Learned once, reused everywhere |
| The evidence | Behind the chart | Hard to check | Records and periods shown with every answer |
Private beta
Bring your questions.
Get development updates and hear first when invitations open.
Or tell us the question your team is stuck on