ProviderQMS

Care operations

Foxtrot for NDIS vs MYP

Compare the published scope, cost evidence and buying questions before you commit.

Sources checked 2026-09-24 · Source-based comparison

Vendor-source research, not hands-on tests or a ranked endorsement. ProviderQMS sells document kits and a separate QMS product. No vendor enquiry collection or affiliate source links. How we compare.

The decision to make

Foxtrot for NDIS and MYP both appear in our care operations research. Connect the participant record, support delivery, worker activity and financial evidence. Start with the differences below, then test the same essential workflow. We have not used these products hands-on or established an overall winner.

Foxtrot for NDIS vs MYP: the published starting point
Buying questionFoxtrot for NDISMYP
What does it do?Stepsoft's Foxtrot for NDIS manages participant, plan and support records. Published packages add billing, claim export and, at larger tiers, scheduling and timesheets.MYP offers an NDIS service-provider platform for participant records, funding and daily delivery. Its separate support-coordination solution tracks billable time, budgets and goals.
Why consider it here?Stepsoft separately markets this Foxtrot configuration to Australian NDIS providers.Vendor explicitly positions its software for Australian NDIS providers and coordinators.
What is the cost basis?Published Micro A$149/month for one user, Small A$349/month for 2–5 users and Medium A$799/month for 6–20 users; GST and terms need confirmation.Current price not verified; request a written quote.
What should the demo show?Record a plan-managed participant's support note and service item, export the claim file and trace payment against the budget.Add a participant goal and budget, deliver a shift with worker check-in, then show the coordinator time and claim record.

Compare the evidence, product by product

Foxtrot for NDIS — published capabilities

  • Participant and plan records
  • Service or file notes with NDIS item numbers
  • Claim-data export for portal upload
  • Plan budgets and invoice records

Source check: 2026-09-24. Published vendor statements, not independent feature testing.

Questions for Foxtrot for NDIS

  • Which tier includes the staff roster and timesheets?
  • Does portal export require manual checking or re-entry?
  • How do custom fields and participant attachments export?
Read the full Foxtrot for NDIS profile ↗

MYP — published capabilities

  • Participant records, documents and permissions
  • Rostering and mobile worker check-in
  • Progress notes linked to goals
  • NDIA integration for service bookings and claims

Source check: 2026-09-24. Published vendor statements, not independent feature testing.

Questions for MYP

  • Which modules are included for support coordination?
  • How are participant portal permissions and invoice approvals configured?
  • What exactly is exchanged with PRODA or PACE?
Read the full MYP profile ↗

Run the same scenario in both

Use a fictional recurring community-access service. Change the worker, record the delivered support, correct a note and reconcile the invoice.

  • Trace service agreement and budget to the roster and delivered record.
  • Check what the worker can see, what they must record and how corrections are retained.
  • Change or cancel a service and inspect the effect on timesheets, billing and reporting.
  • Export the participant history with attachments and demonstrate the exit process.

Put the quotes on the same basis

Model active clients, staff logins, sites, service lines, setup and required accounting/payroll connections.

Use the same volumes, currency, GST basis and billing period for both quotes. Include migration, staff training time, required companion subscriptions and the cost of retrieving records at exit. If a charge is unverified, keep it as an open question rather than treating it as free.

How to reach a decision

  1. Choose the tasks your service cannot operate without before either demonstration.
  2. Record demonstrated, partial, not demonstrated or not applicable for each task. Keep the evidence and edition name.
  3. Ask the vendor to resolve every failed essential task in writing; a high average score cannot erase it.
  4. Test a correction, permission change and export. These are part of everyday operations, not just implementation.
  5. Decide using workflow fit, full cost and your team’s capacity to change systems. Retain the written assumptions for review.

What this comparison does not establish

Service-delivery software varies by provider size, module and funding workflow. Scheduling alone does not establish complete NDIS claiming or clinical-record coverage. A capability not mentioned in the reviewed source remains unverified, not absent. This comparison does not certify compliance, integrations, accessibility, security or migration outcomes.