eMudhra digital signature India: a 240-seat Pune wealth firm consolidates signing
Last updated: 15 June 2026
The CTO opened the meeting with the wrong question. He asked which signing platform was best. That is not actually the question for a wealth firm signing 14,000 client documents a month from a Baner Road office, and eMudhra digital signature India consolidation rarely starts there.
The question was simpler. How many signing systems can one 240-seat firm actually run without losing the audit trail. I have seen this debate land in vendor demos and renewal emails. Neither is where the answer lives.
What was on the table at the Q3 review
240 advisors and ops staff across two floors, ~INR 9,400 crore AUM, regulated under SEBI as a registered investment adviser plus a separate distribution arm. The signing surface looked like this.
DocuSign for board resolutions and HR offer letters, INR 18.6 lakh annual, ~3,200 envelopes a month. A separate India-CA for Class 3 individual DSCs, six different vendors over four years because every advisor renewed wherever was cheapest that month. A custom-built HSM signing API on a single Oracle DB for the AUM advisory mandate flow, written in 2020 by an engineer who has since left.
And then there was the auditor’s finding from March. Two DSC issuance events had no traceable approval. The advisors had renewed personally through a reseller, used the DSC to sign mandate amendments, and nobody at the firm could prove who authorised what.
Anil, the CTO, wanted to keep the best-of-breed stack and add a logging layer over the DSC vendors. I came in pushing for eMudhra full stack. The CFO was in the room. He had two questions, both about money.
Why I went in convinced, then changed half my mind
I came in thinking eMudhra would obviously win. Indian CA, in-region log residency, the eMudhra emSigner platform covers board signing and bulk advisor signing and mandate APIs on one engine, and emCA gateway lets you issue Class 3 DSCs through the firm rather than the advisor wandering off to a reseller. One stack, one log, one renewal date.
Three calls and one spreadsheet later, I changed half my mind.
The half that stayed: emSigner plus emCA inside the firm replaces DocuSign for the internal signing surface and ends the DSC renewal chaos. That part is settled.
The half that flipped: I had assumed we could move external counterparty signing off DocuSign too. We can’t. The firm’s three biggest custodians already use DocuSign internally and send envelopes through their own account. Moving the advisor to eMudhra means asking the custodian to change their workflow. Nobody is changing their workflow for a 240-seat firm. Accept that and move on.
The final architecture: eMudhra for everything inside the firm. DocuSign on a 30-seat downsized contract for the external envelopes that arrive from counterparties. Two stacks, not four, and the two that matter live under one log.
Get my eMudhra signing-stack consolidation quote
The CFO question that actually broke the tie
The CFO asked one thing. What does a single advisor cost to sign on each option, fully loaded, including DSC, the platform fee, and a fair share of the engineer time we spend keeping it running.
It is not a clean question. Per-envelope SKU shifts every year. Vendor base fee depends on seat count tier. The custom Oracle API costs about INR 4.4 lakh a year in engineer time and another INR 1.1 lakh in Oracle licensing that nobody on procurement reads. So we built the math. Here is the table he wrote on the whiteboard.
| Cost line (36 months, 240 seats) | Stitched stack (current) | Consolidated on eMudhra + small DocuSign |
|---|---|---|
| DocuSign Business Premium base | INR 55.8 lakh | INR 8.4 lakh (30-seat tier) |
| eMudhra emSigner + emCA platform | 0 | INR 29.4 lakh |
| Class 3 DSCs (240 individuals, 36 months, ~INR 2,600 retail vs ~INR 900 in-house) | INR 18.7 lakh | INR 6.5 lakh |
| Custom Oracle HSM API (engineer + licence) | INR 16.5 lakh | 0 (retired) |
| Audit + reconciliation effort (CA partner) | INR 8.0 lakh | INR 2.4 lakh (single log) |
| 36-month total | INR 99.0 lakh | INR 46.7 lakh |
That is the 41% number Anil walked out of the room repeating. He still wanted best-of-breed in principle. The number was harder to argue with than the principle.
The DPDP and SEBI ledger that nudged the CTO
The CFO got us to the number. The compliance head got us to the decision.
Under DPDP, every advisor mandate carries client personal data and signing metadata. The auditor reads the trail end to end. Three signing systems with three separate logs means three reconciliation exercises every quarter. One signing system means one reconciliation. Pakka operational risk reduction, not just a TCO line.
SEBI’s adviser regulation is more specific. The mandate audit trail must show who signed, when, and from which authenticated identity. Class 3 DSCs from emCA gateway issued inside the firm satisfy this cleanly because the firm controls the issuance approval. DSCs bought retail by the advisor through a reseller do not, and that is what the March finding flagged.
The compliance head pulled up the MeitY DPDP Act framework on screen and read the bit about data fiduciaries demonstrating a documented foundation for processing personal data. He pointed at “documented.” The custom Oracle API does not. It has an engineer who left in November.
For the SEBI piece, the RBI digital signing notification changes how loan and investment authorisation flow through DSCs, and the firm’s distribution arm is exposed there too. eMudhra has a current empanelment record. The custom Oracle API does not.
One reconciliation, one empanelment, one log. That is the argument that finished the meeting.
How we sequenced the cutover
This is where most consolidation stories go wrong. Big-bang switches break things. We did not big-bang it.
Week 1 to 3, eMudhra emSigner stood up as a parallel signing path for board resolutions and HR letters. DocuSign kept running. We ran 38 envelopes through emSigner in parallel with DocuSign to validate the audit trail format against what the SEBI auditor expected. Two formatting tweaks on the signing certificate page, one DocuSign branding strip from the PDF template, done.
Week 4 to 6, emCA gateway came online for Class 3 DSC issuance. First 12 advisors issued through emCA. The IT head signed off the issuance approval workflow personally because the auditor wanted a named approver in the workflow, not “system.” The remaining 228 advisors moved off retail DSCs as they came up for renewal, which staggers across the year. Nobody had to renew early just for the rollout.
Week 7 to 10, the custom Oracle HSM API for AUM mandate signing got rebuilt against emSigner APIs. This is where most engineering hours went. Two of the original API integration points needed renaming, and the HSM key migration took a long Saturday. We scheduled it for the weekend before quarter-end so the Monday board meeting was on the new path.
Week 11, DocuSign downsized to 30 seats for external envelopes. The contract amendment took longer than the technical work.
Talk to us about your signing-stack cutover plan
What I would tell a friend planning eMudhra digital signature India consolidation
Three things. First, do not let the platform debate happen at the platform level. Do it at the per-advisor fully-loaded cost level. The platform features are similar enough on paper that the per-envelope screen demo does not separate them. The 36-month math does.
Second, the DSC issuance vector is the audit risk most firms miss. If your advisors are buying their own DSCs through resellers and using them to sign anything client-facing, you have a March-finding problem waiting. emCA gateway is the cheapest fix because it puts the issuance under firm control. DPDP compliance packaging and DSC governance live in the same ledger now, treat them that way.
Third, do not pretend you can fully retire DocuSign at a 240-seat firm. External counterparties are why. Keep a small DocuSign contract for the envelopes that arrive from custodians. Negotiate the seat-count downsize at renewal, not before, because the rep will take the call when the term ends, not in month four.
One back-pocket warning. eMudhra licensing has a per-signing-event tier that resets at higher seat counts. If your seat count crosses 350, the per-event price book changes. Watch that line at every renewal.
Karthik’s takeaways
FAQ
Is eMudhra emSigner a full DocuSign replacement for an Indian wealth firm?
For everything signed inside the firm, yes. emSigner handles board resolutions, HR letters, AUM mandate flows, and bulk advisor signing. For external envelopes that custodians or AMCs send from their own DocuSign account, keep a small DocuSign seat count. It is cheaper and faster than asking the counterparty to change their stack.
What is the audit benefit of emCA gateway over advisors buying retail DSCs?
emCA puts DSC issuance approval inside the firm’s workflow. A named approver authorises every Class 3 DSC, the log lives with the firm, and the SEBI auditor can trace who signed what mandate from which authenticated identity. Retail DSCs bought by advisors through resellers do not give the firm that chain.
Does eMudhra meet DPDP data residency requirements?
eMudhra is an Indian Certifying Authority licensed under the IT Act and runs the signing log infrastructure in India. For a DPDP audit, the data fiduciary needs to show where personal data and signing metadata sit. With eMudhra and emCA, both stay in India under documented controls referenced against the ISO 27001 control set. DocuSign global accounts route through their own regional infrastructure, which is a separate conversation.
How long does a 240-seat eMudhra consolidation take in practice?
About 11 weeks if you sequence it. Three weeks of parallel running on board signing, three weeks for emCA gateway issuance, four weeks on the custom-API rebuild, one week for the DocuSign contract downsize. The technical work is rarely the gating item. The contract amendment is.
P.S. Karthik here. We have shipped a similar consolidation for a Mumbai-based NBFC last quarter and a Pune wealth shop the quarter before. The number that surprised the CFO every time was the custom-API line. If you have an internal signing API written by an engineer who has since moved on, audit it before the next quarterly review. The licensing under it usually costs more than the API earns. Reply on WhatsApp and we will scope a signing-stack consolidation for your firm in a single 45-minute call.
Start my eMudhra consolidation conversation
CERT-In incident timelines and SEBI mandate audit rules are the two we cite most when planning a signing consolidation.
Related reading: the emSigner vs DocuSign argument from a Pune fintech, the Veritas NetBackup renewal at a Pune wealth firm, and the DPDP Rules 2025 Mumbai bank CIO day.
