What if we do not have all twelve numbers yet?

Start with the six you can produce automatically and add the rest as the capture improves. A page with six reliable numbers is more useful than one with twelve guesses. Leave the missing rows visible with a note on what is needed to fill them.

Who should present the page?

Nobody — it is read before the meeting. The meeting opens with the numbers that moved, and each owner speaks to theirs. The moment someone is presenting slides, the page has stopped doing its job.

Should the page be the same for a D2C brand and a B2B company?

The structure is the same — leads or sessions, response, conversion, revenue, retention — and the labels differ: orders instead of deals, repeat rate instead of pipeline. The point is one page, the same every week, cut by source and owner.

← Blog·Reporting & data

The Monday revenue dashboard: the twelve numbers that run a weekly meeting

Most dashboards have forty charts and answer nothing. The one-page weekly view — leads, response time, meetings, pipeline, wins, retention — by source and by person, that turns the Monday meeting from status updates into decisions.

14 Oct 2025 · 2 min read · by HeiSyn

A weekly revenue meeting should take thirty minutes and end with three decisions. It takes ninety and ends with none when the numbers arrive as a tour of a dashboard nobody trusts. The fix is a single page, the same every week, with twelve numbers and their change from last week, produced automatically before the meeting and read by everyone before they walk in.

The twelve

New leads by source. Speed-to-lead median and 90th percentile. Meetings booked and held. Positive outbound replies. Pipeline created (count and value). Pipeline by stage with age. Forecast — commit, likely, upside. Wins and losses with reasons. Win rate by segment. Average deal size. Retention or repeat rate. Revenue against plan. Each with last week and the four-week trend.

By source and by person

Every number cut two ways: where it came from and who owns it. The cuts are where decisions live — a source that produces leads that never become meetings, a person whose speed-to-lead is double the team's, a segment with a win rate that justifies more outbound.

Automate the production

The numbers are pulled from the CRM, the sequence tool, the calendar and the billing system by an orchestrator on Sunday night, assembled into a page or a Slack message, and posted with a link to the underlying records. Nobody builds the report on Monday morning; the meeting starts with it already read.

Run the meeting on exceptions

The page shows the numbers; the meeting discusses the ones that moved. Red for a change beyond a threshold, with the owner named. Three decisions written down at the end, checked the following week. Over a quarter the meeting gets shorter and the numbers get better, because everyone knows exactly what will be looked at.

Questions people ask next

What if we do not have all twelve numbers yet?: Start with the six you can produce automatically and add the rest as the capture improves. A page with six reliable numbers is more useful than one with twelve guesses. Leave the missing rows visible with a note on what is needed to fill them.
Who should present the page?: Nobody — it is read before the meeting. The meeting opens with the numbers that moved, and each owner speaks to theirs. The moment someone is presenting slides, the page has stopped doing its job.
Should the page be the same for a D2C brand and a B2B company?: The structure is the same — leads or sessions, response, conversion, revenue, retention — and the labels differ: orders instead of deals, repeat rate instead of pipeline. The point is one page, the same every week, cut by source and owner.

reportingdashboardsRevOps

Want this built for your team?

A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.

blog/the-monday-revenue-dashboard