Accountancy practice — governance retrofit in delivery cadence

Anonymised by industry. The client’s identity is withheld pending consent.

Industry shape

An accountancy practice — accountants, bookkeepers, BAS agents, tax agents — operating with a mix of practice-management software, spreadsheets for client onboarding, scattered document collection across email + cloud-drive sprawl, manual lodgement tracking, and peer-review checklists in Word documents. Mid-market scale (the engagement covered the practice from one principal up through 20–40 staff capacity).

What the platform replaced

• Email + Dropbox + SharePoint sprawl for client document collection — no traceability of what was requested vs received
• Manual BAS / IAS / FBT lodgement tracker in a single shared spreadsheet
• Working-paper management via shared drives with no version control
• Peer-review checklists in Word, emailed back and forth
• TPB and APES 110 compliance touchpoints tracked on a separate spreadsheet, easy to miss

What XCentral delivered

• Staff portal with consolidated client onboarding workflow
• Document collection portal (client-facing) with request-tracking, expected-vs-received status, audit trail
• BAS / IAS / FBT lodgement tracker integrated with the ATO submission cycle
• Working-paper management with version history and role-based access
• Peer-review checklist as platform module with workflow routing
• TPB and APES 110 compliance touchpoint tracking integrated into the engagement record

Governance work delivered alongside the build

This is what makes this case study unusual:

• MASTER specification document + multi-phase specs authored in the framework’s specification format
• A substantial backfill of retrospective work items in Azure DevOps to align project history with the framework’s governance model
• Framework version upgrade applied to the project in the same window as Phase 2 delivery (no separate maintenance project required)
• Built under the framework’s full governance discipline — Clean Architecture, spec-driven delivery, and a complete audit trail

Velocity

• Phase 1 staff portal — dev and staging deployed; production Entra ID app registration configured; production infrastructure prepared but not provisioned
• Estimation variance on completed phases: single-digit percentage

Hours comparison

Compression: 4–5× — plus the rare bonus: most agencies wouldn’t ship a governance retrofit as part of Phase 1.

The framework’s spec-workflow makes the governance retrofit a background task in delivery cadence, not a separate engagement.