What is the difference between a management dashboard and a reporting system?
A management dashboard shows real-time KPIs on a screen, such as a live overview of sales, stock and cash flow. A management reporting system periodically produces a fixed report document: a PDF or Word file with figures, charts and written commentary that goes through a review workflow once a month or quarter. Many organisations need both: a dashboard for day-to-day steering, and a reporting system for formal reporting to the board, clients or regulators.
Do you replace Power BI, Tableau or Qlik?
No — for standard reporting, those tools are excellent and cheaper than custom work. We build custom solutions when standard tools can't deliver a specific format: branded client reporting with an audit trail, industry-specific compliance formats, data from non-standard sources, or a commentary flow where the controller's explanations flow automatically into the document. Often a custom MRS runs alongside Power BI or Tableau rather than replacing them.
Can the report follow our brand identity or our client's?
Yes. A branded report is one of the most common reasons to build a custom MRS. For client reporting (consultancies, marketing agencies, accountants), we set up a dedicated template per client: logo, colours, typography, cover page, header. The figures block and the commentary stay the same; only the look differs. A single MRS instance can run dozens of white-label reports side by side.
How do you handle different source systems?
We start with a mapping workshop: which source systems (ERP, CRM, HRIS, accounting package, industry software) supply which fields. We then set up an ETL layer that periodically pulls data and harmonises it in a central data layer. We build connectors via standard APIs or, for legacy systems, via database replication or CSV import. Changes in a source system are absorbed by the ETL layer, so the report itself remains stable.
How does the commentary flow work?
For each report block, the controller or CFO can add written commentary, for example where actuals deviate from the forecast. We store that commentary separately per reporting period and link it to the figure. When the PDF is generated, the figure and commentary come together in one document. Earlier commentary remains available in the version history, so you can see a trend in the explanations across quarters.
What about security, audit trail and sign-off?
Every report goes through a review workflow: author, reviewer, sign-off. The system records every change with a timestamp and user. Once signed off, the report is pinned as an immutable version, so you can later demonstrate exactly which report was sent to which stakeholder and when. Authentication runs through your existing IdP (Azure AD, Okta, Auth0), data is encrypted at rest and in transit, and access is role-based per report type.
What determines the cost of an MRS project?
Three factors: the number of source systems we need to connect (one accounting package is different from a mix of ERP, CRM and legacy systems), the complexity of the report templates (one standard management report versus dozens of branded client reports), and the rigour of the review flow (simple sign-off versus a multi-stage compliance chain). An introductory conversation is always free; we then provide a realistic scope estimate for your situation.
Do you work with our finance and IT departments?
Almost always. Finance provides the domain knowledge (which metrics, which commentary, which format), and IT provides access to the source systems and the security framework. We deliver the software and the architecture. In the final sprint, we hand over knowledge to your IT team and provide a runbook for incidents. For larger projects, we organise collaboration through shared Linear or Jira boards and a fixed sprint cadence.
