Skip to main content

Security Readiness Platform

A security-readiness assessment in production for a cybersecurity nonprofit (client confidential). It runs on Dynamics 365, Power Platform and Dataverse, with a Next.js front end. It was built over 12 implementation phases, and I have been its sole developer since June 2026.

Role
Director of Software Engineering
Organisation
Cybersecurity nonprofit (confidential)
Years
2025-2026
Status
In production
Phases Shipped
12
Private: client confidential2025-2026

What it is

Organizations take a 52-question security-readiness assessment across five areas: endpoints, identity, email, network and incident response. An assessor scores it, and the organization gets a report with a prioritized 30, 60 and 90-day plan. It runs in production, with Dynamics 365 and Dataverse as the system of record.

Version one lived inside the CRM

The first version was a Power Apps form on Dataverse, built over twelve implementation phases with a second developer: the data model, Power Automate orchestration, the assessor front end, and solution packaging so it could move from development to test to production.

It worked, but the form kept pushing back. Every new behavior meant another business rule layered onto it, and the CRM put hard limits on branding and layout.

Why I moved the front end out

I kept the data in the CRM and moved the experience out of it. The assessment became a Next.js app with Microsoft sign-in. Each organization gets its own link to take it, and results write back to Dataverse through its API. The CRM stays the one place an organization’s record lives; the app is a better way in.

I ported the scoring engine from the in-CRM JavaScript instead of rewriting it, so scores could not quietly change during the move.

Decisions I’d make again

  • Lock each assessment to the question version it started on. Questions change, and an assessment halfway done should not.
  • Generate the AI summary on the server only, so the API key never reaches the browser.
  • Port working logic before improving it. A rewrite and a migration at the same time make every difference impossible to explain.

What I’d do differently

Write tests that exercise real branches before trusting them. One of my early tests passed against code that was broken, because every mock value was empty and no branch ever ran.

And check that a release changed what is actually running, not only that the run went green.

Shares the most stack with this project

Need something like this built?

I take on select contract work. Tell me what you are building.