Your team keeps everything running.
We give it the room to build.
A member association pays for an IT team it cannot use for anything new. Every hour goes to keeping the incumbent systems alive — the CRM, the member database, the renewals that must not break. The board’s requests are declined not because they are hard, but because there is no room in the week.
There is no new budget line for this. The money is already leaving the building every month as payroll.
The consequence is not downtime. It is paralysis with a full payroll attached.
The team is competent. The team is willing. The team has no hours. Prototyping, improving, or building the thing the board keeps asking for is permanently deferred, because there is no capacity left after run-and-maintain.
The organisation is paying market rates for six people and receiving, in exchange, the maintenance of what already exists. Nothing new. Ever.
“Six people, and no capacity to create.”
New Horizons, Ryde — first-hand, not a statistic
Four pains live in this space
Capacity
“I need more hands.”
Slowly. A budget argument.
Departure
“We lost everything when he went.”
Later. Retrospective.
Dependency
“I’m held to ransom.”
Now. A power problem.
Bandwidth
“They keep the lights on and nothing else.”
Now — and the team agrees with you.
The proposal is not “spend more.” It is “get what you are already buying.” That is a very different conversation with a board.
This is not a hypothesis. We have worked inside one.
53 → 12
Choice Australia — Enterprise Architect
A national association whose systems estate we mapped and cut by three-quarters. That is not an anecdote about IT being frustrating. It is a credential.
When your IT team asks whether we understand what they live with, the answer is that we have done it — at an organisation larger than theirs. In a room where the technical people decide whether you are a threat, that sentence is the difference between a vendor and a peer.
22 years
inside an association and its systems
4 NFPs
have already asked for this, unprompted
Built one
our founder runs his own professional body
Centurion is the IT team’s colleague.
Never its replacement.
An AI arriving at an organisation with an IT team normally reads as a threat. That is how internal tools die — a function that feels replaced becomes a blocker, and it does not need to say no out loud. It only needs to be busy.
Where that team is trapped in run-and-maintain, the same product reads as release. They have a backlog they want to build and no hours to build it. They have a board asking why nothing new ships. They have skills going stale for lack of use. And here is a thing that makes them look better, not smaller.
The team becomes the internal champion, not the blocker.
Not a system to run. Capacity to use.
We direct your Centurion to build the prototype your team has been deferring. A real, working thing — scoped, built, delivered. Not a demonstration, and not a roadmap.
01
We build it
Your Centurion builds the prototype the team has been deferring — scoped, built and delivered with a defined end date.
02
We train your team
How it works, how to change it, how to build the next one without us. Your people, on your systems.
03
You keep it
The Centurion stays. The team that ran the build stays. The capability stays in the building.
A project, not a promise
A defined deliverable is far easier for a board to approve than a subscription to a capability nobody can picture yet.
The handover is the proof
You cannot hand a tool to a team, train them on it, and leave them believing they were the target.
The knowledge stays
Why is it like this? For once, the answer exists — held by the thing that built it, not the person who left.
“How does this sit with the EU AI Act?”
We will never tell you we are “AI Act certified.” There is no certification, no approval mark and no notified body for this class of product. A vendor who claims one has not read the Act.
This is a minimal-risk use
Member services, enquiries, internal drafting and knowledge management are not in Annex III. The high-risk list is exhaustive, and this is not on it.
We support your Article 4 duty
AI literacy for staff using the system — an obligation of effort, not outcome. We ship the training and safe-use guidance. The duty remains yours.
Built for human review
Which is what Article 50 transparency wants for anything published. Internal, human-reviewed documents sit outside it entirely.
Clear of the prohibitions
No staff monitoring, no member scoring, no emotion inference in the workplace. Keep HR use out of the deployment, and we will say so.
Every word of that is checkable — which is why it is a better answer than a badge. A badge invites scrutiny and fails it. A use-case-specific answer survives it.
One real proof, honestly counted.
The external evidence in this market is thinner than it first appears, and you will find that out in the first five minutes — so we will say it first. Counting seats as separate proofs would overstate the case, and a board member finds the hole immediately.
The honest position: one proven external company, plus a product your own IT team can evaluate directly. In this segment that is survivable, because the team can test it themselves within days. One real proof, honestly counted, beats three overstated ones that collapse under a single question.
Give your team the capacity it has been missing.
The backlog your IT team has been carrying for two years — started. You already pay for six people. Get six people’s worth of building out of them.
Complete discretion. By invitation and referral.