The Pre-Underway Checklist Doesn't Care About Your Feelings
Before every underway on USS Jefferson City, we ran a Pre-Underway Checklist, and that discipline is exactly what's missing from how most owner-operators approach the 77% of US businesses that now report using AI regularly, up from 48% in mid-2024 per Intuit's 2026 AI Impact Report. The checklist was not a vibe check. Not a roundtable conversation about whether the crew felt ready. A checklist. Binary. Done or not done. Reactor plant parameters verified: done. Steering checked fore and aft: done. Casualty drill procedures posted at every watch station: done. Nobody got underway on a feeling. You got underway on a signed-off list.
Most owner-operators are running their AI adoption the opposite way. They feel ready. They feel like they are ahead of the curve because someone on the team pastes customer emails into ChatGPT. That 77% adoption number looks like progress until you check what "using AI" actually means on the ground. For most owner-operators, it means one person, one tool, zero documentation, zero measurement.
That is not readiness. That is a crew member freelancing a procedure nobody wrote down. On a boat, that gets you a casualty report. In a business, it gets you a tool nobody can replicate, audit, or hand off when that person leaves.
The Gap Between Using AI and Being Ready for It
Here is the number that should stop you mid-sentence: 70% of SMBs remain in early stages of AI maturity, according to the SAS/IDC AI Readiness Survey published in May 2026. Only 9% have fully embedded AI into strategy, operations, and decision-making. Everybody else is somewhere between "we tried it once" and "someone on staff has a favorite chatbot."
That gap between adoption and readiness is the entire problem. Adoption is a headcount metric. Readiness is a systems metric. You can have 100% of your team using AI tools and 0% readiness if none of it is documented, none of it is measured, and none of it survives the person who set it up walking out the door.
McKinsey's research backs this up from the enterprise side, and the small business version is worse, not better. Only 21% of gen AI adopters report fundamentally redesigning at least some of their workflows around the technology. The rest bolted a tool onto an unchanged process and called it progress. Worse: only 1% describe their gen AI rollouts as "mature." Ninety-nine percent of organizations running AI today, at every size, are still standing watch on unfinished doctrine.
You do not fix that with more enthusiasm. You fix it with a checklist.
Why "We Use AI" Is Not an Answer on Inspection
On a submarine, if you tell the Engineer "we ran the drill" and cannot produce a signed drill card, you did not run the drill. Verbal readiness does not exist. Written, verified, signed-off readiness is the only kind that counts, because it is the only kind that survives a watch change.
Apply that standard to your business right now. If I asked you which processes in your company use AI, could you list them. Not guess. List them, with the tool, the owner, and the output it produces. If the honest answer is "I'd have to ask around," you have adoption without readiness, and that gap is where the money leaks out.
AWS built a five-step readiness framework for small business that maps almost exactly onto the boat's own pre-underway logic: data environment, high-impact use cases, tech stack, governance, and metrics. Five stations. Five checks. You do not skip one because the others look fine.
Compare that to the minimum viable version documented for small business operators: one system of record, one written process, one named owner, documented data use rules, and an approved budget. That is not a stretch goal. That is the floor. If your operation cannot clear that floor, you are not ready to scale AI, you are ready to create more undocumented risk faster.
The Tactical Audit: Run This Checklist This Quarter
Here is the audit. Print it. Walk your operation station by station the way you would walk a boat before getting underway. Each item is binary. Done or not done. No partial credit.
Station 1: System of Record Do you have one canonical place where customer data, transaction data, and operational data live? Not three spreadsheets and a CRM nobody updates. One system. If your AI tools are pulling from five different sources with no single source of truth, every output is compromised before the query even runs. A tool cannot be smarter than the data it is fed. Garbage compartmentalized across five systems is still garbage.
Station 2: Documented Process For every place AI touches your business, is there a written SOP describing what goes in, what the tool does, and what comes out? If the process lives only in one person's head, it is not a process. It is a habit wearing a job title. Habits do not transfer when the person holding them takes a new job.
Station 3: Named Owner Every AI-touched process needs a name attached to it, not a department. "Marketing handles that" is not accountability. "Sarah owns the intake-to-CRM pipeline and signs off on it monthly" is accountability. Ownership without a name is ownership by nobody, and nobody catches the failure until a customer does.
Station 4: Data Use Rules Do you have a written rule about what customer data can and cannot be fed into which tools? If you do not know whether your team is pasting client contracts into a free-tier chatbot right now, you do not have data governance. You have exposure, and exposure has a way of surfacing at the worst possible moment, usually during due diligence.
Station 5: Approved Budget Is there a line item, not a credit card someone expensed after the fact, for the AI tools your business runs on? If spending is ad hoc, measurement is impossible, because you cannot calculate ROI on a cost you never tracked in the first place.
Station 6: Verification at Six Weeks Here is the failure point almost nobody checks: does anyone verify the tool is being used correctly six weeks after rollout? Most owner-operators launch a tool with enthusiasm and never audit whether it is still being used the way it was designed. The tool degrades into a habit, the habit degrades into noise, and nobody notices because nobody scheduled the check. This single missing station accounts for more wasted AI spend than any pricing problem.
Station 7: Measurable Outcome Can you point to a number, a saved hour, a reduced error rate, a faster turnaround, that the tool produced? If the answer is "it feels faster," you are back to the vibe check. Feelings do not go on the drill card, and they do not go on a balance sheet either.
Run all seven. If any station comes back "not done," you have found your bottleneck. Fix that station before you add a single new tool. Adding capability on top of a broken station just compounds the failure faster.
The Math Behind Doing This Right
This is not a compliance exercise. It has a dollar figure attached. Deloitte Australia's research found a 45% profitability increase moving from basic to intermediate AI use, and a 111% increase moving from intermediate to fully enabled maturity. That is not a rounding error. That is the difference between a business that compounds and one that treats AI as a novelty subscription.
But you cannot skip stations to get there. The businesses seeing 111% gains are not the ones that adopted the most tools fastest. They are the ones that built the system of record first, wrote the process second, and only then scaled the tool. Skipping to scale without the floor in place is how you get a fast, expensive mess instead of a compounding asset.
Think about what an acquirer sees during diligence on your business. If your AI-touched processes are undocumented, owner-dependent, and unmeasured, that is not a growth story. That is a liability with a subscription fee attached. A business where every AI process has a written SOP, a named owner, and a tracked outcome is a business that survives a change in ownership. That is the entire difference between an acquirable asset and a hobby with better software. Buyers do not pay a premium multiple for processes that only work because one person remembers how they're supposed to work.
This is also where owner-operators underestimate the payback period. A documented SOP takes an afternoon to write. A named owner costs nothing but a conversation. A six-week verification check costs one calendar reminder. None of these stations require new spend. They require discipline you already know how to apply, you have just not applied it here yet.
Doctrine: Responsibility Beats Excuses
Nobody on a submarine gets to say "I thought someone else checked that." The checklist exists precisely because good intentions do not survive a casualty. The same logic applies here. "We're using AI" is an excuse dressed up as an update. "Here is our signed-off readiness checklist, station by station" is a report.
Owner-operators who treat AI readiness as a feeling will keep showing up in that 70% stuck in early-stage maturity, wondering why the tool that worked great in the demo produces inconsistent results six months later. Owner-operators who treat it as a checklist, verified quarterly, station by station, will be in the 9% actually running AI as doctrine instead of decoration.
Run the audit this quarter. Not next quarter. This one. Responsibility beats excuses, and a checklist is the only format that forces you to stop making them.
FAQ
Q: We already use ChatGPT and a few automation tools. Doesn't that mean we're AI-ready? A: No. Tool usage and readiness are different measurements. Readiness requires a documented system of record, written SOPs, a named owner per process, data use rules, and a tracked budget. Most businesses using AI tools have none of those five in place, which is why 70% of SMBs remain in early-stage maturity despite high adoption numbers.
Q: How often should we re-run this readiness checklist? A: Quarterly at minimum, with a lighter check at the six-week mark after any new tool rollout. The six-week check catches the most common failure: a tool that was implemented correctly on day one and drifted into misuse by week six with nobody watching.
Q: What's the single biggest readiness gap for small businesses right now? A: Named ownership. Most AI-touched processes are owned by "the team" instead of one accountable person. Without a name attached, nobody signs off on whether the process is still working, and drift goes undetected for months.
Q: Is it worth investing in AI readiness if we're a small operation with a lean team? A: Yes, and the math argues for it harder, not softer, at small scale. Deloitte's research shows a 45% profitability jump from basic to intermediate AI maturity and 111% from intermediate to fully enabled. Small teams that skip readiness and jump straight to tool sprawl tend to see none of that gain because nobody is measuring what the tools actually produce.
Q: What should happen if a station on the checklist comes back "not done"? A: Stop and fix it before adding new capability. Getting underway with an unverified reactor parameter is how you get a casualty. Scaling AI adoption on top of an undocumented process is the business equivalent. Fix the failed station first, then proceed.