One surface. A whole tax season.

01 / The context

The problem behind the project.

A national accounting group engaged the practice directly for a staffed Tax Dashboard implementation. A fixed filing deadline meant staff needed a reliable view of return state and the ability to act without shuttling between disconnected applications.

02 / The contribution

How I approached it.

1. Led a seven-person delivery team—four core contributors and three specialists—over six weeks, including six production deployments during the implementation.
2. Composed the operating grid on the server and protected mixed desktop versions through an explicit version-aware contract.
3. Built a named twelve-step integration pipeline, preserving multiple vendor API generations when return identifiers changed mid-season.
4. Guarded destructive synchronization with volume assertions, repaired only unambiguous correlations, and logged why every repair occurred.

03 / The result

What the work made possible.

The operating surface carried roughly 7,500 individual returns in a season. Staff could send and track signature requests, retrieve signed artifacts, and file documents from the row, while the platform continued evolving during delivery.