Monday / Revenue review
Start the week with the same definitions.
Review revenue, order volume, and average order value. Keep completed-order definitions and exclusions in a note beside the charts.
Leave with the segments to investigate.
Recurring analytics
Less rebuilding. More understanding.
Build a shared dashboard, reuse its query logic for the next review, and bring follow-up questions to Kole in Slack. Schedule query results for the channels your team uses.
Explore the reporting workflowReport blocks · sample
12
Reporting Workflows workspaceSample dataWeekly business review
Regional performance
Revenue · sample
$312k
Shared context
reporting.weekly_reviewSource in context
Ask with Kole
What changed across our regions?
Charts, queries, and context
Built around the next review
A reporting rhythm.
For the decisions you repeat.
Monthly / Pipeline review
Give every region a comparable view.
Compare pipeline stages, conversion, and deal size. Regional leads use the same SQL, with variables that select their own scope.
Leave with the stages that need attention.
Quarterly / Board reporting
Make the methodology easy to explain.
Bring ARR growth, customer count, retention, and expansion together. Inspect the SQL and record caveats before exporting charts for the deck.
Leave with numbers you can trace to a query.
The workflow in practice
Turn recurring questions into a reporting workflow.
Build
Visual queries + SQL
Reuse
Typed report variables
Discuss
Kole in Slack
Deliver
Scheduled query workflows
A useful reporting workflow carries the question, the query, and the explanation into the next meeting. Start with a shared dashboard, set its scope for each review, and use Slack for the follow-up questions that appear when the team sees the numbers.
Make the metric definition part of the report
For a weekly revenue review, agree on which orders count, which timestamp determines the week, how refunds are handled, and which currency the chart uses. Save those assumptions in a Markdown block beside the charts. A useful report explains both the number and how it was calculated.
Start with the visual builder or SQL, then configure chart type, X and Y fields, title, and colors. Keep revenue, order volume, and average order value in a shared layout. Reviewers can inspect each chart's query when a number needs explaining; takeaways and chart comments keep the discussion close to the result.
Prepare the next review without rebuilding it
Define typed variables such as quarter, region, and min_revenue, and map them into SQL with references such as {{quarter}} and {{region}}. For the next meeting, change the values, refresh, and inspect the result. The team shares the query logic and layout while choosing the scope it needs.
Before presenting, confirm the reporting period, time zone, filters, and source availability. During a review window, use manual refresh or an auto-refresh interval. Dashboard refresh is separate from a scheduled query job that sends a result to a channel.
03 / Kole for Slack
The report starts a conversation.
Keep the next question there.
Mention Kole in Slack when the weekly review raises a follow-up. Ask about connected data in the thread where finance, sales, and operations are already discussing the result.
Be specific about the period, segment, and metric. Keep the answer alongside the conversation, and take deeper investigations into Quantum Lab when the question needs more work.
Connect Kole to Slackweekly-revenueIllustrative conversation
Alex 9:41 AM
@Kole How many paid orders came from EMEA this week?
Kole APP
In this sample, EMEA accounts for 84 of 248 paid orders this week.
public.orders / EMEA / paid / this week
Slackbot handles questions in conversation. Set up scheduled report delivery separately with a query workflow.
When a recurring report reveals a new question
A regional drop in revenue might need a closer look at refunds, product mix, or a small set of customers. Inspect records in Data Explorer, or open Quantum Lab for a SQL and Python investigation with notes and charts.
When that follow-up becomes a question the team asks regularly, add its query as a dashboard chart. Keep the definition, comparison period, and caveats with the chart so the next review starts with the context already in place.
Start with one meeting
Choose the three questions your team asks every week. Build the charts, add the metric definitions, and share the dashboard. Connect Kole to Slack for follow-ups, then configure a saved-query workflow if the team also needs a recurring result delivered to a channel.
Build a dashboard · Connect Slack · Read the visualization guide
Resources
Take the next question further.
Practical guides, reusable starting points, and product details.
Customer perspective
More time for the work that matters.
With their robust platform, we've seamlessly integrated multiple data sources, unified analytics, and automated standard reporting, saving us countless hours each week.