A policy nobody’s read isn’t a policy. It’s a PDF. Here’s how we make sure that never happens to
you
Most compliance work happens backwards: a provider adopts a tool, someone gets nervous,
and governance gets written after the fact to explain what already happened. By then it’s not
governance. It’s damage control.
We flip the order. Every engagement starts with understanding how your team actually works
and where AI already is in your organisation, whether anyone’s approved it or not.
We start with your reality, not our template.
We walk in your shoes and speak your language,
always, not just when it’s convenient. Before anything gets designed, we understand your
workflows, your team, and where the real risk sits, not where a generic checklist says it should.
We build the governance, then the tools.
A policy that sits in a drawer protects no one. We
build governance your team will actually use, clear enough that a support worker can follow it,
specific enough that it holds up in an audit.
We stay in it with you.
True partnership, nothing held back. That means full transparency on
what’s working, what isn’t, and what needs to change, including the uncomfortable calls,
because a problem surfaced early is manageable and one concealed is not.
We show you proof, not potential.
We’d rather demonstrate delivery than sell you on what’s
possible. That’s why every engagement is built around real, measurable outcomes for your
organisation, not a roadmap of what AI could someday do
We activate ownership inside your team, not just outside it.
Governance only sticks if
someone inside your organisation owns it. Where it makes sense, we help you stand up a
named role, an AI Governance Lead, a Pilot Champion, and hand over ownership before we go,
so the framework doesn’t depend on us staying in the room.
What this looks like in practice
Engagements typically move through four stages: a foundation phase to map where you actually stand, a baseline to agree what “audit-ready” looks like for your organisation, a build phase for the governance and any AI implementation, and an ongoing phase once the framework’s live and running.
How long each stage takes depends on where you’re starting from, not a fixed timeline handed to you on day one.
For a medium-sized NDIS provider, this typically means starting with a Discovery Call. As part of
that call, we map exactly where you stand, not just where a generic form assumes you are.
From there, we scope the engagement (compliance review, audit-readiness preparation, or AI
implementation support) to what that provider actually needs, not a fixed package.
