Transforming CCM into AI‑powered CXM.

So the job is to change it without pausing it. The move from Exstream Classic to Cloud Native was not a lift and shift: the template estate was rationalised on the way across, so what landed was smaller and more shared. It went in phases, each starting with its rollback plan, old and new running side by side until no customer could tell which had produced their document.

That only works if some things stay central. I keep template ownership, data formats and release cycles in one place — the three each business most wants to own, and the three that turn one platform into four. Cloud Native gave one of them back: business teams now change their own templates in Exstream Content Author, inside that governance rather than around it.

It is still one platform. Client confidential, so no link; the detail travels well in conversation.

I led an Exstream-based remediation program across banking and insurance lines — AODA-driven, governed to WCAG 2.x and PDF/UA — built on source-level remediation: accessibility rebuilt into the Exstream templates themselves, not patched onto PDFs after composition. Patch a PDF and the next batch run breaks it; rebuild the template and every document it generates is born accessible. More than 2,000 documents — statements, letters, policies, forms — crossed that line while live communications kept flowing.

I hold my own work to the same standard — this site is built and audited to it as well.

I owned the whole path: gathering the data, composing the documents, producing the print files, handing them to the mail stream. Three ways a document could be produced, all on the one platform: overnight batch, on demand in real time, and interactive — a bank employee composing a letter on screen before it went out. Along that path the old engines went — CSF and xPression retired onto Exstream, earlier Exstream applications brought forward, new ones built where none existed.

The hardest moment was a national portfolio takeover. The transfer date was fixed and not ours to move, so the first monthly cycle had to be right — no ramp-up, and no second cycle to fix it in. Transferred accounts arrived as a feed from the outgoing issuer in their own format; accounts opened after the transfer came from the bank’s systems. Two sources, one statement, both correct from the first run.

Those card statements carried marketing messages that changed every month, so business teams got a way to make the change and see exactly what would print before it printed — in Remote Collaboration, which did this long before Content Author existed.

When the portfolio went live, statements landed in mailboxes across Canada from the first cycle — people just called it their statement.

So I built my own agents in Microsoft 365 Copilot to take the first pass — one drafts the design document from the requirements, another drafts QA’s automated test cases from those same requirements and the data layout. I build a fresh set for each new project, since the requirements and the data differ every time.

Analysts, developers, and QA start from a draft, and the work reaches build sooner.

Math Academy is an adaptive learning platform: 30 curriculum-mapped units for Grade 7, a bank of 1,500+ questions, and a practice engine that adjusts difficulty as students answer.

It is in private testing today and expanding — more grades, new units, and question types land continuously. Public access opens when testing completes.