Pilot round open · 3 founder places · £500 diagnostic
The Founder Dependency Diagnostic

The Founder Dependency Diagnostic.

A 5-day, mostly off-call review that shows where your business still depends on the founder — then identifies the first fixes to reduce that dependency.

Format
5 working days · mostly off-call
Pilot price
£500 · 3 founder places
Standard price
£1,200 · after pilot
Application
No payment taken at application

The Diagnostic looks at both sides of founder dependency: the system gap, and the founder pattern keeping it alive.

Every founder pattern is tied back to an operating gap — a missing rule, handover, standard, escalation path or decision right. The output is practical, not therapeutic.

Who this is for

Founder-led service businesses where too much still runs through the founder.

If decisions, approvals, handovers and quality checks still come back to you, this is built for that. It works best for service businesses with a team, contractors or delivery partners — typically £300k–£2M revenue, though revenue isn't the qualifier. Founder dependency is.

UK service business, founder-led
Team, contractors or delivery partners who lean on you for decisions
Past the launch phase — you have a working business and delivery
You're aware the business depends on you too much
Open to showing the messy version, not the polished one
What the Diagnostic reviews

The places founder dependency quietly accumulates.

01

Decision flow

What decisions route back to you, what triggers escalation, and where decision rights are unclear.

02

Handovers

Sales-to-delivery, onboarding, project-to-project handovers — where context is lost.

03

Approvals & quality

Where your team waits for sign-off because the "good enough" standard lives in your head.

04

Scope & change control

Where revisions, exceptions and "quick favours" leak in without a rule for what's included.

05

Recurring questions

The same questions your team keeps asking — and where the answer should live instead.

06

Rescue work

Where you step in to fix the team or delivery — and the system gap behind it.

What you receive

Three deliverables. Built to be used, not filed.

01

Founder Dependency Map

Shows where the business depends on the founder, the system gap behind it, the founder pattern reinforcing it, and the first fix to reduce that dependency.

02

Three StepAway Fixes

A focused priority plan showing what to build first, what to stop carrying, and what to ignore for now.

03

Walkthrough

A short walkthrough or debrief to clarify priorities, ownership and sequencing.

Example

What the Founder Dependency Map looks like.

A simplified sample. Generic rows shown for illustration only.

Founder Dependency Map · simplified sample
Generic structure shown · business-specific content omitted
Illustrative only
01
Dependency 01 — Approval dependency
System gap · no shared "good enough" standard Founder pattern · over-approval
→ First fix: Delivery acceptance criteria
Priority
02
Dependency 02 — Scope-control gap
System gap · no change-request rule Founder pattern · rescue / avoidance
→ First fix: Scope-change decision rule
Priority
03
Dependency 03 — Context handover gap
System gap · no context handover Founder pattern · holding context
→ First fix: Handover template
Priority

Simplified sample shown. Full diagnostic detail is provided after application and payment.

What's included & what's not

Tight scope. On purpose.

Included

In the Diagnostic

  • 5 working days from receipt of materials
  • Kickoff call or async briefing
  • Document, workflow and decision-point review
  • Founder Dependency Map
  • Founder-pattern layer (practical, not therapy)
  • Three StepAway Fixes
  • Short walkthrough or debrief
Not included

Not in the Diagnostic

  • Implementation of systems
  • Full SOP packs
  • Team management
  • Software setup
  • Ongoing ops support
  • HR, legal, financial or strategic advice
Implementation may be offered separately if there's a clear fit. See Build Options →
How it runs

Five working days. Mostly off-call.

Day 1

Kickoff

45–60 minute call or async briefing. You share materials, examples and the dependency points you're feeling most.

Days 2–3

Review

Document, workflow and decision-point review. Off-call. I work through the materials and map the dependencies.

Day 4

Map & fixes

The Founder Dependency Map is built and the Three StepAway Fixes are written.

Day 5

Walkthrough

30-minute call or written walkthrough. What to fix first, what to ignore, and what your team can pick up.

Fit-first promise

If I don't think the Diagnostic will give you a useful map of your founder dependency points, I will not take your payment.

If, after reviewing your materials, the real problem turns out to be outside the scope of StepAway Systems, I'll tell you plainly. This is not a sell-everyone offer.

3 pilot places · £500

See where founder dependency is quietly costing you — and what to fix first.