Engagement workspace
Each engagement lives in its own room — file tree, comments, sign-offs, and audit trail in one place. The right column is a per-row history that satisfies the regulator without slowing the auditor.
We set out to build the tool audit firms actually want — one place to run the whole engagement lifecycle: trial-balance import, risk, materiality, sampling, work programs, review and reporting. The status quo was a stack of spreadsheets and disconnected desktop tools.
Two of us. End to end. Strategy with their partners on Mondays, design through midweek, ship to staging on Friday. No PMs, no offshore handoffs, no slide decks.
Audit data is sensitive — government compliance had to be designed in from week one, not bolted on. The architecture, hosting, and data model all had to anticipate certification before we wrote a single line of UI.
Nine months later: ~250 pages, ~600 API endpoints, a living design system. Live in production and in active use by chartered-accountancy firms, hosted on AWS Mumbai, built to Indian compliance standards.
One backend. Two frontends. Twelve modules. The product-suite architecture lets the same engine power adjacent surfaces (AuditorsPro, CRM, HRM) without rewriting the spine.
Each engagement lives in its own room — file tree, comments, sign-offs, and audit trail in one place. The right column is a per-row history that satisfies the regulator without slowing the auditor.
Compliance checklists live as data, not as code. A partner can update an obligation in one place and it propagates to every active engagement that quarter.
Reviewers see only what needs them, in priority order. Hover any row to preview the file inline; sign off without leaving the queue.
Every write across the system feeds a single audit log that's queryable by entity, user, time, and field. Exports map to the formats the regulator expects.
AuditorsPro is live in production and in active use by chartered-accountancy firms — running on AWS Mumbai, with the uptime and audit-trail guarantees the work demands. You can see it live.
Compliance wasn't bolted on — it was designed in from week one: data residency, encryption, access control and a complete audit trail, all aligned to Indian audit standards. That decision is why the system holds up under scrutiny today.
Compliance had to be designed in from week one, not bolted on later. That single decisionshaped the architecture, the hosting, and the data model — and it's why the audit trail holds up under scrutiny today.