Reporting & alerts
The weekly report that assembles itself from the source systems and lands on time — plus alerts when a number crosses a line you set yourself.
Scope a buildWhat this is
Someone on your team spends hours each week pulling numbers into a deck. We replace that with a report that builds itself: it reads the source systems, does the maths, and delivers the same format every week by email, Slack or a live page. On top of that, alerts — when a metric moves past a threshold you choose, the right person hears about it the same day, not at the next review.
What you get
- A recurring report in the format you already use, delivered automatically
- Pulled straight from the systems of record, so the numbers reconcile
- Threshold alerts to email / Slack / SMS with the context attached
- A live dashboard version if you want one, not just the static report
- Editable definitions — you can change what a metric means without us
How we start
You send us last week’s report. We reproduce it from the source data, get you to sign off that the numbers match, then put it on a schedule.
Who owns the code?
You do, completely. The report-generation logic and the alerting rules are delivered as code in your repository, or as a workflow in your own n8n or Make account. There's no dashboard subscription you're locked into — you can keep running it or hand it to anyone.
How is our data handled?
The report pulls straight from your systems of record — we don't maintain a separate copy of your data long-term. Credentials sit in a vault, access is least-privilege and logged, and nothing collected while building or running the report is used to train a model.
How long does it take?
Reproducing a report you already send by hand typically takes one to two weeks: we rebuild it from source data, you sign off that the numbers match, then it goes on a schedule. Adding threshold alerts on top is usually a small extra step.
Can we change what a metric means later?
Yes — definitions are editable, not hardcoded into something only we can touch. If how you calculate a number changes, you or your team can update it directly. We document the logic clearly enough at handover that this does not require calling us.
Have something like this?
Tell us the workflowWondering who owns the code or where your data goes? See how we work.