← Back to Blog
Methodology

Data First. AI Second. Why I Built It This Way

Suraj Kumar Lohani · 5 min read
Excel Power BI Python SQL Claude AI

Every time I explain 7AM & Realtime CFO™ to a founder for the first time, someone eventually asks a version of the same question: how much of this is AI, really — and can I trust a number an AI generated about my own cash position?

The honest answer is: AI touches your data last, not first. And that order is not an accident.

The 12-layer wall

Before Claude ever sees a single number, the data passes through what we call Rakshak Mode — a 12-layer check covering data confidence, anomaly detection and flag generation. If those checks don't pass, the AI doesn't get involved. Not partially. Not with a caveat. It simply doesn't run.

That's the sequence, in order: Data In. Rakshak Mode. AI — Claude API. Today's Decision. Four steps, and the third one only fires after the second one has already done its job.

Why not just let the AI clean the data itself?

Because a developer sees raw data, and a finance expert sees the story behind it. Every transaction has context that a model, on its own, cannot reliably infer — is this COGS or a Purchase? Is this an inter-company transfer or a real expense? Categorising ten thousand transactions correctly requires understanding chart-of-accounts mapping, inter-company logic, and DSO/DPO intelligence — built first as Excel and Power BI models — that comes from years of hands-on finance work, not from a well-written prompt alone.

A wrong prompt produces a wrong insight, and a wrong insight produces a wrong decision — at 7AM, on a channel the founder trusts, arriving with the authority of "the system said so." That's precisely the failure mode Rakshak Mode exists to prevent.

What "Data Confidence: 84%" actually means

Every One Page News carries a confidence score for a reason: if the UAE entity's sync is pending, the report says so, in plain language, instead of quietly presenting a number as more certain than it is. Anomalies get flagged for review by the underlying SQL and Python checks — "unusual variance pattern, review needed" — never overclaimed as "fraud detected." The system's job is to raise a hand, not to pass a verdict.

Data First. Rakshak Second. AI Third. Founders buy clarity, control and peace of mind — not AI for its own sake.

This is also why the CFO commentary you read at 7AM doesn't sound like a chatbot summarising a spreadsheet. It's written from the same judgment that caught a ₹2.07 crore fraud a CA audit had missed — the AI is doing the writing, but the finance judgment underneath the prompt is the twenty-two years that came before it.

Want to see where your own numbers are hiding something?

Start the Free Diagnostic →

Have a quick question?

Leave your details — we reply within one business day.

No spam. Prefer WhatsApp? DM "DEMO" to +91-7011283542.

Know a founder who needs this? Send them a Fin-vite — that's how most conversations here start.