Customer 0 - how we are owning our AI journey at Scale.

Customer Zero: turning Fusion5 ’s AI flywheel

How we run our own AI transformation — an agentic ideation portal, a live agent register, an operations centre for the fleet, and the flywheel that connects them. By Shannon Moir.

We spend our days advising customers on AI. Fair question back: what do you actually do at home?

Our answer is Customer Zero. Every framework, portal and agent we take to market runs on Fusion5 first — with our data, our governance, our people, and our scars. This post is a tour of what that looks like right now: the real programs, with real screenshots.

The thing holding it together is a flywheel.

The Fusion5 AI flywheel. Six stations, two hard gates, and no finish line — Learn feeds Ideate, and the wheel keeps turning.

The point of a flywheel — as opposed to a pipeline — is that it has no end. Every turn makes the next one easier: ideas arrive better qualified, builds go faster because patterns exist, governance gets cheaper because it ’s automated, operations get smarter because everything is instrumented, and what we learn in operation becomes the seed of the next idea. Momentum compounds.

And it ’s turned from both ends. Top-down , company goals and a written standard shape what gets asked, funded and approved. Bottom-up , anyone in the organisation can walk in with a scrappy idea and be taken seriously. The flywheel is where they meet.

---

Ideate: the front door interviews you

Most idea registers are a form and a graveyard. Ours is an interview.

The Ideation Assistant is the agentic front door to our AI pipeline. You sign in with your work email — your domain becomes your organisation, so ideas stay walled to your own company — and instead of a blank form, a Claude-powered interviewer talks the idea through with you across nine dimensions : the problem and its trigger, users and personas, value and ROI, time saved, the interaction model, cost per interaction, systems of trust, data sources, and feasibility.

The front door: work email in, nine dimensions, and a promise — no blank forms.

Those dimensions are the top-down part, quietly at work. They encode exactly what the business needs to know to fund anything: the quantified benefit, the hours reclaimed, the cost per run, the trust posture. The interviewer doesn ’t just collect your answers — it drills. Vague ROI gets a follow-up question. A missing trigger gets probed. This is ideation actively steered toward company goals, without a single committee meeting.

One sentence in, and the assistant has already checked the pipeline for duplicates (with similarity scores), cleared the idea as new, and come back with two pointed questions. Note the running token cost, bottom right — cost-consciousness starts at the first message.

Two details we ’re particularly happy with. First, duplicate detection : as soon as the idea has a shape, it ’s embedded and compared against everything the organisation has already raised, so effort isn ’t doubled and similar sparks find each other. Second, dimension seven is Systems of Trust — lawful, ethical, robust, commercial. That ’s the same four-dimension language as our governance register, on purpose. Trust questions get asked at the ideation stage, not bolted on at the end.

Ideas then live socially — colleagues comment and upvote — and move through a lifecycle we call paddock to plate : Submitted →In Review →In Development →In Production.

The idea board: every idea carries its ROI estimate, lifecycle stage, votes, comments — and what it has cost in tokens to shape.

Between idea and build sits one page. Under our HumAnIse engagement model, the internal team and the business turn a qualified idea into a business plan on a page — cost understood and compared with value before anything is built, and the solution specified against supported patterns and our existing maturity. Boring, disciplined, and the reason the build stage starts fast.

Build: one loop, humans at the hub

The linear software lifecycle is over. Everything we build — pro-code agents, Copilot Studio flows, skills, embedded AI — walks the same continuous loop: Product, Development, Operations, around a human-centric hub. Humans orchestrate; agents execute the stages. Verification is automated and lives in pipelines — in our house we say manual testing is 2025 .

The Fusion5 development loop, from our AI Development Framework. The concept has pedigree — Gartner ’s human-centric AI-native SDLC and CBRE ’s compressed intent/implementation model — but the two gates are ours: nothing enters the operations arc without a register score, and once there, the operations centre owns it.

Notice the two badges under the wheel. They ’re the hard gates in the flywheel, and they ’re where governance stops being a document and becomes software.

