The Everything vs TechnologyOne
Your ERP runs the system of record. Something still has to run the work between the systems. That is a different purchase.
The short answer
TechnologyOne is an Australian enterprise SaaS company whose ERP is widely used across local government, higher education and the public sector. It is the system of record for the transactional core — finance, rates and revenue, assets, HR and payroll, and the council business it wraps. The Everything is not an ERP and does not compete with one. It is an AI automation layer over Microsoft 365 that runs the process work an ERP never reaches: the email chasing, the approvals sitting in inboxes, the status questions, the handoffs between the ERP and everything else. If you are replacing your core system, that is an ERP decision. If your problem is the weeks of human coordination around it, that is The Everything, live in days.
Their strengths
What is TechnologyOne genuinely good at?
TechnologyOne is an Australian enterprise software company that delivers its ERP as SaaS, and it is deeply established in local government, higher education and the wider public sector. Its strength is being the transactional system of record: finance, revenue, assets, procurement, HR and payroll held in one integrated model, delivered as a managed service rather than something the council has to run itself. For an organisation that needs a single defensible source of truth for money and assets, that is exactly the right shape of product.
A single integrated system of record
Finance, assets, revenue and people in one model rather than five systems reconciled by spreadsheet. That integration is the reason organisations buy an ERP at all.
Delivered as SaaS
The vendor runs the platform and the upgrades. For a council without a large internal platform team, not owning the infrastructure is a genuine advantage.
Built for the Australian public sector
Local government and higher education are core markets, so the domain model, the terminology and the procurement path are native rather than adapted from overseas.
If you need a system of record for the transactional core of the organisation, an ERP is the right category and TechnologyOne is a serious Australian option in it.
The trade-offs
Where does the ERP approach get hard in practice?
This is not about product quality. It is what the ERP category costs, everywhere, with every vendor. An ERP is an implementation programme: data migration, chart of accounts, org structure, security roles, business process alignment and change management. The software is the smaller half. And when it is finished you have a superb system of record that still does not run the human coordination happening around it.
The implementation is the product
Configuration, migration and process alignment are agency work supported by an implementation partner. That programme has a budget, a timeline and a change-management burden regardless of which ERP you choose.
Processes get shaped to fit the system
Integrated systems of record work by standardising. Anything that does not fit the standard model either gets a customisation request or falls back to email and spreadsheets outside the system.
The work between systems is nobody home
A development application waiting on a referral, a supplier who has not returned a document, an approval sitting in a manager inbox — that is where the elapsed time lives, and it is not a transaction the ERP is tracking.
Change requests queue
Because the ERP is core, changes to it are governed and scheduled. Small process improvements end up waiting behind large releases, which is why staff route around them.
The practical test: take a process that currently takes three weeks and ask how much of that time is spent inside the ERP. In most councils the answer is minutes. The rest is coordination.
Our approach
What does The Everything do instead?
The Everything runs the coordination. It is an AI automation layer on top of Microsoft 365 that executes a real process end to end — reading what arrives, preparing the work, stopping for the human decisions that matter, chasing what has not come back, and logging all of it. It sits above your systems rather than replacing any of them, which is why it does not require a migration or a data model.
Process definitions
The steps, owners, conditions and exceptions of a real council or agency process, written once and then executed — including the parts that live between systems.
Approval and authorization engine
Anything consequential stops and asks a named officer in Teams with the context to decide. Approve or reject and the process resumes from where it paused.
Audit logging
Every action, input, decision and approval recorded as it happens, so accountability for the coordination is as clear as accountability for the transaction.
RBAC and permissions
Enforced per person and per action from existing Microsoft 365 identity, so the access model is the one you already administer.
Governed-asset stewardship
Approved templates, standing references and required wording the AI must use, so correspondence and outputs are consistent across officers.
Microsoft 365 native
It works in Outlook, Teams and SharePoint over the content already there. No migration, no new system for staff to adopt, no competing programme.
A first workflow goes live in days, and it goes live beside the ERP rather than instead of it. That is the point: the improvement does not have to wait for a core system programme to finish.
Our limits
What does The Everything explicitly not do?
The Everything is not an ERP and does not touch your transactional core. It is not a finance system, not a rates or revenue system, not a payroll system, not an asset register and not a general ledger. It does not post journals, calculate rates, run a pay cycle or hold the numbers you report against. If you need a system of record for money, people or assets, buy an ERP — The Everything automates the process work an ERP was never built to reach.
It does not replace your systems of record
The ERP, the document store and the line-of-business systems all stay where they are. The Everything runs the work between them rather than absorbing any of them.
It is not a statutory records system
No retention schedules, no disposal authorities, no legislated recordkeeping. Our audit log records what happened in a process; it is not a record register.
It does not take the decision off a human
Consequential actions require a named approver by design. Automating a council decision away from an accountable officer is not something we offer.
Keep the ERP for the transaction. Use The Everything for the three weeks of email, chasing and waiting that happen around it — because that is where the elapsed time actually is.
Which should you pick?
| If your problem is | Pick | Why |
|---|---|---|
| You need one system of record for finance, rates, assets and payroll | An ERP | That is the category. TechnologyOne is a credible Australian public sector option. |
| You are consolidating fragmented core systems | An ERP | Integration of the transactional core is what an ERP is for. The Everything is not. |
| Approvals and referrals sit in inboxes for weeks | The Everything | The approval engine routes to a named officer in Teams and chases what has not returned. |
| Most of your cycle time is between systems, not inside one | The Everything | It runs the coordination layer that no system of record is tracking. |
| Small process improvements are queued behind core system releases | The Everything | It sits above your systems, so a change does not need a core release window. |
| You need something live this quarter, not next financial year | The Everything | A first workflow goes live in days and does not depend on the ERP programme. |
| You have an ERP and the work around it still runs on email | Both | Different jobs. The ERP holds the transaction, the automation layer runs the work. |
Common questions
Is The Everything an alternative to TechnologyOne?
No. TechnologyOne is an ERP — the transactional system of record for finance, revenue, assets and people. The Everything is an AI automation layer that runs the process work around systems of record. They are not substitutes, and any vendor telling a council an automation layer replaces its ERP is not being straight with you.
Does The Everything touch finance, rates or payroll?
No. It does not post journals, calculate rates, run a pay cycle or hold a general ledger. It automates the coordination around those systems: the intake, the preparation, the approvals, the chasing and the decision trail.
Can The Everything work with an ERP that is already in place?
Yes. It sits above your systems rather than replacing them and requires no migration, so it runs alongside an existing ERP, document store and line-of-business systems, working over the Microsoft 365 estate staff already use.
We are mid-way through an ERP programme. Should we wait before looking at automation?
No, they are independent. The Everything does not depend on the ERP configuration and does not compete for the same release window. A first workflow can go live in days while the core programme continues.
What kind of council work does The Everything actually automate?
The work that lives between systems and people: intake of requests and correspondence, preparing what is needed for a decision, routing approvals to named officers in Teams, following up what has not come back, and recording every action and decision to an audit log.
Work out which one you need
Bring us the workflow that is actually costing you time. We will tell you whether it is an automation problem or a document platform problem — including when the answer is that you do not need us.
Last reviewed 2026-07-21. We describe TechnologyOne at the level its vendor publicly documents and do not assert specifics we cannot verify. If anything here is out of date, tell us and we will correct it.