The accounts answer a specific set of questions well. Profit and loss, balance sheet position, tax liability, statutory compliance — this is the territory where financial reporting has always lived, and where it delivers.
But SME clients are increasingly asking a different set of questions. Not because they've become more sophisticated — because their businesses have become more complex, and the gap between what they need to know and what the accounts show them has widened.
These five questions come up repeatedly. The accounts can't answer them. BI can. For advisors considering whether to add a BI layer to their service stack, they're a useful starting point.
Revenue by client, if the chart of accounts is set up for it. Sometimes gross margin by client if jobs or projects are tracked in the accounting system. Rarely anything adjusted for the time, complexity, or rework that went into earning that revenue.
Profitability per client adjusted for delivery time, support load, and revision cycles. The client ranked third by revenue who absorbs 40% of the team's bandwidth — visible. The client ranked eighth who generates the cleanest margin — visible. The accounts confirm revenue. BI reveals what was left after earning it.
Confirmation that margins dropped. The P&L shows the outcome clearly. If the cost of goods or direct labour lines have moved, that's visible. The root cause — which product line, which client segment, which operational change — is not in the accounts unless someone has already built the segmentation to find it.
The margin trend disaggregated by product, service line, and client type. The month where the shift started. Whether it's a pricing issue, a delivery cost issue, or a mix issue — meaning the product composition of revenue changed, not the margin on each product. This is a different question from "did margins drop?" and it requires different data to answer.
Where the business stood at the last period close. For most SMEs, that's a month behind the present. The management accounts — if they exist — might be three to four weeks old by the time they're reviewed. They show what happened. Whether that trajectory continues depends on what's in the pipeline, what's been invoiced but not received, and what's been committed but not started.
A forward-looking view built on confirmed pipeline, committed orders, and run-rate assumptions. Not a forecast in the FP&A sense — a structured answer to "given what we know today, what does the quarter look like?" This is the question that determines whether the business needs to act now or has breathing room. Compliance answers it four weeks late.
Labour cost in aggregate. Direct versus indirect costs if the accounts distinguish them. What the accounts cannot show is where operational time is going — which client requests absorb disproportionate resource, which internal processes create rework, where the team's capacity disappears between billable hours. This data doesn't live in the GL.
Operational visibility outside the general ledger — drawn from project tools, CRM activity logs, support ticket data, or time-tracking exports. The point isn't to surveil the team. The point is to give the business owner a factual answer to a question they currently answer by gut feel — and gut feel on resource allocation is one of the more expensive blind spots in an SME.
An accurate picture of what happened. This is not a limitation — it's the correct scope of statutory and management reporting. The accounts are not designed to generate decisions. They're designed to record outcomes accurately and reliably.
The structured layer between the numbers and the decision. Not a recommendation system — a framework that connects specific metrics to specific choices. When revenue concentration is high, the decision is client diversification. When the Tier 2 client retainer margin is falling, the decision is delivery model review. BI makes the link explicit. Compliance leaves it implicit.
The Pattern These Questions Reveal
None of these questions are unusual. Every growing SME asks versions of them — and most ask them directly to their accountant or bookkeeper, because that's the only external party who works with their numbers.
The compliance answer is always technically correct: "the accounts show X." But it isn't always the answer the client needed. The client needed to know what to do about X — and that requires a layer of analysis that compliance work wasn't designed to provide.
The advisors adding a BI layer aren't replacing compliance work. They're answering the questions that come after compliance has done its job — and charging for it accordingly.
The service stack for delivering that layer is the Diagnostic (baseline assessment), the Operating Layer (structured reporting cadence), and the Strategic Partner engagement (quarterly decision-review). Each tier is priced to reflect the value of the question it answers — not the hours it takes to deliver. The pricing framework is here, and the worked economics are in the BI Service Stack Planner.
This article maps to the Awareness stage of the partner acquisition funnel — framing the BI opportunity for accountants, bookkeepers, and fractional CFOs who haven't yet formalised a BI service layer. The five questions are drawn from patterns observed across SME advisory engagements; they are not client-specific.
For the service stack that answers these questions: How to Price BI as an Add-On Service. For the case study: How Hartwell & Co. Built a BI Service Line in 90 Days. BIP Method™ applies across all four stages — Baseline, Foundation, Rhythm, Evolution.