Enterprise DNA

Instead of Vertex360

Outgrowing your Vertex360 participant band? Own your NDIS provider system instead.

We build your version around your registration groups, your intake and the way your coordinators roster, bring your Vertex360 participants, staff and shifts across, and run it for you. No band to climb and no contract term to sit out.

Vertex360 lists Total Suite at $35 a month for 1 to 5 participants and $600 a month for 51 to 100, plus GST, with a one-off onboarding fee that also rises with the band.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

How Vertex360 adds up

A price set by how many participants you support, then terms on top

Vertex360 does not charge per staff member, and support worker accounts are free. The price follows your caseload instead: pick a participant band, pay that band's monthly fee, and pay a one-off fee to get in, plus a fee if you leave a term early.

stairs

A higher band as you take on participants

Total Suite is $35 a month for 1 to 5 participants, $360 a month for 21 to 50 and $600 a month for 51 to 100, plus GST. At 51 to 100 that is $7,200 a year for the same records you kept at five.

event_busy

The discount comes with a 12-month term

Paying annually takes 25% off, so 1 to 5 participants drops to $26.25 a month. In return you agree to a 12-month minimum, and leaving early can cost half of what is left on the contract.

gavel

Advice bundled into the top plan

Platinum starts at $100 a month for 1 to 5 participants and adds lawyer advice, a standard employment contract and an internal audit report. It also carries a one year minimum with exit fees.

login

An entry fee that also scales

Onboarding is a one-off charge set by your band: $199 at 1 to 5 participants, $999 at 51 to 100. A larger provider pays more just to start.

description

Your history moved in by the file

Data migration is $3 per file for staff and participants. If migration was given free, the terms make it payable when you leave early.

trending_up

A price that can rise at review

The terms allow pricing to be reviewed each year in line with CPI, fees paid are non-refundable, and your records stay on Vertex360's platform while you pay.

What you run instead

One provider record, no matter how big the caseload gets

Shifts

Bookings that check themselves

Every shift is tested against the participant's agreement and the worker's clearance before it is saved.

  • check A worker whose NDIS Worker Screening clearance has lapsed on the day cannot be booked
  • check A shift needs a signed service agreement that is in date
  • check The same worker cannot be in two places in the same hour
  • check Late cancellations keep their notice period, so whether they can be claimed is worked out for you

Claims

From finished shift to payment request without a gap

Coordinators see the work that has been delivered but not yet billed, every morning.

  • check Completed shifts with a note and no payment request, listed oldest first
  • check Claims priced at the agreement's rate, so a line above the price limit is never created
  • check The bulk payment request file prepared for someone to upload
  • check Rejected lines kept in view with the reason until they go back in

Evidence

An audit trail that builds itself

The rules sit in plain writing with their sources, and the strictest ones stop a record being saved.

  • check No progress note, no completed shift
  • check A reportable incident stays open until the Commission notification is logged
  • check A single check lists every breach and the rule it breaks
  • check Records are never deleted: participants exit, staff become former, claims stay for the 7 years required

Growth

Participant number 6, 21 or 101 costs the system nothing

There is no band to move up and no term to wait out when your caseload grows.

  • check No charge per participant or per staff member
  • check Spending tracked against pace for each agreement, so a plan running under shows early
  • check New fields, support items or rules added by describing them
  • check MIT licensed and open source, so there is no contract to exit

Make it yours

Design your own Vertex360 replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Vertex360. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Vertex360 replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Vertex360 data across and run it for you.

Switching

How to switch from Vertex360

