Work ← 2025 ● Maintained

Internal operationsData to a usable report

Internal software

Marketing Machine

I build and operate internal tools for Sirv's marketing and reporting. The difficult part is often making the number mean what its label says.

  1. 01Collect the data
  2. 02Check the definition
  3. 03Inspect the report
  4. 04Act on the evidence

A label that hid the wrong calculation

In August 2026, the analytics page labelled a value Average MRR while calculating it from cash collected over the selected period. An annual payment could look like a recurring monthly spike.

The repair separates cash collected from recurring revenue. Average MRR now averages point-in-time recurring revenue at month ends and the end of the selected period. Long ranges use bounded sampling.

A regression test uses a $1,200 yearly payment. Cash collected is $1,200. MRR is $100. (Test values, not Sirv’s numbers.)

The rest of the report had to work too

Calendar-period queries could select a lookback the scheduler had not cached. The page then rebuilt the combined user dataset instead of using a warm result. The fix chooses a warmed source range and gives the page a timeout.

The plan breakdown was a pie chart with eleven long labels. It became a ranked horizontal bar chart, with the remaining plans grouped separately. A Revenue card shows cash collected in the selected period.

The change went through the calculation, the API, the tests and the interface. A nicer chart on top of the old formula would still have lied.

Where it fits

Marketing Machine brings together Sirv analytics and marketing workflows, including search, advertising and content work. All those integrations are only useful if each number means what its label says.

This is what I mean by product and operations work. The repair is commit a23fcc74, from 10 August 2026.

What remains imperfect

It is internal, so you cannot try it. I also have no revenue result to attach to this repair.