In 14 days, we take one recurring process that relies too heavily on you and turn it into a clearer, documented and delegatable system — without redesigning your entire business.
We look at both sides of the bottleneck: what's missing from the system, and what you've had to do manually to compensate for it.
That might mean remembering, approving, chasing, checking or stepping in to rescue the work. The output is practical, not therapeutic.
We work with founder-led service and property businesses — hospitality and boutique accommodation, serviced accommodation, cleaning and housekeeping, wellness studios and spas, retreats and experiences, and adjacent founder-led businesses with repeatable delivery. Revenue is context, not the qualifier — founder dependency is.
What decisions route back to you, what triggers escalation, and where decision rights are unclear.
Sales-to-delivery, onboarding, project-to-project handovers — where context is lost.
Where your team waits for sign-off because the "good enough" standard lives in your head.
Where revisions, exceptions and "quick favours" leak in without a rule for what's included.
The same questions your team keeps asking — and where the answer should live instead.
Where you step in to fix the team or delivery — and the system gap behind it.
We identify the recurring dependency, what's causing it and what needs to exist so the process can run with less reliance on you.
Starts with a 45-minute kickoff and review of relevant examples and materials.
I build the improved process, documentation and supporting assets needed to make it usable by someone else.
Depending on the process, this might include an SOP, checklist, decision guide, handover, template or practical improvement to an existing tool. Simple automation may be used where appropriate.
We test the system, hand it to a nominated owner and agree a simple 30-day measure so you can tell whether it's holding.
Includes a 30-minute handover.
The 14-day delivery window assumes agreed materials and feedback arrive on time. If required input is delayed, the delivery clock pauses rather than the work being rushed.
Simplified sample shown. The Sprint builds one selected system in full — full detail is provided once the paid engagement begins.
If I determine during Find that the dependency can't responsibly be solved within the Sprint, I'll stop before Build begins and refund you — rather than force the wrong problem into the wrong scope.
I'd rather tell you the scope is wrong than sell you a system that won't hold.
50% to secure your Sprint · 50% before final handover
This founding rate applies to the current intake. Future intakes will be priced higher.