The CFO's recurring problem
Every Indian mid-market CFO has the same Monday morning: a finance team head walks in with three spreadsheets. One has the bank position from the accountant. One has the ageing report from the AR team. One has the customer-wise sales view from someone in the CRM. The numbers do not reconcile cleanly. The CFO spends an hour stitching them in his head, gives the management committee a directional read, and waits for the month-end close to confirm.
By month-end, the receivable that started slipping at day 45 is at day 75. The customer who quietly cut order volume in week 2 has cut it again in week 5. The GST input credit gap surfaced in the reconciliation report after the deadline. None of these were invisible. They were just never read together in time.
The CFO does not need a better spreadsheet ritual. The CFO needs a layer that joins the four sources - cash, sales, receivables, margins - and answers in seconds when the question comes up.
Four metrics every CFO wants live
The CFO dashboard does not need 40 KPIs. It needs four metrics, joined cleanly, refreshed on demand. The rest falls out of these.
Cash flow vs commitments
LiquidityWhat the CFO wants to see: bank balance today vs the payment commitments due in the next 14 days - vendor payables, GST deadlines, salary, loan EMIs. Where the data lives: Tally for ledger and bank reconciliation, the AP module for payables, GST returns for tax obligations, a spreadsheet for the loan calendar. The live query: "Cash position this week vs commitments next 14 days, and the three customers most overdue". One screen, one decision: pull collection focus or rebalance payable timing.
Sales trend by customer
RevenueWhat the CFO wants to see: the customer whose order volume dropped 30% this month, the region whose pipeline is drying up, the salesperson whose conversion is sliding. Where the data lives: the CRM, the order book, the dispatch sheet, and Tally invoices. The live query: "Top 25 customers by revenue trend last 4 weeks vs prior 4 weeks, with realised margin per customer". The drop surfaces while there is still time to talk to the customer, not after the relationship has cooled.
Receivables ageing and DSO
Working capitalWhat the CFO wants to see: DSO trend week over week, the top customers whose ageing has slipped from 45 to 75 days, and the receivables that may need a credit decision. Where the data lives: Tally bill- wise outstanding, the AR module, customer payment terms in the CRM. The live query: "Show me every customer where receivables aged past 60 days this week, with the change vs last week and the cost of carry". The customer who looks profitable on paper but expensive on carry surfaces in seconds.
SKU and customer margin drift
ProfitabilityWhat the CFO wants to see: the SKU that drifted 4 points below standard margin this month, the customer whose realised margin is below target after all credit notes and schemes, the cost head that is creeping above plan. Where the data lives: Tally item-wise sales and purchase, the scheme calendar in Excel, the CRM for customer mix. The live query: "Top 10 SKUs by realised margin drop vs standard this month, with the variance source - material, yield, scheme". The leak surfaces while there is still volume left to fix it.
Why static reports break the cadence
A static dashboard - the kind a BI consultant ships after a 12-week build - refreshes on a schedule. Once a day if you are lucky, once a week more typically. That cadence makes three things hard:
- Ad-hoc questions stop the dashboard. The CFO asks "show me the same view but only for customers in Maharashtra over ₹50 lakh" and the analyst opens Excel for three hours.
- The dashboard ages between refreshes. By Friday, the Monday view is too stale to act on without re-asking the AR team to confirm.
- Drill-down stops at the report cell. The CFO sees a number but cannot trace it back to the underlying Tally voucher or CRM record without a second tool.
A live CFO dashboard refreshes at query time. Every question gets a fresh answer with the underlying records one tap away. The CFO stops asking the analyst to rebuild the report and starts asking the system the next question.
Five live questions a CFO should be able to ask
The point of a live dashboard is not the dashboard. It is the next question after the dashboard. These five recur every week:
- What is cash position this week vs commitments next 14 days?
- Which top 20 customers have receivables aged past 60 days, with cost of carry?
- Which SKUs are running below standard margin this month, and why?
- Which customers cut order volume more than 20% in the last 4 weeks?
- What is the GST input credit reconciliation gap this period, by GSTIN?
None of these need a custom report. All of them need the four sources joined in one place and a plain- English query surface on top.
How KolossusAI builds the live CFO view
KolossusAI reads each source in place. No data warehouse, no ETL pipeline, no BI rebuild.
- Tally per company. Multi-company consolidation, GST, bill-wise outstanding, vendor payments, item-wise sales and purchase.
- CRM and order book. Custom CRM, Salesforce, Zoho, Sell.do - read via DB or API. Joined with Tally invoices so customer-wise margin and revenue trend tie out.
- AR / AP module and bank data. Receivables ageing, payable schedule, bank statement reconciliation - matched against expected cash positions.
- Excel trackers and PDFs. Scheme calendars, loan EMI sheets, supplier rate cards, GSTR-2B downloads - picked up from a shared folder on a schedule.
The CFO opens a chat-style interface, types the question in English or Hindi, and gets the answer in seconds. Every row drills to the source - a Tally voucher, a CRM record, an Excel cell. The dashboard is whatever the CFO last asked.
What changes in the CFO's week
Faster visibility is not a dashboard. It is a different operating rhythm.
- Monday morning starts with a digest, not three sheets. DSO trend, top three customers slipping, cash gap for the week, top three SKUs drifting on margin. All in one email or WhatsApp message.
- Mid-week ad-hoc questions get answered live. Management committee asks "what if we tighten credit terms on customers above 60 days" - the CFO models it on the call.
- Month-end becomes confirmation, not discovery. The shape of the month is already known three weeks in. The close confirms the picture, not reveals it.
- Finance team time shifts. Less time stitching spreadsheets, more time on credit decisions, vendor negotiation, and the actual FP&A work the CFO hired them to do.
Conclusion
A real-time CFO dashboard is not another BI build. It is a layer that reads the systems you already have and answers in plain English when the question comes up. Four metrics carry most of the value - cash flow vs commitments, sales trend by customer, receivables ageing, SKU margin drift. All four sit in Tally, the CRM, the AR module, and an Excel sheet today. Join them once and the CFO stops waiting for month-end to read the shape of the month.
The cost is one connection per source, three weeks of vocabulary tuning, and an hour a week. See how KolossusAI works or start the free 14-day POC on your real systems. The first DSO surprise usually surfaces on the kickoff call.
