A chartered accountancy practice's
tax-season cockpit,
built around the deadline and the client.
Iyer & Joshi was running a growing Pune CA practice on three spreadsheets, a shared inbox and a wall of paper folders. We replaced it with one cockpit the partners open every morning of tax season and a client portal that finally stopped the back-and-forth on email.
From three spreadsheets and a shared inbox to one cockpit the partners open every morning.
A practice that grew faster than its filing system.
Iyer & Joshi had built a name in Pune for tax and audit work done carefully, on time, by senior people who actually read the file. The work was strong. The way the work moved through the office was held together by memory.
Every January the season opened the same way. A spreadsheet of clients per partner. A second spreadsheet of filings per client. A third one for who owed what document. A shared inbox where documents arrived as attachments named “scan_001.pdf” and got renamed by hand. The juniors knew where things stood because they had been told. There was no one place to look.
By March the office was running on caffeine and goodwill. Filings did go out on time, but every one of them cost twice what it should have, in stress and in chasing. The partners knew what they wanted: the same picture of the season, on everyone's screen, every morning.
Three pieces that act like one practice.
A cockpit the partners open every morning
Every client, every filing, every deadline on one screen. Filter by partner, by week, by deadline, by status. Drill into a client and see the whole file: documents in, documents missing, filings drafted, filings reviewed, filings filed. The shared inbox stops being the source of truth.
- Single picture of the season
- Filter by partner, week, deadline, status
- Drill-through to the client file
A client portal that ends the email chase
Each client signs in and sees what the practice needs from them, in plain language, with deadlines that mean something. Form 16, bank statements, GST workings, investment proofs — uploaded once, named correctly, attached to the right filing. The juniors stop renaming attachments.
- Plain-language document requests
- Drag-and-drop upload, auto-filed
- Mobile-first, signed in by OTP
Documents
3 awaiting your upload
A filing tracker the team works through
Each filing is a card. Drafted, reviewed by partner, filed, acknowledged. Every transition leaves an audit trail with who did what and when. The senior partner stops asking for status updates. The juniors stop sending them.
- Draft → review → file → acknowledged
- Audit trail per filing
- Calendar export per partner
From a discovery week in Pune to a cockpit the partners run the season from.
- Week 01
Discovery
Three days at the Pune office, sitting through a January Monday morning end to end.
- Week 02
Plan
One-page spec, fixed scope, fixed price. Signed before any code shipped.
- Week 03
Build · α
Cockpit live for one partner as a pilot. The morning meeting moved off the spreadsheet.
- Week 04
Build · β
Client portal opened to a first cohort. Documents started landing in the right place.
- Week 05
Filing tracker
Draft → review → file workflow rolled in. Audit trail behind every transition.
- Week 06
Launch
Whole practice on the cockpit ahead of the March deadline. On retainer the same day.
Mature, boring, well-supported.
Nothing on the bleeding edge. Everything has documentation, a community, and a future. Iyer & Joshi can hire any competent engineer to maintain it.
- Front-end
- Next.js · React · Tailwind
- Client portal
- Next.js · OTP auth
- Back-end
- FastAPI · Postgres · Redis
- Document store
- S3 · server-side encryption
- Workflow
- State machine · audit log
- Telemetry
- Sentry · access log
For ten years our season was held together by spreadsheets and the fact that we remembered. Tanvora gave us a cockpit we open every morning, and a portal our clients actually use. The chase is gone.IJSuresh Iyer · Senior Partner · Iyer & JoshiPune