# Sirv Marketing Machine Internal Sirv reporting and marketing software. One analytics repair shows why growth work sometimes starts in the revenue calculation. ## 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 case uses a $1,200 yearly payment. The cash result is $1,200 and the monthly recurring amount is $100. Those are synthetic test values, not Sirv's business figures. ## 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 crossed the calculation, API, tests and interface. Correcting only the chart would have preserved the misleading metric. ## Where it fits Marketing Machine brings together Sirv analytics and marketing workflows, including search, advertising and content work. Its integrations create useful context, but the report still depends on the definitions underneath each number. This is an example of [what I mean by product and operations work](/posts/the-title-was-fuzzy/). The repository records the repair in `a23fcc74` on 10 August 2026. It does not establish that the change increased revenue, and I do not have a business outcome to attach to it here. --- [Canonical HTML](https://www.varyvoda.com/projects/sirv-marketing-machine/) ยท [Sitemap](https://www.varyvoda.com/sitemap.xml)