A move involves getting your participant, staff and shift records out, mapping them to the new system, checking the import and running both systems side by side before you switch.

  1. 1

    Ask for your records

    We could not find public instructions for exporting from Vertex360. Ask Vertex360 or check the reports available in your account for participant, staff and shift lists, including the history you want to keep. Export what your account allows, usually CSV or Excel, and confirm the available formats with Vertex360. Check your contract and any renewal date before planning when to turn off your current system.

  2. 2

    Map and load the records

    The exported records will not match the new system’s import layout. Map your participant, staff and shift details to the fields the import expects, and decide which history to bring across. Run the import’s test run first, if offered, then load the records. Enterprise DNA handles the mapping and test run when you have them build and run your version.

  3. 3

    Review the import findings

    Read what the import flags before you rely on the new records. Check for missing details and issues such as a shift without a covering agreement or a participant whose funding type was not recorded. Compare the imported records with Vertex360, correct what you can, and decide how to handle anything that cannot be mapped or confirmed.

  4. 4

    Run both systems together

    Keep Vertex360 running while you use the new system for a short period. Compare the records and day-to-day work in both so you can catch missing information or rules that need adjustment before the switch. Keep staff clear on which system is the current record during this overlap, and do not treat the move as complete until the checks you need are done.

  5. 5

    Switch off Vertex360

    Once you have checked the imported records and are ready to work from the new system, plan the change around your contract and renewal date. Vertex360’s terms may include an early termination fee, so check them before ending the service. Keep the records you need access to, then end Vertex360 according to your agreement.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules to the new system, then deciding how much history to bring across and checking that it imported as intended. Vertex360 exports may not match the import layout, and some details may need review. When Enterprise DNA runs the build, they handle the mapping and test run with you.

Not ready for a call?

Get your Vertex360 switch plan by email

We will send you the step-by-step plan for moving your business off Vertex360, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Two ways to switch

Take the free version, or let us build and run yours

Open source

Run it yourself

Free

  1. 1 Clone the repo from GitHub and run npm run demo
  2. 2 Open the folder in Claude Code and type /attention
  3. 3 Ask Vertex360 or download from its reports whatever participant, staff and shift lists your account allows
  4. 4 Ask Claude Code to map those columns to the import, then load your records
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA build and run it

One setup fee, then a monthly retainer

  • check We get your Vertex360 records out, map them across and check the counts before you switch
  • check We set it up for your registration groups, support items, cancellation windows and intake steps
  • check We add a worker phone app or simple screens if your team needs them
  • check It runs inside Omni, our managed Command Centre, beside the rest of your business
Book a discovery call

Questions

Instead of Vertex360, answered

Vertex360 is cheap for a small provider. Why would we change? expand_more

At 1 to 5 participants it is, and if you plan to stay that size it may well be the right choice. The question is what happens as you grow: the monthly fee moves with your participant band, onboarding moves with it, and the annual discount ties you to a 12-month term. Your own version has no participant band to climb.

We are on an annual Vertex360 plan. Can we leave early? expand_more

Check your contract first. Vertex360's terms set a 12-month minimum on annual and promotional plans and describe an early termination fee that can be half the remaining contract value. One option is to build your own version while the term runs out, then switch on the renewal date.

How do our Vertex360 records come across? expand_more

We could not find public documentation on exporting from Vertex360, so the first step is asking them, or your account's reports, for participant, staff and shift lists. Those files will not match the free version's import layout. Mapping them and doing a test run is part of what we do when we build your version.

Platinum gives us lawyers and an internal audit. What replaces that? expand_more

Nothing here is legal advice, and we do not pretend otherwise. What you get is a record that holds the NDIS rules as it is written: screening before rostering, notes before claiming, incident notification before closure, each rule with its source. Keep your own lawyer and auditor; they will find the records easier to check.

Our workers use the Vertex360 app on shift. What do they use instead? expand_more

The free version has no worker phone app today. When Enterprise DNA builds your version, a worker app or simple screens for shift times and progress notes can be part of it, built to how your team already works.

See what your provider system looks like when you own it

30 minutes with Sam. Bring your Vertex360 plan, your participant count and your contract end date. We look at which band you are in, where you are heading, what your coordinators actually use, and what your own version would hold. If it fits, we build it and bring your records across. If not, the free version is yours to run.

Home Care for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Vertex360?

Get your version built