Notara — an AI-assisted NDIS documentation platform, designed and built solo.

The challenge

NDIS support workers spend one to two hours a day writing mandatory documentation by hand — shift notes, incident reports, and progress notes. Experienced workers have a speed problem: the writing takes too long. New sole traders have a knowledge problem: they don't know what a well-structured document is even supposed to look like. Both groups needed the same thing — a faster way to get from "what happened" to a usable first draft.

What we built

Notara is an AI-assisted NDIS documentation platform. A support worker describes their shift in plain English, and the platform generates a structured document draft — a shift note, incident report, or progress note — in under 3 minutes. Every draft is built around NDIS documentation standards and is explicitly framed as a draft: the support worker reviews, edits, and approves it before it's used.

• Full authentication and multi-organisation account system, with role-based access (owner, admin, member)
• AI-generated document drafts for three document types, plus a secondary AI review pass that flags content for human review
• Stripe-powered subscription billing with monthly and annual plans, a self-serve billing portal, and webhook-driven plan sync
• Participant profiles, file storage, and full document history
• Admin dashboard for reviewing flagged documents and exporting audit records as CSV or PDF
• A separate participant-facing portal, on its own subdomain — support workers share individual documents with a participant or family member in one click, with sharing always explicit and opt-in
• Email notifications via a transactional email provider — invitations, shift reminders, and weekly digests

The technical foundation

This is where a lot of software in regulated-adjacent domains cuts corners. We didn't.

The application is split into two distinct layers, not one login screen with hidden permissions: a provider-facing dashboard for support workers and admins, and a separate participant-facing portal for the people receiving support — each on its own subdomain, each with its own access boundary. Row-level security on every database table means a support worker only ever sees their own records, an admin only sees their own organisation, and a participant only ever sees what's been explicitly shared with them. Encrypted data in transit and at rest. A subscription and billing system that stays correctly in sync with Stripe through webhooks, not manual reconciliation.

The outcome

A real, working product — not a prototype. It handles real authentication, real billing, and a genuinely useful AI integration, in a domain where the documentation actually matters. It's live today at app.notara.com.au, and it's the clearest proof we have of how we build: end to end, and built to actually run.