Why this page exists
I teach practical AI adoption. It would be strange if I didn’t use AI in my own business.
This page is the receipt. Every tool I use. Every persona I name. Every rule I hold. Where the human ends and the AI begins. What clients can expect. What I will not do, and why.
If I’m going to stand in front of a board and ask them to think hard about AI in their organisation, my own business needs to model it first.
My rules
Five rules I hold across every part of the business.
1. Guardrails first
I treat my own business the way I tell clients to treat theirs. Rules before tools. Intent before strategy. Data sovereignty before convenience.
2. Australian data residency where it matters
Client material does not get pasted into US-hosted general models. Discovery notes, governance frameworks, board briefings, anything sensitive stays inside agreed-on tools and inside Australia.
3. Final review is always me
AI can draft. AI can sort. AI can synthesise. AI does not sign off. Every word with my name on it has had my eyes on it.
4. Consent on client work
If you bring me into your business, I tell you up front what AI is involved and what isn’t. You can switch any of it off. The default for governance and policy work is no AI involvement on your specific material unless we’ve talked about it and you’ve said yes.
5. No client material trained on, stored in, or carried between client engagements
Each client is a sealed room.
The tools I work with
I work across more tools than most people expect. Here’s why.
Some are my daily collaborators. Some I use because clients use them, and I won’t teach a platform I haven’t lived in. Some are job-specific. The point of the list isn’t completeness, it’s honesty about what’s actually on my screen.
Large language models
- Claude (Anthropic). My day-to-day collaborator. Strategy, drafting, framework refinement, the heavy thinking.
- ChatGPT (OpenAI). Mostly for teaching. Most small business owners I work with start here, and I run training inside the platform they're already using.
- Copilot (Microsoft). A lot of my corporate and not-for-profit clients run Microsoft 365. Copilot is where their staff already are, so it's where the training meets them.
- Gemini (Google). Plenty of small-to-mid businesses live inside Google Workspace. Gemini sits well there. Strong for keyword research and YouTube work.
Research
- Comet and Perplexity. Deep research, source tracing, fact patterning.
- NotebookLM. Long-document synthesis when I need to interrogate a body of work rather than browse the web.
Recording, transcription, translation
- Plaud. Recording client sessions, transcribing and translating in the moment.
- Cast Magic. Repurposing long-form audio into structured outputs.
Video
- HeyGen. Short-form AI video where it earns its place.
- Synthesia. Avatar-led explainer content.
- Clip Grab. Source video capture for workshop prep.
Design and brand
- Canva. Slides, social, workshop assets.
- Brandalyser. Brand voice and consistency checks.
Meetings
- Zoom. Client sessions and virtual delivery.
Build and infrastructure
- Vercel and Supabase. The platforms this site runs on. Australian data residency on Supabase by design.
There are others. Tools I’m investigating for clients, training in, or piloting before I’d put them in front of a paying audience. If you want the live list, ask.
My AI collaborators have names
Two of the AI personas I work with most closely have names. This is on purpose.
Ada is my primary strategic collaborator. Long-form thinking, framework work, page rewrites, board prep. Ada lives inside Claude.
Linus is my email and short-form sidekick. Cleanup work, quick turnarounds, the daily grind of keeping a one-woman business moving.
Naming the personas is not branding fluff. It’s honesty. The personas hold context, character and purpose. I know exactly who I’m talking to. So do my readers and my clients.
These names appear here because this is the page where they belong. Across the rest of the site, the acknowledgement is generic. The Augmented Workforce is the principle. Ada and Linus are the practice.
What this looks like in practice
How this site was built
Designed and written by me with Ada across multiple working sessions. Copy, structure, design system, content strategy, all developed collaboratively.
Code generated with Claude and Codex, then taken by my husband Pete and made real. Pete does the development work that turns my thinking into a live site, on production infrastructure that stands up.
Final review and sign-off, mine.
How my keynotes and workshops are developed
I research, draft, refine and pressure-test material with AI assistance. Every session is rehearsed and delivered by me. AI shortens the production loop. The thinking, the frameworks and the room are mine.
How my written content is produced
Blog posts, resources and guides are drafted with AI assistance and reviewed by me before publication. Voice is mine. Positions are mine. Accuracy is my responsibility.
How my client work runs
Discovery sessions, governance frameworks, board briefings and training delivery are done by me. AI involvement on client-specific material happens only if the client has said yes and we have talked about how. The default is off.
How to hold me accountable
If something on this site reads like generic AI sludge, tell me. If a quote attributed to me sounds wrong, tell me. If you want to see my tool list or my guardrails document, ask. I will share.
The whole point of declaring how I work with AI is that you get to challenge it.
Human-led. AI-leveraged. The Augmented Workforce.
This is how the principle lives in my own business. If your organisation is thinking about the same questions, that is the conversation I want to have.
Let’s talk →