Bridge △ · The Scaffolded Crossing
How do you cross — with confidence?
The third gate is where transformation either stalls or launches. Most businesses can see the destination. Very few can see a path they trust enough to step onto. The guide's job here is not to close a sale — it is to engineer confidence.
Confidence is not faith. Faith is a leap. Confidence is the equation: anticipated outcomes ≥ expectations + cost of the journey. This gate is the Loop — the centre zone of the Tight Five, what you run to close the gap. Five fronts, run simultaneously, each with a proof signal and a named kill switch.
Five-cell anchor — five fronts to run to close the gap
NZD $54K
Stage 1 cap — cost of being wrong named before any work begins
Week 8
Kill check — if Monday number is not automated, spend stops here
Month 9
Conservative breakeven — confidence equation clears the bar
90 days
The crossing — 3 milestones, 4 GO conditions, 1 written kill switch
Reverse-Engineer from the Dream
Performance-First means starting at the outcome. Define what winning looks like — then trace backwards to what must be true one step before, and one step before that, until you reach today's first action. Planning the play before defining winning is how budgets get spent on the wrong problem.
Winning looks like
The Monday merchandising report lands in the CFO inbox at 8am, automatically, for four consecutive weeks. No manual assembly. Exceptions named. Every pricing and stock call anchored in current data, not last week's memory.
Trace back from that outcome:
Week 16 — Prediction confirmed
Four consecutive automated Monday reports have landed and survived dual-run reconciliation. The Stage 1 prediction is confirmed and the bet is paid back.
Week 8 — Kill check #1
First automated Monday must have arrived by here. If not, the kill switch fires. Stage 2 funding is unlocked only if this check passes clean.
Week 5 — First automated Monday
The pipeline runs its first full automated cycle. Dual-run validation against the manual process begins. This is the first proof the bet is real.
Day 14 — Four GO conditions confirmed
The foundation of the crossing. Without these four conditions met in writing, scope is adjusted before a dollar of build spend is committed.
Day 14 — Four GO conditions
- 1.POS API access confirmed in writing (IT lead named, Day 3)
- 2.Stage 1 budget of NZD $54,500 approved with named kill switches (CFO, Day 7)
- 3.BI substrate vendor selected from shortlist: Metabase / Hex / Power BI (CFO, Day 14)
- 4.5 Documentation Sprint owners named — supplier history, pricing logic, margin floor, catalogue selection, store-mix (Owner, Day 14)
The 30/60/90 Onboarding Contract
An AI system dropped into production without an onboarding sequence fails the same way a new buyer dropped without shadowing fails — too many decisions, too much missing context, no trust built. The 30/60/90 shape is not a schedule. It is the MKO scaffolding that makes the crossing teachable.
The new-staff parallel: a senior buyer takes 30 days to own one category with weekly review. They do not attempt the full role in Week 1. AI onboarding follows the same discipline — surface one decision instrument, prove it works, then expand.
Three live instruments
Day 30Monday number lands automatically. Catalogue saleId ROI dashboard in weekly use by Marketing + Buying. FX exposure tracker online for CFO. Two named problem areas answered with data for the first time.
New-staff parallel: New buyer: owns one category with weekly review
Second loop in production
Day 60UC1 (Unified Data) is stable production — no manual reconciliation. Buyer Brief phase begins. Catalogue ROI is the Marketing + Buying joint meeting agenda. FX tracker referenced in monthly Owner conversation.
New-staff parallel: New buyer: independent decisions on smaller categories
Quarterly review + Cwic pilot
Day 90UC3 pilot (Cwic replenishment loop) in test with 1–2 SKUs. The CFO presents the quarterly review using the same instruments — the framework has become the operating agenda, not a consultant deliverable.
New-staff parallel: New buyer: full category ownership with documented decision trail
At any point: if the agreed kill-switch trigger fires, the spend stops. This is what the CFO needs to hear — the bet is bounded, not open-ended.
The Bounded Bet + Written Kill Switch
Confidence = anticipated outcomes ≥ expectations + cost of the journey. Three levers, each doing distinct work. Read the confidence equation →
Reality raised outcomes
The honest reckoning updated what the business believes is possible. Honest diagnosis expanded the ceiling on anticipated outcomes.
Dream sharpened the target
A specific, readable destination made the anticipated outcome concrete. Specificity is the precondition for commitment.
Bridge caps the cost
A written kill switch, a NZD $54K cap, and a named walk-away cost. The cost of being wrong is known before the work begins.
Automated Monday report does not arrive for two consecutive cycles by Week 8
Cost to walk away: Walk-away cost: NZD $30–40K (Stage 1 spend to that point). Spend stops immediately.
Decision owner: CFO — kill-switch calendar written and held before Day 1
POS API access not confirmed in writing by Day 3
Cost to walk away: Scope shrinks to the data source that can prove the Monday loop fastest. No additional spend unlocked until access is confirmed.
Decision owner: CFO + IT lead — named before work begins
Automated vs manual report reconciliation diverges beyond agreed tolerance at Week 5
Cost to walk away: Dual-run period extended. No Stage 2 funding unlocked until Stage 1 reconciliation is clean.
Decision owner: CFO signs off on agreed tolerance threshold before Stage 1 begins
The three numbers to hold
- NZD $54K — Stage 1 budget cap. Cost of being wrong is named before Day 1.
- Week 8 — Kill check. Monday number must be automated by here or spend stops at NZD $30–40K.
- Month 9 — Conservative breakeven. The confidence equation clears the bar before the 12-month mark.
The Staging Discipline — Scaffolding Removed as Confidence Grows
Each stage unlocks only after the prior feedback loop demonstrates it is working. This is not caution for caution's sake — it is the mechanism that builds genuine confidence rather than manufacturing a leap of faith. Staged proof is what makes the crossing teachable.
As confidence grows and the business demonstrates it can hold the new operating model, scaffolding is removed. Graduation is the proof the crossing worked. The end state is a business that runs AI-native and self-directs.
Stage 0
Stage 0Turn tech-strategy trust into the smallest responsible leap.
Confidence signal: POS/API access, BI vendor fit, owners, and kill-switch calendar confirmed by Day 14 so the leap is bounded, not blind.
Adaptation trigger: If a known unknown stays unresolved, shrink the scope to the data source that can prove the Monday loop fastest.
Stage 1
Stage 1Automate the Monday number and saleId ROI, then prove POS-to-loyalty join quality before expanding the system.
Confidence signal: First automated Monday by Week 5, four consecutive on-time reports by Week 16, and a customer-response join that is useful without being creepy.
Adaptation trigger: If API access, reconciliation quality, KYC/customer identity, or vendor fit blocks flow, change the ingest path or pause at Week 8.
Stage 2
Stage 2Add store replenishment and FX margin visibility only after Stage 1 is stable.
Confidence signal: Store exceptions and landed-cost exposure change weekly decisions without reintroducing manual spreadsheet work.
Adaptation trigger: If store workflow or treasury assumptions prove wrong, revise the destination before adding more automation.
Stage 3
Stage 3Pilot AI-assisted buyer briefs after the knowledge base has enough owned truth.
Confidence signal: Buyer briefs meet or beat the human baseline and compress onboarding without inventing supplier context.
Adaptation trigger: If brief quality fails, keep the captured knowledge and stop the AI layer until the evidence improves.
This Is the Decision Gate
Three gates have been run. Reality was named honestly. The Dream is specific enough to anchor a commitment. The Bridge has a cost cap, a written kill switch, and four proof-sequenced stages. The confidence equation is solvable.
The commitment belongs to the CFO and the Owner. Not to the guide. What the guide provides is an accurate enough picture that the decision is made on evidence, not faith — and a written kill switch that means the cost of being wrong is visible before any work begins.
What a GO decision at Gate 3 commits to
- Stage 1 budget of NZD $54,500 — capped, not open-ended.
- Week 8 kill check — written and held by the CFO before Day 1.
- Four GO conditions confirmed by Day 14 before build spend begins.
- Dual-run validation: automated report reconciled against manual for four consecutive weeks.
- No Stage 2 funding unlocked without Stage 1 proof.
- A guide who earns continued trust by showing the path, not by managing the perception of progress.
Next — the decision summary
Decision Summary — What to Do This Week
The decision summary names the four GO conditions, the five next actions, and the three numbers. One page. Everything needed to decide by Day 7 and ship by Day 90 — or walk at Week 8 with the cost capped.
Read the decision summary →Dig Deeper
This page keeps the BRIDGE gate readable. The full 90-day week-by-week, financial model, and benefit ledger live in the instrument pages — go there for depth when the decision is being stress-tested, not before.
- Critical Path — 90-day week-by-week + 4-stage roadmap with named owners and adaptation triggers
- Financial Impact — 3 scenarios × 24 months, conservative payback Month 9, bounded NZD $54K Stage 1 bet
- Benefit Ledger — itemised benefit-by-benefit breakdown, 3 scenarios with confidence grades
- One-Page Plan — commercial strategy on one screen: fee, payback, benefit:cost, the ask
- Decision Summary — what to decide this week: 4 GO conditions, 5 next actions, 3 numbers
- Build Platform (Build Vessel) — the technology stack recommendation: atoms to bits in the right order, with governance and the action layer