Govern: a register that scores, not a spreadsheet that rots

Every AI asset we run — built, low-code, direct frontier-model use, or AI embedded in a vendor product — is registered in our Trustworthy AI Register and assessed by AI against a written standard: the Fusion5 Trustworthy AI Archetype. Four dimensions — lawful, ethical, robust, commercial — each scored 0 –5, with 225 requirements behind them. Score 3 in all four is the production line. One dimension below 3 blocks sign-off, no matter how good the engineering is.

The register: every agent with its owner, its four trust scores, its engineering-security scores, its gap count — and what its assessments have cost.

The register isn ’t a compliance tax; it ’s designed as a carrot. Registration takes minutes — a Claude Code skill scans a codebase forensically and submits the evidence — and every level of governance you accept unlocks capability you can ’t get any other way. We even maintain a non-production archetype : a deliberately reduced standard of twenty requirements, so a day-one experiment scores meaningfully instead of failing a production bar it isn ’t aiming at yet. Register early, fail nothing, promote when ready.

Governance you can read at a glance: live portfolio maturity per dimension, pulled from the register, against the green production line.

Operate: an operations centre for a workforce of agents

Development ends where operations begin. The end state of every AI asset — whatever kind — is good citizenship in our Agent Operations Centre : five pillars (safety &trust, reliability, cost, compliance, continuous improvement), seventy-plus observable signals per agent, and a four-tier exception model that runs from self-healing retries up to human escalation. Kill switches are honoured, always. Costs are attributed per call. Drift is watched after deployment, because AI that was accurate at release doesn ’t stay accurate for free.

The AOC: not a compliance checker — the always-on function that observes, acts and improves the fleet.

And here ’s the closing of the loop: everything the fleet does in operation — usage patterns, human overrides, quality signals, cost curves — is treated as a first-class feed , not a log to archive. That reinforcement-learning exhaust drives improvement, retraining, triage and retirement. What we learn operating agents becomes the raw material for the next round of ideas. Learn feeds Ideate. The wheel turns.

---

Coming together: top-down meets bottom-up

None of these pieces is the story on its own. The story is that they now connect — one hub, one register, one operations centre, one loop.

One front door to the platform: the AI Development Framework, the Trustworthy AI Register, the Intelligence Layer architecture, research intelligence, and the AOC.

The energy in our business is real and bottom-up: when we counted late last year, close to two hundred of our people had built or attempted to build an agent — roughly four hundred agents. Most of those are experiments, and that is exactly as it should be. The failure mode isn ’t the sprawl; it ’s sprawl without a flywheel — ideas nobody qualifies, agents nobody registers, pilots nobody operates, lessons nobody keeps.

So the top-down half of the machine doesn ’t say no ; it says through here . Goals shape the ideation interview. The plan-on-a-page decides what gets built. The register gates what reaches production. The AOC owns what runs. And every one of those checkpoints was designed to be faster than going around it — governance as the path of least resistance, not the toll booth.

Why this matters to our customers: when we bring a customer an ideation portal, an agent register, or an operations centre for their AI fleet, it isn ’t a slideware framework — it ’s the machinery we run our own company on, standards and scars included. That ’s what Customer Zero buys: everything we sell has already survived us.

The flywheel isn ’t finished — flywheels never are. The measures will get harder (we ’re aligning to outcome metrics, not activity), the archetype keeps versioning quarterly, and the operations centre grows signals as the fleet grows. But it ’s turning, it ’s speeding up, and every turn makes the next idea cheaper to try and safer to run.

If you ’re wrestling with the same problem — a business full of AI energy and no machine to turn it into value — we ’d genuinely love to compare notes. We ’ve got the scars, and we ’re happy to show them.

Shannon Moir leads AI platforms and observability at Fusion5. Screenshots are from Fusion5 ’s internal platforms, shown with sample data. The frameworks referenced align to external standards including the NIST AI RMF, ISO/IEC 42001, Australia ’s Voluntary AI Safety Standard, and Gartner ’s AI-native SDLC research.