MCP-AIPractice intelligence

How it fits the firm's stack

MCP-AI is a layer, not a migration. It reads from the systems the firm already runs, joins what they each know, and hands drafts to people for the decisions.

FYI Elite

Documents, jobs & automations

MCP-AI: Reads documents and job state · writes tasks and filed copies back.

Xero

Client financials

MCP-AI: Reads P&L, balances and GST figures · writes nothing back.

MCP-AI

Practice intelligence layer

Microsoft 365 + Copilot

Email, files & meetings

MCP-AI: Reads the shared inboxes · writes back only replies a person has approved.

IRD myIR

Filings & assessments

MCP-AI: Reads due dates and assessments · filings stay with the team.

Sits beside the stack — never replaces it.

Real vs simulated

An honest demo labels its edges. Here is exactly where they are.

Real in this demo

  • The NZ tax-calendar rules engine — GST, provisional, terminal, returns, FBT — with tests
  • RAG status logic: every red and amber shows its reasons
  • The workflow tracker's maths — capacity in weeks of work, job costing against a margin target, weekly KPI grading
  • Scenario maths — the payout slider and the uplift comparison
  • The full UI you're clicking through, on your own sandboxed data
  • The audit trail — every action logged with who, what and when

Simulated — and badged as such

  • The Xero adapter — sample financials shaped like real Xero reports, draft invoices pushed nowhere
  • Email sends — drafted and approved for real, delivered nowhere
  • The document store — seeded documents standing in for FYI Elite
  • Practice-system jobs — the tracker's job book is seeded, not synced
  • The 48 sample clients and 14 sample staff — invented, any resemblance coincidental

From demo to production

The demo was built around three deliberate seams, so “make it real” is a swap at each seam — not a rewrite.

Repository → Firestore/Postgres

The UI only ever talks to a repository layer, so the in-browser store swaps for a real database without touching a single screen.

Integration adapters → real APIs

Each simulated adapter shares its interface with the real one — Xero OAuth, Microsoft Graph and FYI Elite slot straight in.

Reports as pure selectors

Every number on every card comes from one set of pure, tested functions — production analytics are the same code over real data.

A phased path

1

Pilot

One office, read-only Xero and the compliance radar — value visible in weeks, nothing written back.

2

Phase 2

Inbox triage and reminders, every outbound message behind a human approval.

3

Phase 3

Client insight and document intelligence across all four offices.

Built with zero client credentials. Production hardening — SSO via Microsoft 365, audit, backup and NZ data-residency choices — is scoped at kickoff, not discovered later.

NZ Privacy Act posture

Data minimisation by design, purpose-limited access, and NZ data-residency options on the table from day one.

Humans approve everything outbound

MCP-AI drafts; a person sends. No reminder, reply or filing moves without an approval.

Every action audited

Filings, sends, syncs and triage all land in the audit trail — who, what and when, reviewable at any time.