For Indian enterprise software, the audit file is the product
Selling into regulated industries rewards documentation over benchmarks. Most engineering roadmaps are still built the other way round.
We lost two deals on documentation before I understood what we were actually selling. In both cases the platform performed. In both cases the customer wanted us to win. Procurement could not assemble an audit file from the artefacts we produced, and there is no benchmark that compensates for a missing artefact.
This is the part of the Indian enterprise market that engineering leaders coming from consumer or global-platform backgrounds consistently underestimate. A bank does not buy uptime. It buys evidence of uptime, in a format its regulator will accept, produced by a system its internal audit function can inspect without our help.
What that does to a roadmap
Roughly half our engineering organisation works on control-plane observability, compliance tooling and evidence generation. In a board deck this reads as overhead. It is the reason the other half has customers.
The uncomfortable implication is that feature velocity — the thing engineering organisations are usually optimised and celebrated for — is not the constraint on growth in this segment. Auditability is. And auditability work is unglamorous, hard to demo, and almost impossible to attribute to a specific closed deal.
A test
If your customer’s internal audit team cannot answer a question about your platform without emailing your support desk, you have not shipped the feature. You have shipped a dependency on yourself, and in regulated procurement that is a finding rather than a differentiator.