Origin stories, case studies and the fractional CFO methodology — written from twenty-two years on the ground, not from a textbook.
In 2006 a DSO office executive told a Home Guard constable Excel wasn't for him. That evening changed the next twenty years.
Read the story →Between March and August 2004, 47 companies said no. Here is the exact method that turned each rejection into preparation for the next.
Read the story →A vendor cheque for six consultants and a month of work landed on my desk. The real cost wasn't the ₹12 lakhs — it was the question nobody had asked first.
Read the story →The Last Layer Approach™ goes where audits usually stop — the warehouse floor, not the P&L.
Read the story →Before Claude ever touches your numbers, an 8-layer Rakshak check has to pass first. Here's why that order is the whole point.
Read the story →Most Indian founders have heard these words but never quite understood them. Here's what each one actually means, and why hiring one isn't the same as hiring "a cheaper accountant."
Read the story →New posts add as the work does — check back, or follow on LinkedIn for daily posts.
Why a business can show a profit and still struggle to pay its bills, and the three places to look first.
Read the post →What Days Sales Outstanding means, how to calculate it, and what to do when it rises.
Read the post →A practical way to read budget variances by separating price, volume and timing before asking who is responsible.
Read the post →A good management report answers five plain questions on one page. Here is the structure and what to leave out.
Read the post →Margin rarely falls in one big step. Four common leaks and how to check each one.
Read the post →Simple, non-technical checks that tell an owner whether the books behind a report can be relied on.
Read the post →Why a clean data model matters more than the charts, and a simple structure for finance data in Power BI.
Read the post →Practical design rules for an Excel template: separate inputs, calculations and outputs, and build in checks.
Read the post →Why automating a messy process makes it faster but not better, and how a simple process map helps.
Read the post →A practical split between what AI can do in a finance workflow and what should stay with a person.
Read the post →A short structure for writing a finance SOP that stays useful: purpose, roles, steps, controls and exceptions.
Read the post →A starter pattern for turning a monthly manual report into SQL queries and a Python script with checks.
Read the post →Three posts a day, every day, on LinkedIn — follow along for the ongoing version of these stories.
Follow on LinkedIn →Leave your details — we reply within one business day.
No spam. Prefer WhatsApp? DM "MORNING" to +91-7011283542.
Know a founder who needs this? Send them a Fin-vite — that's how most conversations here start.