Why I Use Military SOPs to Run My AI Consulting Practice

Most consultants run their practice on intuition, experience, and improvisation.

I run mine on SOPs.

Not because I don't trust my judgment, I do. But because judgment is expensive. It requires active cognitive work every time you apply it. SOPs are judgment pre-applied. You do the thinking once, write it down, and execute consistently without burning decision-making capacity on things you've already figured out.

In EOD, SOPs weren't bureaucracy. They were how a team of people with different experience levels could execute complex, high-stakes procedures with consistent results. The SOP captured the best-known approach so that individual variation didn't introduce unnecessary risk.

The same logic applies to a consulting practice.

The SOPs I Actually Use

Client intake. Every new engagement starts with the same sequence: an intake questionnaire that covers current AI stack, existing process documentation, team structure, and what they've already tried. I don't modify this based on who I'm talking to. The questions are the same because the gaps I'm looking for are the same.

The intake takes the client about 45 minutes to complete. It takes me about 20 minutes to analyze. Before I've had a second conversation with them, I have a preliminary picture of where the problems are.

Audit protocol. The AI Systems Audit follows a fixed sequence: inventory, process mapping, gap analysis, governance assessment, priority ranking. Each phase has a defined output. The sequence doesn't change based on the client's size or industry.

What changes: the specific findings. The process is fixed. The outputs are client-specific.

Delivery format. Every audit ends with the same deliverable structure: a prioritized gap list, a 90-day action plan, and a capability roadmap. Three documents, consistent format, every time.

Clients know what they're getting before they sign. I know what I'm producing before I start. The SOP removes ambiguity from both sides of the engagement.

Follow-up cadence. Maintenance clients get a monthly check-in using the same agenda format: what changed, what's working, what needs adjustment, what's coming in the next 30 days. I don't build this agenda fresh each month. I fill in the fields.

Why This Matters for AI Work Specifically

AI implementations have a tendency to drift. What the tool was doing on day 30 is often not what it was doing on day 1. Data shifts. User behavior shifts. The environment the agent was trained in shifted.

Without a systematic review cadence and an SOP, drift goes undetected until something breaks visibly.

The maintenance SOP catches drift before it becomes a problem. It's not exciting work. It's exactly the kind of unsexy operational discipline that determines whether an AI deployment delivers value over 12 months or just over the first 90 days.

The Objection

Some consultants resist this. "Every client is different; you can't standardize." Yes, every client's specific situation is different. That's why the outputs are custom. But the diagnostic process for finding problems doesn't need to be different. Problems have patterns. Patterns have repeatable diagnostics.

Surgeons use checklists. Pilots use checklists. The variability is in the patient and the flight conditions. The protocol is standard.

The Insight

A consulting practice without SOPs is a job, not a business. You're selling your time and judgment, fresh, every engagement. With SOPs, you're selling a system, one that produces consistent results and scales beyond what any single person's improvisation can sustain.

Military EOD taught me that the most capable teams aren't the ones who improvise the best. They're the ones whose SOPs are good enough that improvisation is rarely necessary.

The Takeaway

Pick the one thing you do most often in your work that you haven't written down as a procedure. Write it. Not a flowchart, a step-by-step written procedure with defined inputs, defined outputs, and defined decision points.

Then follow it exactly for one month. Note where it breaks. Fix it. Repeat.

That's how an SOP gets built.