Why I Built an AI Employee for NDIS Providers (And What I Learned From 6 Months in the Groups)

I am a Systems Engineer by day. I build infrastructure, automate workflows, and solve problems that slow people down. That lens — seeing inefficiency and wanting to fix it — is what eventually led me to build ContentAutoPilot.

But the product didn't start with a business plan. It started with my sister.

The 45-minute problem nobody talks about

My sister runs an NDIS organisation in Australia. She is good at what she does — genuinely cares about participants, builds real relationships with support workers, and runs a tight operation.

But every single shift, her workers were spending 30 to 45 minutes on documentation after the care was done. Progress notes. Incident reports. Shift handovers. Support plans. Each one written from scratch, each one needing to meet the NDIS Commission's standards, each one a potential audit risk if the wording wasn't right.

Multiply that by every worker, every shift, every week.

I watched support workers stay back after their shifts. I watched coordinators rewrite notes at 11pm because a worker's handover didn't capture the right detail. I watched a genuinely caring organisation spend more time on paperwork than on the people they were there to support.

So I started building.

What I built and why

ContentAutoPilot started as a single tool: give a support worker a simple input field, let them type a few rough sentences about what happened during a shift, and generate a compliant, professional progress note in under 60 seconds.

That was the core. Everything else grew from there. Over the following months I added:

• 23 document types across daily notes, planning documents, coordinator tools, workforce documents, and compliance tools
• Voice-to-note in 8 languages so multilingual workers could speak their observations and get professional documentation back
• An incident report generator that structures the narrative in the way NDIS auditors expect to see it
• A support plan builder that reduces hours of coordination work to minutes
• Australian servers in Sydney for data sovereignty — because NDIS participant data should never leave Australia

The platform runs on Claude, Anthropic's AI model. Every document it generates is structured around NDIS compliance frameworks, not generic templates. The difference matters enormously when an auditor is reading your notes.

Six months in the NDIS Facebook groups

Building the product was one thing. Understanding the real pain was another.

I spent months inside NDIS Facebook groups. Not selling. Listening. Joining conversations about audit stress, documentation overload, registration confusion, and the July 2026 evidence standard changes that are keeping every provider principal up at night.

What I found surprised me.

The documentation problem is not just a time problem. It is a consistency problem. One provider told me her biggest audit risk wasn't her worst documentation — it was the inconsistency between her best and worst workers' notes. Auditors don't just check quality. They check whether your organisation's documentation reflects a coherent, repeatable standard of care.

That reframed everything for me.

I also learned that NDIS providers are deeply sceptical of generic AI. And they should be. The NDIS Commission is actively flagging self-assessment submissions that look AI-generated and identical across organisations. Generic AI creates audit risk, not protection.

ContentAutoPilot is built differently. The output is structured around your organisation's actual participants, your service model, your specific incident context. Automation for the structure. Your reality for the content.

The July 2026 deadline every provider should know about

Progress notes will need to demonstrate participant outcomes more explicitly. This is not a threat to providers who have strong documentation systems. It is an existential risk to providers who don't.

ContentAutoPilot's NDIS DocAgent already structures progress notes around participant goals and measurable outcomes — because that's what audits have always required, and what the new standards are formalising.

What's live today

ContentAutoPilot currently serves eight industry verticals:

Every vertical is built specifically for that industry's workflows, terminology, and compliance requirements. Not generic AI. Vertical AI employees.

The founder pricing window

I am offering a locked founder price of $49 USD / $59 AUD per month for the first cohort of users across all verticals. This price is locked for two years — regardless of what standard pricing becomes as the platform grows.

I'm doing this because I want users who are invested in the product, who will give me real feedback, and who will grow with the platform. Not a discounted trial that expires. A genuine founding partnership.

Why I'm writing this

I'm a solo founder. I don't have a marketing team or a VC budget. What I have is a product that solves a real problem I watched someone I care about struggle with, and a community of NDIS providers and service professionals who understand that problem intimately.

If you're an NDIS provider spending more than 20 minutes per shift on documentation — I built this for you.

If you're a support coordinator rewriting notes at 11pm because your workers' handovers don't capture what auditors need — I built this for you.

If you're preparing for a July 2026 audit review and you're not confident your documentation standard is consistent across your whole team — I built this for you.

Try it free at ndis.contentautopilot.ai

---

Franco John is the founder of ContentAutoPilot, a multi-vertical AI documentation and content platform for service businesses. He is based in Washington State, USA and builds at contentautopilot.ai