Most CA firm client portals are a login screen bolted onto a practice management product. The client gets a username and password, signs in once, sees a list of folders, and never comes back. The partner gets one more dashboard to ignore. The articleship staff still chase Form 16s on WhatsApp. Calling that a client portal is generous.
A real one does six jobs and looks nothing like a tab in your practice management product. This post is the framework we use when a firm asks us what to build — written for senior partners and practice managers at Indian CA firms with somewhere between eight and sixty fee-earners, where the cost of getting this wrong is two more tax seasons of WhatsApp groups and missing documents.
What a client portal is actually supposed to do
The phrase "client portal" gets used to mean five different things in vendor decks. Before you buy or build anything, name the jobs you want it to do. The honest list is six.
- Document collection on a per-client checklist. Form 16s, bank statements, sales and purchase registers, capital gains statements, foreign asset disclosures, GST workings. Each client has a known list of what's owed each month or quarter. The portal's job is to pull files into a structured per-engagement folder without anyone re-typing what they are.
- Live status visibility. For every active engagement: where is it. Documents pending, return drafted, partner reviewed, filed, e-verified, paid. The client should be able to see it without calling. The partner should be able to see all of it across forty clients on one screen.
- E-signature and approval. Engagement letters, return drafts before filing, audit reports, balance confirmations, vakalatnamas where the firm handles incidental representation. Every signature that today travels via printed PDF and WhatsApp.
- Payment. Invoices visible to the client, paid via UPI or card without a phone call. Receipts back into the books automatically.
- An auditable communication log per matter. Every WhatsApp, every email, every call log, attached to a specific client and engagement, exportable. This is the job the rest of the industry under-discusses, and it's the one that protects the firm in a peer review or a client dispute.
- A partner cockpit. One filter (partner), one screen, every client in their book, every column above. Pulls from the practice management product, the books, the WhatsApp gateway, the e-signature provider, the payment gateway. Refreshes in real time. Sends a Monday summary.
Count the products on the market that do all six well. The honest answer is none. The packaged Indian products — Practive, Jamku, ERPCA, ATOM, QwikCA, CAdesk, Turia, Vider, Bizalys — each do two or three of the six, with very different angles. The global ones — TaxDome, Karbon, Canopy — do four or five but miss Indian compliance. Which is fine. The job isn't to find the one product that does all six. It's to know which job each tool you own is solving, and to own the seams.
Why the packaged story breaks
Indian CA practice management products have grown up. For a single-office firm under ten fee-earners running mostly compliance work, one of them is the right answer. Pick the one whose support team picks up the phone, run it for a year, stop evaluating.
The packaged story breaks at three thresholds, in this order. The first is multi-partner allocation: the moment originating partner shares, supervisory overrides, and advisory cross-charges diverge from the product's defaults, you're back to exporting and reconciling in Excel. The second is multi-service: a firm doing audit, tax, and advisory in roughly equal weights has three different matter shapes, and packaged products are usually strong in one. The third is client document volume at scale — once you're collecting fifty documents a week across forty clients, rigid checklist trees start losing files, and the partners start asking why a five-rupee Drive folder works better.
At any of those three thresholds, the leverage stops being in replacing the practice management product and starts being in building the layer on top. That's the layer most firms don't build, because it isn't what their vendor sells them.
The communication audit log nobody talks about
If you read the marketing pages of every Indian CA portal product, you'll notice something. They all talk about document collection. Most talk about status visibility. A few talk about e-signature and payment. Almost none talk about a per-matter communication log.
That's the most important job and also the quietest one. It's the difference between a partner being able to defend a position in a peer review or a client dispute and a partner having to scroll through three years of WhatsApp messages on a phone they no longer use. The DPDP Act made it more important — now every WhatsApp message containing client financial data is, technically, regulated personal data with audit obligations.
A real portal logs every WhatsApp interaction (via the Official WhatsApp Business API, not a screen-scraping bot), every email sent or received in a matter mailbox, every call note, against the engagement. The articleship staff don't have to think about it; the system does the attribution. When a partner needs to defend a filing decision two years later, they pull the log and it's there.
This is the single feature most likely to be missing from a packaged tool and most likely to matter when it counts.
WhatsApp first, web second
Indian SMB clients run their businesses from a phone. They will not log in to your portal weekly. They might log in once when you onboard them and never again. If your document collection lives behind a web login, you will be chasing them on WhatsApp anyway, which means you've added a portal cost without removing a WhatsApp cost.
The correct architecture is the inverse. WhatsApp is the front door for ninety percent of client interaction — checklist nudges, document upload, status queries, payment links, signature reminders. The web view exists for the ten percent that needs structured input or formal e-signature. You bill once for both, you log everything in one place, and the partner cockpit reflects all of it.
The technical caveat: use the Official WhatsApp Business API. Unofficial bots get banned, and a banned business number on the day before a GST deadline is the kind of incident a firm doesn't recover from. The Official API is more expensive per conversation; it is also the only version that survives.
Where firms get the e-signature decision wrong
E-signature is the second under-discussed feature. Most Indian CA firms still print engagement letters, scan signatures, and email PDFs back. For client review approvals before a return is filed, the dance is worse — a draft over WhatsApp, a verbal approval, a partner signing on their behalf, a hope that no one ever asks.
A portal that does e-signature properly captures intent in a way that holds up under scrutiny: timestamp, IP address, OTP verification, an audit trail. The Indian Information Technology Act recognises Aadhaar-based e-signature; for non-Aadhaar flows, OTP-based consent with proper audit logging is the working standard. Either is dramatically better than a scanned PDF.
The reason this matters more than partners think: the average tax season ships dozens of engagement-letter signatures, hundreds of return-draft approvals, and a handful of audit-report sign-offs. Every one of those is a friction point that today costs five to fifteen minutes of a senior associate's time. Removing that friction across a season is two associate-weeks of capacity.
What we'd build first if we were a 22-fee-earner Mumbai CA firm
Start with the lowest-leverage thing first and shipped before October.
- Phase 1, weeks 1–4: WhatsApp-first document collection and status visibility. Per-client checklist, WhatsApp Business API for nudges and uploads, files routed to a structured per-engagement folder, status visible to the client and the partner. Sits on top of your existing practice management product. Pulls deadlines from the filing tool, status from the practice management product, document state from the portal itself.
- Phase 2, weeks 5–7: E-signature and payment. OTP-based e-signature for engagement letters and return-draft approvals; Razorpay or Stripe for invoice payment; receipt sync back into the books.
- Phase 3, weeks 8–10: Communication audit log and partner cockpit. Every WhatsApp, every email, every call note attributed to a matter. One screen per partner, every client, every column. Monday morning summary.
We've shipped a version of this for Iyer & Joshi — a tax-season cockpit, client portal, and filing tracker built before March, sitting on top of their existing Winman and Tally setup. The build was six weeks of focused work; the change in how a Monday morning feels was visible by the second tax season.
For a 15–40 fee-earner firm with reasonable integration ambition, the realistic budget for a phased build like this is INR 8–14L, plus a 35k–60k/month retainer after launch covering compliance updates, client onboarding, and the small features that always surface in the first six months of real use. That's an order of magnitude more than a packaged portal subscription, and it does an order of magnitude more.
Buy, build, or hybrid
We get asked the binary version of this question — buy or build — and the honest answer is almost always hybrid. Don't replace what works. Don't build what's commoditised. Buy the boring core: practice management for tasks and timesheets, packaged software for return prep and computation, an Indian books product. Build the layer that's specific to your firm: client document collection, status visibility, the partner cockpit, the communication log. That's where the leverage is, and it's also where every packaged product is weakest.
If you're under ten fee-earners and mostly compliance, skip the build entirely and pick a packaged Indian product. If you're over forty fee-earners with serious advisory volume and multi-partner allocation, the build pays for itself in the first tax season. The hard cases are the firms in between — twelve to thirty-five fee-earners, growing, mixed practice. For those, the question is less "buy or build" and more "what's the smallest custom layer that removes the most pain," which is usually document collection plus the partner cockpit, in that order.
For canonical reference on confidentiality obligations, peer review templates, and UDIN compliance, the ICAI's official site is the source of truth. Packaged products' interpretations of compliance rules drift, and a partner should always be able to point to the rule itself when a client asks why a workflow is what it is.
What good looks like, six months in
The signal that the portal is working isn't the dashboard view count or the upload metric. It's quieter than that.
Articleship staff stop spending Friday afternoons on document chase calls. Partners stop being interrupted by "is my return filed" WhatsApp messages from clients. Junior associates stop being the human glue between the books, the filing tool, and the practice management product. A new client onboards in a single sitting because the portal walked them through it. A peer review goes smoothly because the audit log is exportable. A Monday morning starts with a one-page summary that's already true rather than a partner meeting that takes ninety minutes to become true.
That's the quiet test. If your client portal isn't doing those things six months in, it's a login screen, not a portal. The job isn't done.
If you're a partner thinking about this seriously and want a second opinion that isn't trying to sell you a product, send us a note. We'll tell you when to buy a packaged product, when to build the custom layer on top, and when the right answer is to fix the process before touching any software at all — and we lose work in each direction often enough that we mean it.
Sources: