AI Enablement · Prepared for Diversi Consulting

Automating the handoffs, not the firm

A phased plan for building a lightweight workflow layer on the Microsoft 365 environment Diversi already runs — starting with one automation, proven, before anything bigger is on the table.

4 phasesDiscovery through scale
Power PlatformBuilt on M365, not bolted on
One pilot firstValue proven before scope grows
The Approach

Sized for a five-person senior team, not an enterprise

Diversi doesn't need a case management platform. It needs the repetitive handoffs — correspondence, compliance tracking, status updates — taken off senior engineers' plates, without adding a system they have to maintain themselves.

01

Narrow first

One workflow, one clear owner, one measurable outcome — not a rebuild of the whole project lifecycle.

02

Proof before scale

Every phase after the pilot is a decision point, not a foregone commitment. Results earn the next step.

03

Netcare-supported

The automations live on infrastructure Netcare already manages — no new system for Diversi to own or patch.

The Roadmap

Four phases, each earning the next

Every stage produces something usable on its own. Nothing past Phase 1 is scheduled until the pilot has shown its worth.

Phase 0 · Discovery & Scoping2–3 weeks

Map the real workflow

Before any build, understand exactly where time and certainty get lost in Diversi's own delivery process.

  • Map the project lifecycle end to end — intake through DA, CC, construction admin, and close-out
  • Inventory current systems: SharePoint structure, job tracking, how council/developer correspondence is logged today
  • Select one narrow, high-friction workflow to pilot — not the whole lifecycle
OutputOne scoped pilot workflow with agreed success metrics
Phase 1 · Pilot4–6 weeks

Build the one workflow that matters most

A single automation, built end to end and used on live projects — not a demo.

  • Incoming correspondence auto-classified, logged, and routed to the right engineer
  • A Copilot Studio agent trained on Diversi's own templates and precedents drafts the first response
  • Deadlines tracked automatically instead of manually
OutputOne live automation, measured in hours saved and deadlines met
Phase 2 · ExpandOnce the pilot proves out

Extend the same pattern

Only after Phase 1 earns its keep — apply the proven approach to the next highest-friction workflow.

  • Add 1–2 more workflows — likely compliance checklist tracking or project cost visibility
  • Begin connecting workflows so status updates pull from the automations, not manual reporting
Output2–3 workflows live; less time spent on manual status updates
Phase 3 · Scale & EmbedLonger term

Tie it together, deliberately

A connected view of active projects — only once enough workflows are live and trusted to justify it.

  • A lightweight central project dashboard (Power Apps) drawing on the existing automations
  • A clear ownership model — the system stays Netcare-supported, not a new burden on Diversi's team
OutputA connected workflow system with defined, sustainable ownership

Prove it small. Then decide.

The first step doesn't need to be large — it needs to be useful, and it needs to be proof. That's the basis for every conversation that follows.

  • Matches the risk appetite of a senior, five-person team with no dedicated IT resource
  • Gives a concrete result to evaluate before any larger commitment is discussed
  • Keeps the system inside infrastructure Netcare already supports