The board
Every build we have shipped, and whether it is still running.
Perth businesses have tried AI. Almost none of it is still running. That is the part we do, so this is the page where we have to prove it. One row per build. What it does, the month it went live, and whether it is in production today. Anything that stopped stays on the board with the reason it stopped.
Nothing here is a case study. There is no pull quote, no percentage, and no logo wall. A date and a yes or no are harder to write and harder to fake.
Core Nova builds, internal
We run the playbook on ourselves first.
These are builds inside Core Nova. They are on the board for the same reason client builds are: if we will not publish a live date for our own work, we have no business asking anyone to trust ours.
Two rows below are dated but not yet live. They stay on the board in the off position with the month they are due, because a board that only shows finished work tells you nothing about what happens to the work that is not finished.
| Build | What it does | Sector | Live since | Status | Running for |
|---|---|---|---|---|---|
| Daily LinkedIn newsroom | Reads fourteen feeds each weekday at 9am AWST, scores each item against positioning, and drafts three posts in the operator's voice to a human reviewer. Nothing publishes itself. | Core Nova, internal | Still running | ||
| Branded-PDF skill | The model writes markdown, which it is good at. Pandoc and the Core Nova stylesheet render the branded PDF, which code is good at. Six other workflows call it rather than reinventing typesetting. | Core Nova, internal | Still running | ||
| Inbox triage and day plan | Classifies overnight mail into needs you, can wait, and drafted reply ready by 6:30am, then compares the calendar against standing priorities and lands the shape of the day at 7:00am. Drafts stage in the Drafts folder. The operator sends. | Core Nova, internal | Not yet live | ||
| One-prompt proposal pipeline | Looks up the client and the matching service spec, applies pricing and GST rules in code, drafts the narrative, and renders the branded proposal PDF. One prompt end to end. The operator stays the editor. | Core Nova, internal | Not yet live |
Internal builds are here to show how we work, not as benchmarks for a client engagement. Client scope, data boundaries and governance are named in the SOW. Detail on each build is on the work.
Client builds
No client rows on the board yet.
We could fill this section today with unattributed claims. We are not going to. A client build goes on the board when two things are true: it has been in production long enough for a duration to mean something, and the client has given written consent for the row.
A client who does not want to be named still gets a row. Sector, live month, duration and status are published. The name is withheld. Everything on the row that can be checked stays checkable.
If you want to see a row that is not on this page yet, ask on a call. We will tell you what is running, for whom we can say, and how long it has been going.
What a client row will look like
| Build | Quote-to-invoice reconciliation |
| Sector | Metal fabrication, WA |
| Live since | Month Year |
| Status | Still running |
| Running for | n months |
Illustration of the row format. Not a real engagement. Nothing on this page is a real row until it is in the board above.
The rules
What keeps this board worth reading.
The moment a board like this becomes marketing it is worthless. These are the rules that stop that happening, published so you can hold us to them.
- Live means in production and operated by the people who own it. A pilot is not live. A demo is not live. A build somebody has to be reminded to use is not live.
- The duration is computed, never typed. Every row carries the go-live month in the page source. The months-running figure is calculated from it when the page loads, so it cannot quietly go stale.
- A build that stopped stays on the board. It keeps its live month, gains the month it stopped, and carries the reason. Deleting a failure is how a proof board turns into a brochure.
- No client is named without written consent. Unnamed rows still publish sector, live month, status and duration.
- The board changes when the work changes. It is not updated to a marketing calendar and it is not held back for a campaign.
- Nothing goes on the board without a confirmed month. If we cannot say when it went live, it is not evidence.
Why this page exists
Adoption was never the problem.
Australia has one of the highest AI adoption rates in the world alongside more than a decade of weak productivity, with hours worked rising faster than output. Businesses here are not short of AI. They are short of anything that reached handover and kept going after the person who built it moved on.
Every vendor can show you a demo. A demo proves a thing worked once, in a room, with its author standing next to it. The only claim worth making is the one with a date on the front of it and a duration behind it, which is why the whole of Core Nova's proof is a table with a month in it.
Adoption and productivity figures: Morgan Stanley, Future of Work Downunder, via Business News, 11 August 2026.
Find one workflow worth automating. Ship it in four days.
The First Workflow engagement is fixed price, four working days, A$6,000 + GST. We map your processes, name the workflow with the largest unrecovered hours, and ship the first improvement before the second week ends. If it works, it goes on this board with a date on it.