What is hard today
- Every client's reporting lives in its own workbook and its own folder, and the method lives in one consultant's head. When that consultant leaves, the client's reporting leaves with them.
- Quarter-end arrives for every client on the same date. Capacity is not limited by demand but by the two weeks in which everything is due at once.
- Clients sit on different frameworks and different reference dates, so the "same" template is not the same template — module versions overlap and the wrong one is a silent error.
- A rejected submission at a client is your reputational problem, not the client's software problem.
What changes
- One workspace, every client institution in it, strictly separated — a consultant sees the clients they are assigned to and nothing else.
- The method stops being tacit. The template is rendered from the model and the checks are the supervisor's own, so quality does not depend on which consultant staffed the engagement.
- A framework release lands once, for every client at once, instead of being reapplied workbook by workbook.
- Validation runs before filing, so the quarter-end crunch is spent on the findings that need judgement rather than on discovering them after the deadline.
On billable hours. Advisory revenue is measured in time, and software that removes hours can look like software that removes revenue. Our experience says the binding constraint is not demand — it is how many clients one consultant can carry through the same two weeks. Automating the mechanical part raises that number and moves the billable work to where clients actually value it: the judgement calls, the findings, the supervisory dialogue. We would rather say that plainly than pretend the tension is not there.