The Practice
Private Paradox is an Auckland advisory practice. The work is shaped by direct experience inside NZ regulatory institutions, law enforcement, and health sector operations — not by proximity to them.
Direct operational experience inside NZ government and enforcement environments.
AI productivity setup, regulatory compliance advisory, investigations.
Written proposal, defined deliverables, and a price you know before work starts.
How We Think
Most consulting businesses optimise for engagement length. The longer the engagement, the more revenue. Private Paradox is structured around the opposite logic.
Every package has a fixed scope and a defined end date. The goal is a client who doesn't need us again — not one who does. If they come back, it's because the work was good and the situation has changed, not because we left something deliberately unresolved.
That means being clear about limits from the first conversation. It means declining work that creates ambiguity about professional responsibility. And it means telling clients when the answer to their question is no — even when saying yes would be easier.
Every engagement starts with what we won't do. For a practitioner who's handing over access to their workflow, knowing the boundary is more important than knowing the capability.
Scope creep destroys trust. A client who gets exactly what was promised — no more, no less — is a client who refers others. Open-ended engagements end badly more often than not.
We do not create outputs that substitute for legal advice, clinical judgment, or regulatory opinion. The practitioner reviews everything before it's used. That's not a hedge — it's the right design.
Most compliance failures aren't about missing policies. They're about how organisations actually behave under pressure. Experience inside those environments is what makes this advice useful.
Experience Base
The practice draws on direct operational experience across several NZ institutional environments. That experience is what distinguishes advice grounded in how things actually work from advice grounded in how they're supposed to work.
Direct operational experience inside NZ government regulatory environments — working on compliance frameworks, enforcement operations, and continuous improvement from the inside. Understanding of how regulators actually prioritise and what they genuinely look for, not just what the legislation says.
→ Regulatory advisory · compliance strategy
Background in formal investigation environments — structured methodology, evidence handling, and the discipline of building findings that hold up under scrutiny. The analytical rigour developed in those contexts is what distinguishes defensible investigation work from informal inquiry.
→ Investigations · structured analysis
Operational leadership experience within health service environments, including direct exposure to health information governance, the real pressures of clinical settings, and what it takes to implement change in complex service organisations that resist it.
→ Specialist AI setup · health privacy constraints
Consulting work across financial services, professional practices, and owner-led businesses — spanning compliance design, technology implementation, operational review, and organisational problem-solving across NZ's regulatory environment.
→ All service lines
Hands-on experience building and deploying AI productivity systems in professional environments. Practical knowledge of what today's AI tools can and can't reliably do — and where professional, regulatory, and privacy obligations constrain what they should do.
→ AI setup for barristers and specialists
Every engagement runs to a defined scope with documented deliverables and a clear handover point. Change management experience in organisations where resistance to new processes is the default — not the exception.
→ All implementation work
Why It Matters
Anyone can read the AML/CFT Act or the Health Information Privacy Code. Understanding what a regulator actually looks for during a supervisory visit — how they prioritise, what language in a policy document raises flags, which gaps they'll pursue and which they won't — that comes from being inside those environments.
The same logic applies to AI implementation. Anyone can configure a tool. Knowing which workflows create professional liability risk, which data flows violate privacy obligations, and how to build a system that a regulator or disciplinary body would consider appropriate — that requires a different kind of background.
Start a ConversationI didn't want someone who'd read about regulatory compliance. I wanted someone who'd sat inside a regulatory body and understood how it actually thinks.
Client · Financial advisory firm · Wellington
The first conversation is free. Tell us what you're dealing with and we'll tell you plainly whether we can help — and what that would look like.