Manideep GNS
I treat finance like engineering.
I treat finance like engineering.
"Querying Zoho is like querying a database replica that's two weeks behind master. The data exists somewhere — just not in any one system." — from "Why MIS Takes 15 Days" · an internal memo
Most finance failures aren't accounting problems. They're system problems. Foreign keys missing. State machines absent. No webhooks. Excel as the database. I see them — and I write the diagnosis before I propose the fix.
I close the loop.
Five quarterly DD packages. Filed on time, every cycle. — institutional investors · single point of contact
Tax notice defended in Karnataka HC. First Big-4 audit in charge — four countries, closed in two months instead of six. $1M ODI to the US sub — cleared.
I learn out loud.
"The fix isn't working harder in December. It's front-loading the hard work to July–September so the only conversations are clarifications, not methodology debates." — bottom line of a 4,000-word postmortem I wrote after FY25
FY25 closed at the cost of nights nobody should work. The postmortem below is me admitting the December grind was the wrong fix — and what FY26 does instead. Postmortems after every cycle. Architecture diagrams. Diagnoses for the founder when something breaks. Documentation as discipline, not decoration.
Ten years from age 16 to running a four-country function.
Eight checkpoints. Seven years to qualify as a CA, another two-and-a-half before running the function.
Head of Finance, UrbanPiper (Series B+, four entities).
Team of seven, reporting to the founders.
FY27 plan, multi-entity consolidation, treasury, monthly close, audit, investor DD. Whatever the function needs.
And on the side — I built the system we run on.
Atlance — internal finance OS. 16 modules. 228 API endpoints. Replaced seven SaaS tools and a twenty-one-sheet workbook.
I write while I work.
Three docs from the last three months. Each one earned itself — written without prompt, because the thinking only landed once it was on paper.
Why MIS takes 15 days
(and how we're fixing it)
"It's like querying a database replica that's two weeks behind master. The data exists somewhere — just not in Zoho."
Finance memo to the founder, written in tech terms: ten cases where expense data leaks across vendor systems, Pazy queues, Excel, and people's heads. Each one diagnosed as a state machine problem, schema mismatch, or missing webhook.
FY26 Audit Prep — Lessons from FY25
"The fix isn't working harder in December. It's front-loading the hard work to July through September."
A four-thousand-word postmortem written after closing the FY25 statutory audit. Methodology debates, version-control failures, the Tushar escalation pattern, the audit-night 5-emails-after-9pm reality. With a plan for FY26 that removes them.
The Finance Transformation,
Mani × the Founder
The honest version of what the working relationship actually is.
An AI read every Slack DM between me and the founder from June 2025 to March 2026. No cherry-picking, no editing. Inheritance. Standards getting set. The audit crucible. The two-week WFH that became Atlance.
Locking April MRR. Townhall prep. Killing Zenskar.
Locking April MRR ahead of the Townhall. Finalising the homegrown billing flow that routes around Zenskar — Stripe for payments, Avalara for tax, Zoho for the ledger, and us in the middle. Prepping for the Retro meetup. The variance dashboard is running its first real cycle on April actuals. Reading Refactoring UI.
Open to advisory + investor conversations. Especially: founders rebuilding finance after a leadership exit, or finance leaders who want their function to ship software.
Always up for finance × ops × automation chats. Telugu-English mix is fine.
Click the email button to copy it — opens your mail client too if you have one set up.