Services · Recurring Reports
The monthly report,
delivered every cycle.
A managed, recurring business report — a refreshed source-of-truth file, the same dashboard re-run against the new period, and a short summary email alongside it. The page is about the ongoing service, not the first build: the one-off dashboard build it sits on top of is a separate engagement (see Dashboards).
What gets delivered each cycle
Three artefacts, one flat per-cycle scope.
The same shape as the /work recurring case study, broken down by what actually lands in the inbox each cycle. The cadence is set on the first cycle and held — week to week or month to month — so totals stay continuous and the report stops being a scramble.
Refreshed data file
The source-of-truth file re-run against the latest period — canonical keys, currencies and sign conventions carried forward, new rows deduped against the previous cycle so totals stay continuous week to week.
Updated dashboard
The same dashboard the one-off build produced, refreshed against the new period — the metrics, labels and formulas stay where they were, only the inputs and the latest window change.
Short summary email
A few-line summary in the inbox alongside the refreshed file: the headline number, the variation against the previous cycle, and anything worth a glance before the report is forwarded onward.
Engagement shape
What the recurring engagement looks like.
One cadence, one source-of-truth file that survives the cycle, one short summary email every run. You can read the first deliverable before the recurring scope goes live.
Engagement shape
recurringA recurring cadence, one refreshed file, and a short summary email.
Sent under NDA on request · English only · Most cycles turn around in a single calendar week.
- The source-of-truth file refreshed against the latest period, with the previous cycle's canonical keys, currencies and sign conventions carried forward so totals stay continuous.
- The same dashboard re-run against the new period — the labels and formulas stay where they were, only the inputs and the latest window change.
- A short summary email alongside the refreshed file — the headline number, the variation against the previous cycle, and the one thing worth a glance before the report goes any further.
Same cadence every cycle — designed to be handed off cleanly if the engagement changes hands.
See the work
Closest in shape on /work is the weekly Shopify webhook report — a webhook export collapsed to one row per deal, the cleaned table re-built every cycle, and the same total carried forward week to week.
Related reading
Reads on recurring reports from the studio.
Recurring Reports
2 min readWhen the monthly report stops being a scramble.
The switch from ad-hoc to recurring is mostly discipline, not technology — input drift, format drift, and a Friday-afternoon scramble are the early signs the format is ready to lock.
Set the cadence. Get the report every cycle.
One short email with a sample export and a sentence about the cadence you want the report on is enough to start. Reply the same business day, with a flat per-cycle quote for the first run.
$50 starter · NDA on request · Most cycles turn around in a single calendar week.