Business Intelligence ยท Three client programs at a nearshore contact centre
Emailed files in, dashboards and alerts out
Every morning brought emails, spreadsheets and notes in different shapes. Now they become master data that feeds dashboards, scheduled reports and alerts, with a separate edition for an outside audience.
What we built.
Files arrive by email
Emails, spreadsheets and notes, routed by name to the right program.
They become master data
Each program's inputs are transformed into one consistent record, with AI reading the messy parts.
Anything odd raises an alert
Unusual or conflicting data goes to a person instead of being quietly corrected.
Dashboards rebuild
Published behind a login, with a separate edition for the audience outside the company.
Scheduled reports go out
With recipient controls and safeguards against sending twice.
Built to hold up.
Flag, never fudge
Conflicting numbers are raised, and estimates are labelled as estimates.
Right report, right reader
Each audience has its own edition and its own access list.
No double sends
Delivery is guarded against sending the same report twice.
Traceable
Data and deployments are versioned, so a report can be traced back to its source.
Where it stands.
- An operating reporting stream for three client programs, with recorded deployments and repairs.
What we measure next.
- Report timeliness against schedule
- Reconciliation failures per week
- Hours managers no longer spend assembling numbers
Runs on
- n8n
- Claude (Anthropic API)
- GitHub
- Cloudflare Pages
- Cloudflare Access
- Brevo
- Google Workspace
Tell us what needs to happen.
Thirty minutes, your agenda. You leave with a first step whether or not we work together.
+1 213 556 4010