NDIS provider
Claim submission & resubmission pipeline
End-to-end: claim built from session data, validated against the participant's plan budget, submitted to the portal, rejection reasons parsed an
Services
One offer. One price. The scope changes with your operation — the number doesn't.
We don't sell tiers, packages, or per-seat plans. Every engagement is A$8,000 to ship the system, A$500/month to keep it running.
Engagement
A$8,000 setup + A$500 / month
What the setup includes
✓ Two-week mapping phase — we watch your team work, document what's actually painful
✓ Three iterations of the system shipped (v1 → v2 → v3) over ~6 weeks
✓ PII isolation architecture — LLM never touches identifying data
✓ Compliance review against the relevant Australian standard
✓ Source code in your account — you can fire us and keep using it
✓ Handover documentation written for your team, not us
What the A$500/month includes
✓ System runs on our infrastructure (or yours, if you prefer)
✓ Fixes when something breaks (most months it doesn't)
✓ Minor changes as your workflow evolves
✓ Cancel anytime. No lock-in. No exit fee.
How we ship for high-compliance industries
PII isolation built into the architecture, not bolted on.
The LLM never sees participant or patient names. Identifying data lives in a separate store; the model only sees structured placeholders. A local merge layer puts the names back at the end, before the final output reaches a human.
The red dashed line is the data path PII takes. It bypasses the LLM entirely. This is the engineering pattern we ship for NDIS, allied health, and aged care work — and it's the part that makes the rest of the system defensible in an audit.
Scope examples