The Core Promise
Identify what's creating the most founder dependency, then leave with a plan
Most founders don't need another person carrying part of the load, and they don't need a deck telling them everything is broken. They need to know which one or two things are creating the most founder dependency, operational uncertainty, and unnecessary mental load, and they need a credible architecture for removing it.
That is what the Sprint produces. Not a list of everything wrong, but a clear operating architecture and a prioritized 90-day plan that tells you where to start, what to leave alone, and why. By the end, the next move is obvious whether you run it yourself or bring in help.
The Sprint Answers
Ten questions the Sprint resolves
Every Sprint is built to answer the same set of questions, because these are the questions that separate a symptom from the system underneath it.
What is actually breaking?
What is merely a symptom?
Where is the founder unnecessarily embedded?
Where does information live?
Where are ownership and decision rights unclear?
Which systems are missing?
Which systems are overbuilt?
What should be fixed first?
What should not be touched yet?
What operating architecture would create the greatest increase in confidence?
The Scope
Intentionally narrow
The Sprint is scoped to do one thing well: produce a credible diagnosis and architecture recommendation. It stops there on purpose.
What it includes
- ·Enough investigation to produce a credible diagnosis
- ·A recommended operating architecture
- ·A prioritized 90-day sequence
- ·One focused founder session and one final review
What it does not include
- ·Implementation of any kind
- ·Full team discovery
- ·A miniature FoundationOS that quietly expands
If the scope of your problem is bigger than a diagnostic, that becomes clear during the Sprint, and the right path is one of the three this engagement is built to open up.
How It Runs
Six steps from intake to a plan
The Sprint is built to move fast without skipping the thinking. Each step has a defined job and hands off cleanly to the next.
01
Intake
A structured founder questionnaire that maps company structure, tools, operating pain, founder bottlenecks, the questions that keep coming back to you, decision flow, documentation, ownership, current systems, and known risks. I read it before we ever get on a call.
02
Selected Artifact Review
I review only the materials necessary to understand the operating environment. Not a full team discovery, not an audit of everything. Just enough to see how work actually moves through the company today.
03
Strategic Diagnostic Session
One focused founder session. We walk through where information gets stuck, where ownership breaks down, and where you have quietly become the workaround. This is where the real diagnosis takes shape.
04
Analysis
I go away and apply the Operational Confidence framework and BUILD thinking asynchronously. This is where raw observation turns into a credible architecture recommendation and a prioritized sequence.
05
The Operating Priority Map
A concise decision document showing current-state findings, major operational risks, founder-dependency points, the highest-impact priorities, a recommended architecture, what should be built first, what can wait, and a suggested 90-day sequence.
06
Final Review
One structured walkthrough. I present the map, explain the reasoning behind the priority order, and answer your questions until the picture is clear and the next move is obvious.
The Final Deliverable
The Operating Priority Map
You walk away with a concise decision document, not a sprawling audit. It is built to be read by a founder and acted on the same week.
What's in the map
- →Current-state findings
- →Major operational risks
- →Founder-dependency points
- →Highest-impact priorities
- →Recommended operating architecture
- →What should be built first
- →What can wait
- →A suggested 90-day sequence
Where It Goes Next
Three legitimate paths, no manufactured upsell
The Sprint is built to preserve trust. It opens three honest paths forward, and which one you take depends entirely on what the diagnostic shows.
Path 01
Implement internally
You take the Operating Priority Map and run the sequence yourself. The diagnostic was built to stand on its own, and many founders do exactly this with their existing team.
Path 02
A focused OS installation
If one or two systems are clearly the bottleneck, you can hire Operational Magic for a narrow, targeted build that solves exactly those, rather than committing to the full engagement.
Path 03
Move into FoundationOS
If the diagnostic shows that the problems are interconnected enough to justify it, FoundationOS becomes the logical next step, a full 90-day foundation build across the company.
If the problems turn out to be interconnected enough to justify a company-wide foundation build, FoundationOS is the natural next step, and the map hands off directly into it. If they aren't, you'll know that too, and you'll keep the diagnostic either way.
The Investment
Clarity on what to fix first, before you spend more
The Sprint is $2,997. For a fraction of what a single bad hire or a duplicated software stack costs, you get a credible diagnosis, a recommended architecture, and a prioritized sequence that keeps you from building the wrong thing first.
Straight Answers
The questions that come up most
Is this just a funnel into FoundationOS?+
No. The Priority Sprint exists because some founders don't need a 90-day build, they need to know what to fix first. The diagnostic is built to create three legitimate paths forward, and implementing internally is one of them. It is never engineered merely to manufacture an upsell. If FoundationOS is the right move, the map will make that obvious on its own.
Does this include implementation?+
No. The Sprint is intentionally narrow. It includes enough investigation to produce a credible diagnosis and architecture recommendation, and it stops there. Implementation, full team discovery, and anything that would turn this into a miniature FoundationOS are explicitly out of scope.
How long does it take?+
The engagement runs from intake to final review in a matter of days, not months. The exact timeline depends on how quickly intake and the diagnostic session are scheduled, but the Sprint is designed for founders who need clarity now, not a six-week consulting process.
What if I already know what's broken?+
If you genuinely know, you probably don't need the Sprint. But most founders who feel that way are looking at a symptom rather than the system underneath it. The Sprint separates the two, so you spend money and energy fixing the actual problem instead of its loudest expression.
Who is this for?+
Founders who know operations are creating friction but do not yet know what should be fixed first. If you can feel the drag but can't point to the single point of failure, the Sprint is built to surface it before you commit to a larger engagement or a hire you may not need.
Stop guessing what to fix first
If you can feel the friction but can't yet see the system underneath it, the Priority Sprint will surface it. You leave with an Operating Priority Map, a recommended architecture, and a 90-day sequence, and three honest paths for what to do next.