From Spreadsheet Reporting to Decision Intelligence

Why does the weekly report take two days to build?

Monday morning, someone exports last week from the accounting software. Someone else pulls the enquiry list out of the CRM. A third person keeps outlet numbers in a sheet that only they understand. The three files are copied into a fourth, a formula breaks because a column moved, and the pack lands on Wednesday afternoon. The first half of the meeting goes on disagreeing about one number. The second half goes on last month.

• A capable person spends one or two days a week assembling numbers instead of thinking about them.
• The pack describes a week that is already over, so decisions arrive late by design.
• Three versions circulate, each named final, and nobody can say which was discussed.
• The meeting produces agreement in the room and no written record of what was decided.

None of this is the spreadsheet’s fault. A spreadsheet is an honest tool and most Indian businesses run real operations on one. The trouble starts when the same sheet is rebuilt by hand every week, from sources that disagree, by a person who has become the only one who knows how it works.

Why do two teams report different numbers for the same month?

Usually because they are answering different questions with the same word. Sales counts an order when the customer confirms on WhatsApp. Finance counts it when the invoice is raised. Despatch counts it when the lorry leaves the gate. All three are behaving sensibly. None of them is wrong. The pack simply prints three answers and lets the loudest person win.

Until the definitions are written down and agreed, a dashboard only distributes the disagreement faster and with better typography. This is why the first week of a reporting project is usually spent in conversation, not in software.

How do you agree metric definitions people will keep?

Keep the list short. Most businesses need ten or twelve numbers that actually lead to a decision, not the sixty a reporting tool can produce. For each one, write a short entry and give it an owner:

1. The name people already use for it, not a new one invented for the report.
2. A plain-English definition of what counts, in one or two sentences.
3. What it excludes: cancelled orders, inter-branch transfers, samples, staff purchases, taxes.
4. The source system it comes from, and how often it refreshes.
5. The named owner who approves any change to the definition.
6. The caveats a reader needs, such as a branch that reports late.

What does connecting your sources actually involve?

Connecting sources is less glamorous than it sounds. It is read-only access to your accounting software, your CRM and your operations tools, a reliable way to match the same customer across them, a refresh schedule everyone knows, and a decision about which sheets stay.

• Agree read-only access first, with a named person who can grant and revoke it.
• Choose one identifier for a customer, an order and a site, and fix the mismatches you find.
• Set a refresh time and show it on the report, so nobody argues with a stale figure.
• Keep the sheets that are genuinely the source, such as targets or price lists, but give each one a fixed shape and one owner.
• Record what changed in the pipeline and when, so an unexplained jump can be traced.

Expect the joining to surface problems in how work is recorded: the same customer under three spellings, an outlet code entered by hand, a delivery date typed into a notes field. That is a finding, not a delay. Our guide to reducing manual data entry covers the entry side of the same problem.

What checks should run before anyone reads the numbers?

A chart renders whether or not the data behind it arrived. That is the quiet risk in automated reporting: the pack looks the same on the morning a feed failed. Run the checks before publication, and publish the result of the checks with the report.

• Freshness: when did each source last load, and is anything older than it should be?
• Completeness: are all branches, outlets and channels present, and does the row count look sane?
• Reconciliation: does revenue tie back to a trusted total, such as the ledger?
• Duplicates and restatements: has last week changed since it was published, and why?
• Silence: alert someone when a source stops sending, rather than showing a flat line.

The habit of saying what you cannot measure is worth borrowing from risk practice. The NIST AI Risk Management Framework asks organisations to select measurement approaches for the most significant risks and to document properly the things that will not, or cannot, be measured. In reporting, that means the caveat sits next to the number, not in a footnote nobody opens.

How should a report show what changed and why?

Totals are a poor opening. Everyone in the room already has a rough idea of the month. What they do not have is the movement: which three things changed enough to be worth twenty minutes, and what sits underneath them. A useful entry is short and evidenced.

• The movement, in the unit people think in: cases, orders, days, rupees.
• The comparison basis, stated plainly, and like for like where outlets or ranges changed.
• The most likely drivers, each with the rows or documents behind it, one click away.
• What the system could not explain, named rather than smoothed over.
• The caveat: a late branch, a restated week, a definition changed last quarter.

That is the shape of our Decision Intelligence work: bring approved data together, check freshness and definitions, surface the changes that deserve attention, and leave the interpretation with people. Forecasts and explanations are shown with their assumptions, because a number without its assumptions is just a confident guess.

Who interprets the numbers, and what gets recorded?

A system can rank, compare, group and flag. It cannot know that a distributor was at a wedding all week, that a competitor opened two streets away, or that your best fitter was on leave. India’s Economic Survey 2025–26 makes the same point about work in general: as AI absorbs retrieval and summarisation, the contribution people make shifts upward towards judgement, direction, expertise and synthesis. Reporting is an early example of that shift.

Then record the decision where the numbers live: what was decided, who owns it, what you expect to see if it works, and when you will look again. Most reporting improves the week someone starts writing that down, because the next pack has something to answer to.

When is a spreadsheet still the right answer?

Often. If one person builds one report a month, from one system, and nobody disputes the numbers, a spreadsheet is the sensible tool and a connected platform would be an expensive way to make it prettier. The same is true while your process is still changing weekly: definitions worth automating are definitions that have stopped moving.

The case changes when the pack has grown into a two-day job across several systems, when decisions wait on it, or when the person who built it is the only one who can. At that point the AI Opportunity Blueprint is a paid diagnostic that maps the workflow, establishes a cost baseline and gives you a recommendation about what is worth building.