A memo that decides what to do next.

What the Operating Map is

It's a memo. Read it once and you know what's broken, what it's costing, and what to do.

Eight sections. Visual process maps for every major workflow you run. An architecture diagram showing what currently connects to what, and what would after. A dollar figure on what the current state is costing you per month. A phased roadmap from week one to week twelve. A quantified ROI based on your numbers from the discovery call, not industry benchmarks I made up.

The point of the memo is to make a decision. Implement the three highest-leverage moves yourself. Hire me to build them. Take the memo to someone else to execute. Any of those is a valid outcome. The memo gives you the information to decide.

What gets looked at

Four lenses, applied to every part of the business that matters.

• Where the business depends on you. The calls only you can make. The standards only you can hold. The judgment that hasn't been written down. Operations that depend on one person aren't operations yet.
• Where work is being re-done. Data re-entered. Decisions re-litigated. Tasks waiting on someone else's review. Every handoff that breaks is a place the company loses speed.
• Where machines can take over. AI as one input. Not “use ChatGPT more.” Specific places where an automation, an AI workflow, or a rule could carry work that's currently routed through a human who'd rather be doing something else.
• What the structure is asking of you. Sometimes the org chart isn't the problem. Sometimes the way the team is shaped is the problem. The memo will tell you if you have a structural issue, an automation issue, a judgment issue, or some combination.

How it works

1. Walkthrough. 90 minutes, week one. You walk me through how the business actually runs. Every major workflow, every decision routing, every place work gets stuck. I draw it on the wall. By the end of session one, you've seen your operations mapped for the first time.
2. Draft review. 90 minutes, week two. I come back with the draft memo: process maps, architecture, the cost of inaction calculated from your numbers, the proposed moves. We work through it together. You push back, correct what I've gotten wrong, sharpen the priorities.
3. Final read. 90 minutes, week three. The final memo. Eight sections. A 12-week implementation roadmap with weekly deliverables and a recommendation on whether to execute internally or with outside help.

The memo arrives within 48 hours of session three.

What the memo contains

1. Executive summary. One page. Your situation in three sentences, in your own language. What I'm proposing in three sentences. Expected outcome in three sentences. Investment range. If the summary is weak, nobody reads the rest.
2. Current state. Visual process maps for every major workflow. Who owns what. Where the handoffs break. Where data gets re-entered. Where work sits waiting.
3. Cost of inaction. Dollars per month being lost. Hours per week being burned on manual work. Opportunity cost. Risk you're carrying. All using your numbers, not mine.
4. Proposed solution. Architecture diagram. Before-and-after process maps. Specific tools, not vague tech talk. Data flow. Security considerations. The thinking, not just the build.
5. Implementation roadmap. Week 1–4. Week 5–8. Week 9–12. Clear deliverables per phase. If we work together, you'll see daily demo items in a shared Slack, not a three-week delivery wait.
6. Quantified ROI. Hours saved per month. Dollars saved per month. Capacity unlocked. Payback period. Under-promised on purpose. If the memo projects $20K and you see $8K, I've lost you. If it projects $8K and you see $12K, you're the next case study.
7. Investment. Included if you choose to engage further. Total cost. Phase breakdown. Payment terms. Scope boundaries.
8. Next steps. Included if you choose to engage further. Kickoff timeline. Signing link.

Who it's for

Founders and operators of growing businesses that are working but starting to break.

You're hitting one or more of these walls:

• The team can't move faster than you can review their work.
• Hires aren't ramping. You're still the person who has to train them.
• The methodology, the standards, the pricing logic still live in your head.
• You've heard AI could help, but every demo you've seen looks like a toy.
• You can't tell whether you need to hire, restructure, or buy software.

The Operating Map tells you which.

What happens after

Three outcomes, all common.

• You take the memo and execute internally. The implementation roadmap is detailed enough to do this.
• We continue together. A Project (defined scope, fixed price, time-boxed) or an Embed (fractional COO, ongoing, monthly). Pricing is in the memo. The $1,999 you paid for the Map is credited toward whatever follows.
• You take the memo to someone else. The memo is yours either way. Take it to another operator, another agency, an internal hire. The work still gets done.

The memo names the path. You pick which one.