Operational freedom is not a people question.
It is an architecture question.
As long as decisions, processes and client relationships run through you, your business is structurally dependent on you. That is not a leadership problem but a system failure.
90 days · scope after the Diagnostic
What 90 days produce.
- The baseline: the value later progress is compared against
- The target architecture: how your business must be structured for dependency to fall
- A responsibility and decision model: who decides what, within which frame, above which threshold
- The critical systems in the right order
- First implemented handovers: delegations that actually happened and work
- Checkpoints at which the structure is tested
- A measurement system for the time afterwards
What 90 days do not produce.
We draw this line deliberately, so the promise stays unambiguous:
- No complete independence from you. That is a process across quarters, not weeks.
- No complete operational transformation.
- No implementation of every identified system.
- No permanent personal support. The mandate is limited to 90 days.
- No sale readiness. After the 90 days the structure stands, not the sellable state.
Build to Leave™ does not promise independence in 90 days. In 90 days it creates the structure and the first robust evidence that dependency is falling.
What is designed and set in motion during the 90 days, you then implement in daily operations. Reckon with about a year for that. Anyone intending to sell afterwards commissions ExitReady™ separately.
Founder dependency is a valuation problem.
Buyers, investors and partners measure independence. A company whose value lives inside the founder's head is not a transferable asset. It is a risk. Build to Leave™ addresses exactly this structural deficit, not with delegation but with system architecture.
What is included and what is not.
You are not buying access to us for 90 days. You are buying a system for reducing your owner dependency, in which our effort sits where diagnosis, architecture, decision or correction is needed.
- The Owner Dependency Diagnostic as the baseline
- A kickoff with a binding scope
- The six gates
- Architecture and decision design
- Review of the decisive work products
- After each gate, in writing: decisions and next steps
- Bundled written support between the gates
- The T90 review against the baseline
- The agreed re-measurement at six and twelve months
- Daily project management
- Ongoing operational work
- Writing every SOP
- Implementing every system identified
- Managing your people on your behalf
- Tool administration
- Constant availability
- Unlimited review rounds
Mandates start at CHF 32,000. The scope is set after the Owner Dependency Diagnostic, because only then is it clear what is being worked on. "From" binds the scope; it is not a negotiating signal.
There is a defined written channel for questions on live work packages. Handling is bundled, not on demand. The extent is set in the mandate. Interventions outside the agreed scope are commissioned separately.
Four dimensions. One function.
Build to Leave™ is not a programme. It is a way of thinking and building. The goal is a company that runs without the founder. That requires work across four areas simultaneously.
Clear accountability structure
Who decides what, when, without asking? As long as that answer begins with your name, the business is structurally not scalable. Role definition is not an HR task but the first building block of operational freedom.
- Decision matrix per role
- Accountability transfer documented
- Escalation paths defined
Decisions without the founder
Decisions must run through the system, not through one person. That requires defined decision rules, principles and trigger points, independent of who is in the office.
- Decision rules documented
- Principles over case-by-case decisions
- Recurring decisions automated
Workflows without tacit knowledge
Every process living inside the founder's head is a bottleneck. Process logic means: make visible, structure, make transferable. Not as a documentation project, but as an operational necessity.
- Core processes visible and structured
- No process lives only in the founder's head
- Onboarding viability checked
Handover by design
Real delegation is not 'you do that now.' It is a structured transfer with context, decision framework and clear outcome. Delegation without system creates re-delegation.
- Delegation framework per function
- Feedback loops without loss of control
- Founder as architect, not operator
Where do you stand today?
Build to Leave™ does not describe an ideal state reachable in one step. There is a measurable path from complete dependence to structural independence.
Founder as bottleneck
The company stops without you. Every decision goes through you. Processes live inside your head.
First structural transfer
Roles are defined. First processes documented. Delegation begins, but the founder is still the safety net.
Operational independence
Day-to-day runs without you. Decisions are made systemically. The founder designs rather than operates.
Structural transferability
The business is transferable. No critical dependencies. ExitReady™ can begin.
Six gates in 90 days.
We do not take on the operational project management. We determine what has to change, in what order, and how you would know it worked. Execution happens inside the company.
Gate, decision, execution inside the company, evidence, review, next gate.
The week ranges are indicative and overlap. What binds is the order of the gates and their conditions, not the calendar.
Scope and target architecture
Week 1- Confirm the relevant dependencies from the Diagnostic
- Determine the largest lever
- Define the target state for day 90
- Assign ownership for execution
- Fix the measures
- 90-day scope
- Target architecture
- Prioritised dependencies
- Success criteria
- Named internal owners
No start without named ownership inside the company.
Constraints and intervention design
Weeks 2 to 3- Identify the structural constraints
- Determine cause rather than symptom
- Prioritise the interventions
- Deliberately discard what is not needed
- Constraint map
- Prioritised interventions
- Execution backlog
- A clear order
Only measures that pay into the prioritised dependency.
Critical systems
Weeks 3 to 6- Determine which processes sit implicitly with you today
- Depending on the mandate: decision paths, client handovers, proposal and sales processes, sign-offs, core operations, business-critical knowledge
- Set standards only where they lower the dependency
- Define roles, inputs and outputs
- Defined critical systems
- The necessary standards, no more
- Roles with inputs and outputs
- Defined control points
As little systematisation as possible, as much as necessary. The goal is not to write as many SOPs as possible.
Decision rights and delegation
Weeks 5 to 8- Who may decide what
- What limits apply
- When escalation happens
- Which responsibility actually transfers
- What the newly responsible person needs to know
- Decision rights
- Delegation matrix
- Escalation rules
- First real handovers
A delegation counts only once it has actually happened and works without you taking it back.
Management and control
Weeks 7 to 10- Determine the few measures that actually steer
- Set the management rhythm
- Define decision reviews, exceptions and escalation points
- Put feedback loops in place
- Management system
- Minimal control logic
- Defined escalation points
- Relevant management measures
Only the control this business needs. No dashboard where none is needed.
Evidence and handover
Weeks 11 to 13, day 90- Which decisions run without you
- Which handovers hold
- Which escalations have disappeared
- Which critical dependencies remain
- Where responsibility fell back
- Which systems already carry
- T90 review
- Comparison against the baseline
- Open dependencies
- Prioritised next steps
- Measurement points at six and twelve months
What is examined is the change inside the company, not the number of sessions attended.
Know your level.
The free quick check asks four questions, one per area, and sorts where dependency sits by your own assessment. No advisory, no call.
To the quick check →ExitReady™
Operational freedom is the prerequisite. ExitReady™ prepares governance, documentation and handover structures for due diligence.
View ExitReady™ →Build to Leave™ rests on a documented decision logic: the CEOPRENEUR Principles and the Decision Matrix™. Openly accessible.
View frameworks →