Evidence
System surface
No public screenshot on file, generative preview stands in for the visual layer.
Story arc
How this shipped
Where I learned to build at scale and lead teamsThree beats: what pressed against the work, how the stack answered, and what changed once it was live.
I · Constraint
The brief
A healthcare cybersecurity nonprofit needed a structured MSP-readiness assessment with auditable scoring and multi-stakeholder flows. The original in-CRM Power Apps front-end hit customization limits, so the assessor experience needed to move out of Dynamics without giving up Dataverse as the source of truth.
II · Build
The craft
Built the platform in two arcs. First, a 12-phase Dynamics 365 / Power Platform implementation: a governed Dataverse data model, Power Automate scoring orchestration, and repeatable cross-environment solution packaging. Then externalized the front-end into a Next.js 16 + React 19 app on Vercel that reads and writes Dataverse directly, replacing the in-CRM Power Apps Canvas UI while keeping Dynamics 365 as the system of record.
III · Proof
What moved after launch
Live in production at msp.cyberready.clinic. Externalizing the front-end removed the Power Apps customization ceiling and put the assessor UI fully under version control, while the internal team keeps ownership of the Dataverse platform behind it.
Signals
Signals & scale
Inventory