Diagnose · Where to start
What is actually slowing the business down—and what is the smallest useful fix?
In two weeks, I follow one important workflow, talk with the people doing it, and inspect the tools and handoffs. You leave with the diagnosis, a build specification, a fixed-price proposal, and a starting measure. The diagnostic defines the fix; implementation is a separate step.
2 weeks
$7,500 fixed · credited toward a build
One principal · Scope agreed in writing
Who it’s for
When this is the right step.
For an owner, COO, or department leader who can feel the drag—missed follow-up, slow handoffs, repeated decisions, too much work routing through one person—but cannot yet see the first fix clearly.
- Leads, requests, or jobs enter the business but do not move consistently.
- The owner or COO is still the default router for routine decisions.
- The CRM holds records but does not guide the work.
- Handoffs depend on messages, spreadsheets, and memory.
- A key person is leaving, or the business has outgrown its current way of working.
Outputs
What you get.
- A plain-language diagnosis of where the work breaks down
- A map of the workflow, handoffs, systems, and decision owners
- The specific rules, states, or connections that are missing
- A focused specification and fixed price for the first build
- A simple baseline for judging whether the change helped
- A working session to decide what to do next
Week 1
Listen and look
Conversations with the people doing the work, plus a walkthrough of the tools, handoffs, and records around one important flow.
Week 2
Follow the work
Follow the work end to end. Find where it stalls, which decisions repeat, and who is compensating by hand.
Readout
Decide
A clear diagnosis, a fixed-price plan for the first fix, a starting measure, and a plain recommendation—including if the answer is to leave it alone.
Pricing
Founding-client rate: the first three diagnostics are $5,000 in exchange for permission to describe the work publicly, anonymously if preferred. A reference call is requested only if the work earns your recommendation.
Boundaries
The fine print, up front.
Stated before any contract, so scope and expectations are clear.
- One business unit or revenue motion. A whole-company assessment is scoped separately.
- No software or data is changed during the diagnostic.
- No outcome is promised before the starting point and first build are understood.
- There is no obligation to build with TKO. The specification is yours to use with anyone.
What comes next: If the first fix is worth building, the diagnostic ends with a fixed-price Operating System Build. The diagnostic fee is credited if that build starts within 30 days.
Typical work
What this usually involves.
Is this a sales pitch in disguise?+
No. It is paid, fixed-scope work with a written report you keep, whether or not you hire me for anything else.
How much of my team's time does it take?+
About 45 minutes each for up to six people, plus a walkthrough of your main systems. Most of the work happens on my side.
Our data is a mess. Is that a problem?+
No. Messy data is usually part of the finding. The diagnostic shows which mess actually matters.
Do you work in person?+
In South Florida, yes, if you prefer it. Everywhere else, the work runs remotely.
The other steps
Start with the smallest step that answers the question.
One principal · Priced up front
Tell me what's stuck.
Bring one workflow that keeps slowing you down, or an AI idea you want to put to work. In 30 minutes, we will talk through the problem, the tools involved, and whether a diagnostic or a scoped build is the right next step.