Case study
Three days of
month-end, gone.
A reporting process that consumed the first three days of every month now runs on a schedule and lands in an inbox.
3 days scheduled
Month-end reporting, before and after
Week 2
When the client first clicked working software
The problem
Month-end meant three days of exporting, reconciling and formatting, done by people whose job was supposed to be something else. Every client of theirs wanted the same numbers in a slightly different shape, and the differences lived in one person’s head.
They had asked for a dashboard. What they needed first was a data model that could answer the questions the dashboard would ask.
What we did
We spent discovery on the data rather than the screens: what a tenant is, what a period is, and which of the fifteen years of accumulated exceptions were rules and which were mistakes.
The portal came second, and it was quicker to build for having waited. Role-based access across tenants with an audit trail, scheduled exports in each client’s preferred shape, and a staging environment that matched production so releases stopped being events.
What changed
Month-end is a scheduled job. The three days went back to the people who were spending them, and the shape-per-client knowledge is in the system rather than in one person’s memory.
We still run it — monitoring, patching and the next set of features on a retainer.
Tell us what you are trying to ship.
A real technical opinion back within two business days — not a sales call.