46 governed models. One architecture.

Thirty-two operational control models across five pillars, plus fourteen project finance and valuation models. Every one is built on the same four layers, the same nine-tab workbook spine, the same cell-state standard and the same QA gate.

Four layers, strictly separated.

The separation is the product. Inputs never touch logic, logic never touches presentation, and every layer is documented in the same place.

Layer 1

Input

The only editable surface. Validated entry with units declared and dropdowns driven from governed lists. No end user ever sees a formula.

Layer 2

Calculation

Protected, tested logic, isolated from inputs and outputs, with an audit column that explains each step in plain words, not cell references.

Layer 3

Control Room

The view your leaders run the week from: KPI band, ranked losses, the binding constraint, and an issue register with an owner on every line.

Layer 4

Governance

Data dictionary, version control, reconciliation checks and a signed testing checklist: the release gate that has to pass before anything is handed over.

The four layers sit on the nine-tab workbook spine published in our standard.

The catalogue.

Every model is AU$500 ex GST and ships on the nine-tab workbook spine with a data dictionary and a QA sheet. There is no “lite” version of the governance. Buy online for an instant download, or ask us about any model first.

Showing all 46 models.

Start with one model, or commission the room.

“Can I just buy one model and try it?”

Yes. One model, self-installed, yours to keep. It is a full governed model with its own dictionary and QA sheet, not a teaser with the logic stripped out. It is also the first rung of the same architecture that runs a full Control Room, so nothing gets rebuilt when you climb.

Most people who start here do it to settle one argument. That is a good reason.

“We want the whole room installed.”

Target: 14 days from data access to go-live. Data mapping, build, test, train, hand over. You get the Control Room, the models under it, the governance pack, the operating cadence and 14 days of hypercare while your team runs it for the first time.

We target your lowest-scoring, highest-dollar control gap first, so the system starts paying before it is finished.

The install. Target: 14 days from data access.

Fixed scope, fixed price, published so you can hold us to it. Each phase has a named exit condition, and we don’t move on until it is met. The 14 days start when we have your exports, not when you sign.

  1. 01
    Days 1–2

    Data mapping

    We take your existing exports as they are, map them against the minimum viable dataset, and agree the KPI definitions in writing. Exit: a signed data dictionary and one agreed definition per metric.

  2. 02
    Days 3–7

    Build

    Input, calculation and Control Room layers built on your real data, with the Power Query refresh pipeline wired to your export format. Exit: the model reconciles to your source system.

  3. 03
    Days 8–10

    Test

    The QA sheet runs: reconciliation checks, threshold tests, edge cases and a full recalculation. Exit: every check passes and is signed, or the finding is logged and fixed.

  4. 04
    Days 11–13

    Train

    Two sessions: one for the people entering data, one for the people running the meeting. We train the cadence, not just the file. Exit: your team runs the review while we watch.

  5. 05
    Day 14

    Go-live

    Handover of the workbook, the governance pack, the changelog and the operating rhythm. Exit: the first live week is run on the system.

  6. 06
    Days 15–28

    Hypercare

    Fourteen days of direct support while the cadence beds in, which is when most of the real questions surface. Exit: two consecutive weeks run without us in the room.

The 14-day target assumes exports are available on day one and the people named in the data dictionary are reachable. It is a target, confirmed in your written proposal, not a guarantee.