04
Growth has stalled in a way more effort won’t fix.
12xdecision.com.au — Central Coast, Australia · United States
Guardrails: Stop Improvising in Front of Prospects
Pricing debated in the room. Scope decided on the spot. A different explanation every time. Guardrails set the rules before the meeting, not during it.
If This Is You
The presenting conditions we see most in Guardrails
You don’t need all of them. One is usually enough.
05
Your team waits for you, even when they shouldn’t have to.
06
You’ve been meaning to fix this for two years.
These aren’t problems you solve by working harder or thinking differently. They’re structural. The conversation starts here.
Inside the Engagement
What Decision Architecture looks like when it’s applied to Guardrails
Guardrails are a written ruleset. Pricing floors, scope boundaries, delegation triggers, escalation thresholds — the decisions your team currently improvises in the room, captured before the room. Not a values statement. Not a “we should probably” conversation. A document that names the rule, the exception, and who can invoke each.
Most founders reach for confidence coaching when this is the problem. It doesn’t work. Confidence in the moment is downstream of clarity before the moment. If the pricing rule isn’t written down, the person in the meeting will negotiate against themselves — every time — because there’s nothing to hold. Guardrails give them the thing to hold.
Inside a DA engagement, Guardrails get produced as a discrete artefact — usually a wire-bound document the team can reference in real time. Pricing rules, scoping heuristics, delegation matrices, escalation paths. The scope depends on how many functions the ruleset needs to touch. A single-function ruleset (say, pricing) can be produced from a Blueprint. A cross-function ruleset (pricing plus scope plus delegation) usually rides on top of a 30-Day Audit.
The test is whether the rules work when the founder isn’t in the room. That’s the whole point. Guardrails don’t make the founder unnecessary — they make the founder’s judgment portable. The team acts on the rule, escalates the exception, and the founder gets to weigh in on the exception rather than every decision.
The Core Practice
Four tiers. One methodology.
Every situation runs through the same practice. Guardrails can be produced as a standalone artefact from a Blueprint if the scope is tight, or as part of a broader Audit if the ruleset needs to touch multiple functions.
For Guardrails, the 48-Hour Blueprint is the tightest starting point — ideal when the ruleset is single-function (pricing, scope, or delegation) and needs to land fast. When the ruleset spans multiple functions, the 30-Day Audit is the better fit.
48-Hour Blueprint
For Immediate DecisionsWhen you need a clear answer fast. One focused session. One decision brief. Delivered in 48 hours.
$1,500 AUD
Begin the Inquiry →
30-Day Audit
For Structural ClarityA full audit of where decisions are stacking up and why. Three sessions, seven wire-bound artefacts, one written report.
- Operations Mapping — How work actually moves through your business
- Decision Flow Analysis — Where decisions stack up, who makes them
- People & Roles Review — Who does what, where the gaps are
- Risk Identification — What would break if you weren’t there tomorrow
$8,500 AUD
Begin the Inquiry →
90-Day Architecture
For Lasting ChangeFull structural redesign. Decision rights, reporting lines, delegation frameworks, and operational guardrails. Built to run without you in the room.
$22,000 AUD
Begin the Inquiry →
Systems Build
For ImplementationFull installation of the 90-Day Architecture alongside your leadership team. Decision rules embedded, guardrails deployed, resistance coached through. Not a design engagement — this is where the redesign becomes how the business actually runs.
On inquiry
Begin the Inquiry →
How We Work
Fifty years of pattern recognition. AI where it helps.
Fifty years across ten industries teaches you how businesses actually break. AI helps us surface those patterns quickly — transcripts, decision maps, cross-industry reference — so we spend our time on the judgment work, not the mechanical work.
AI is a tool. Judgment is the product.