All work

Case study

July 2026

In production

A daily read, not a dashboard.

Two scheduled briefs, daily and weekly, that pull the CRM, the call recordings, and the documentation system into a written read on the business. Built at Stratus. The CRO and CEO use them to keep a pulse.

Briefs on a cadence
2
Systems synthesized
3
Manual assembly
0
Standing readers
CRO + CEO

Context

Leadership already had dashboards. Dashboards report what happened. They do not tell you what it means, and they are silent on the one question an executive is actually asking, which is whether today changed anything.

The gap was being filled by hand, which meant it got filled inconsistently and cost somebody a morning every time.

The problem

A chart cannot say that both losses that day were timing, neither was competitive, and the one worth worrying about had already reached Proof, because a deal that advances that far and then stalls usually means nobody confirmed a compelling event.

A chart also cannot tell you when it is lying to you. One opportunity was reset from Commit back to an early stage and then re-advanced through every stage to Commit inside the same hour. On a dashboard that reads as a downgrade and a recovery. It was a data correction, and it needed to be excluded from the movement counts and explained, not plotted.

That judgment layer is the whole job. Automating the numbers without it just produces a faster dashboard.

What I built

Two briefs on a schedule. The daily lands after close of business and covers the day: calls that mattered, objections and competitive signal, opportunity creation, forecast movement, outreach volume, and pace against the quarter. The weekly runs at week close and does the same at a different altitude, adding day-by-day shape and the themes that only appear across five days.

Every section splits New Logo, Expansion, and Renewal apart and keeps them apart. That one decision does most of the work: a perfect retention month will otherwise quietly cover for a month with no new business in it, and the summary number will look fine while the business underneath it does not.

Each brief opens with the read, not the data. Metrics expand into the records behind them, so a number is never a dead end. Goal tracking is drawn as pace against how much of the quarter has elapsed rather than as raw attainment, because being at 40 percent means different things in week two and week nine.

Read them

Both briefs in full, running here. Click any metric tile in the daily to expand the records behind it. Sanitized editions: account names, rep names, and revenue figures are withheld, and goal tracking shows pace and status rather than amounts.

Sales Daily Brief

Metric tiles and cohorts expand into the records behind them

Open full screen

Loading the live artifact…

Sales Weekly Brief

Month-end close · cohort split, daily shape, outreach

Open full screen

Loading the live artifact…

Two details worth pulling out

  • Forecast movement, grouped by what the move means rather than by stage. The data note at the bottom is the part a dashboard cannot do: an artifact identified, explained, and excluded from the counts.

  • Outreach broken down by outcome and by rep. More dials with a worse contact rate points at list quality, and one rep making 62 percent of all calls is a dependency worth naming.

Outcome

The CRO and CEO rely on both briefs to keep a pulse on the business. Nobody assembles them.

The briefs also turned out to be a standing audit of data quality. Once loss reasons and opportunity values are read back to leadership every week in plain language, the patterns become impossible to ignore: four straight weeks of timing losses and no competitive ones, or a quarter where opportunity count is measurable and opportunity value is not because most records carry a placeholder. Neither of those shows up as a problem on a chart.