Situation · 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 conditions we see most in Guardrails.

You don’t need all of them. One is usually enough.

04

Growth has stalled in a way more effort won’t fix.

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 sales training 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 the Diagnostic. A cross-function ruleset (pricing plus scope plus delegation) usually rides on top of the Blueprint.

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.

Practice

Three tiers. One methodology.

Every situation runs through the same practice. The context changes; the methodology holds.

Beyond the ladder Systems Build — On inquiry

The Architecture becomes how the business actually runs. Guardrails deployed. Decision rules embedded. Resistance in the team worked through. Scope depends on the state of the business at the point of installation.

For Guardrails specifically, Systems Build is where the ruleset gets installed across every function it needs to reach. Larger engagements, succession windows, and specific operational builds. By inquiry.

Scope and price by inquiry

Start the inquiry →

Outcome

What you get, and what it does.

For Guardrails, the artefact is the Diagnostic for a single-function ruleset, or the Blueprint for a cross-function one: a written document (usually wire-bound) naming the rule, the exception, the escalation path, and who can invoke each. It is not a values statement and not a training deck. It is the thing the team references in the room so they stop improvising.

Act on it, and pricing stops drifting, scope stops expanding mid-meeting, and the founder stops being the escalation point for the same five decisions every week. The team keeps acting on the rule and escalates only the genuine exception, which is where the founder’s judgment is actually worth having.

How we work

Fifty years of pattern recognition.
Applied to your situation.

Fifty years across seven industries and four continents teaches you how businesses actually break. Work spanning the US, UK, Australia, Singapore, China, and Bangladesh. Food service, financial services, real estate, workforce training, construction, mining services, recruitment. The patterns repeat. The work here is to read the pattern in front of us, and design the structure that holds it.

Every engagement leaves a permanent artefact. A bound booklet after the Diagnostic. A written brief after the Blueprint. A full architecture document after the Architecture engagement. A decision that is made once and stays made, on paper, signed at the top.