Current intake · 2 places remaining · Apply →
FAQ · Quick answers

The questions founders actually ask.

Straight answers on application, fit, format, confidentiality and what happens after.

01 Why only one dependency? +
Because one system, built properly and actually handed over, is worth more than five half-finished ones. Most founder-led businesses have several dependencies. The Sprint identifies the one with the best combination of frequency, impact and how transferable it is — and builds that one to the point your team can run it.
02 What counts as a "system"? +
Whatever form actually closes the gap: an SOP, a decision-rights guide, an escalation rule, a quality checklist, a handover, an onboarding flow, a change-request process, a response template, a tracker — or occasionally one simple no-code automation, where that's genuinely the right tool. The system is chosen to fit the dependency, not the other way round.
03 Do I need an existing SOP to start? +
No. Most founders don't have one for the dependency that matters most — that's usually exactly why it still runs through them. What you need is real examples of how the work actually happens now, messy version included.
04 Is automation included? +
Not automatically. The goal is to reduce founder dependency, not add technology for the sake of it. If a straightforward automation would genuinely improve the process and sits comfortably within scope, it may form part of the system. The Sprint does not include complex API work, custom development or advanced AI builds.
05 Is this coaching? +
No. This is practical operational work, not coaching or therapy. We look at what the process is missing and what you've had to do personally to compensate for that gap. The output is a working system, not an ongoing advice relationship.
06 What if my whole business feels messy? +
That's normal, and it's not what the Sprint tries to fix. It deliberately solves one dependency well rather than attempting an entire-business redesign. If the underlying issue turns out to be broader — staffing, strategy, or something needing ongoing support — I'll say so, rather than force a fit.
07 What happens if the issue isn't suitable for a Sprint? +
Days 1–3 include a buildability checkpoint. If, once the dependency is properly scoped, I determine it can't responsibly be solved within a 14-day fixed-scope Sprint, I'll stop before implementation and refund you — rather than force through something that won't hold up.
08 What do I need to provide? +
Access to relevant examples and material for the dependency in question, roughly 45 minutes at kickoff, one consolidated round of feedback, and 30 minutes for the final handover. Redact anything sensitive first — customer, employee or financial detail that isn't needed to understand the workflow.
09 What if my feedback is late? +
The 14-day clock assumes materials and feedback arrive on the agreed timeline. If a required input is late, the delivery clock pauses rather than the Sprint being rushed or compressed to fit.
10 Is the work confidential? +
Yes. Anything you share is treated confidentially and used only to deliver your Sprint. You can redact client names, employee names, financial detail or anything else commercially sensitive before sharing. For founding-round case studies, only anonymised patterns and outcomes are used, and only with your written permission.
11 Do you need passwords? +
No, passwords are never requested. Where a simple automation is built, client-owned accounts are preferred, personal-data access is minimised, and a manual fallback is kept for anything operationally important.
12 What happens after the Sprint? +
You leave with the working system, clear ownership and a simple 30-day measure. If the Sprint surfaces another important dependency, I can document it as a next-step recommendation. Any further work is scoped separately — there's no automatic upsell or ongoing retainer built into this one.
Founding intake rate · £950 fixed fee

Not sure if it fits? Apply first.

No payment is taken at application. If it isn't a fit, I'll tell you plainly.