This post is a bookmark. A table of contents. A promise.
I’m building an end-to-end AI compliance automation system for a Chartered Accountant firm in India, and I’m documenting every step publicly on this blog.
The client is confidential. The systems are not.
Why This Series Exists
Most “AI automation” content is either:
- Vaporware demos that never touch production
- Enterprise case studies so abstracted they’re useless
- Tutorial content that stops at “Hello World”
This series is none of that. I’m shipping real systems, solving real problems — and writing about exactly what I built, what broke, what I learned, and what I’d do differently.
If you’re a CA firm thinking about automation, you’ll see exactly what’s possible. If you’re a builder in this space, you’ll get an honest technical playbook.
The Starting Point
I recently built and demonstrated the core proof-of-concept:
An AI agent that logs into India’s Income Tax e-Filing portal, navigates to e-Proceedings, identifies new notices, downloads the PDF, extracts key details, and sends a structured summary with the document attached via WhatsApp.
It worked on the first run — against a live portal with real data.
Read the full technical breakdown: I Built an AI Agent That Checks the Income Tax Portal and Sends Notices via WhatsApp
Read the strategic context: The CA Firm Automation Playbook
Who This Is For
CA firm founders and partners who want to see what automation actually looks like — not a sales pitch, but the real thing being built in real time.
Developers and AI builders interested in practical agentic workflow design — browser automation, document processing, multi-system orchestration.
Anyone in Indian tax/compliance tech who wants to understand where AI agents fit in the current landscape.
The Offer
I’m taking on a limited number of CA firms as automation clients. The system I’m building is designed to be replicated — each firm gets a customized instance tuned to their client portfolio, team structure, and workflow preferences.
Last updated: March 31, 2026. Check back regularly — this page evolves as the build progresses.