Step two, when it's needed
You can't automate a process nobody ever wrote down.
Operational Foundations is the unglamorous work that has to come first: getting your workflows out of people's heads and onto paper, in a form a machine can actually read. It's not exciting. It's what makes everything after it work.
from $1,000, scoped
What it is.
Most small businesses run on undocumented expertise. The renewal gets handled because Denise has handled it for eleven years. The month-end close works because one person knows which numbers to distrust. That works right up until you try to hand the process to software, because AI works off what your business has written down, not what your people carry in their heads.
Operational Foundations is the fix. We sit inside the workflow, write it down completely, chase every "it depends" until it has a rule, and leave you with SOPs and documented workflows that a new hire or a model could follow. It's business-agnostic on purpose. The method doesn't care whether the process is insurance renewals, client onboarding, or commission reconciliation.
Simplicity is king here. We don't document everything. We document the one workflow you actually want to improve first, all the way through, and leave the rest for later.
What you walk away with.
- The one workflow you care about most, documented all the way through, including the 'it depends' moments nobody ever wrote down.
- SOPs written so a stranger, or a machine, could run the process without asking the veteran at the next desk.
- Decision rules made explicit: what happens when, and why, in writing.
- A foundation an AI build can actually stand on, whether we build it or someone else does.
Who it's for.
- The audit said 'not yet' and named the gaps. This is how the gaps get closed.
- Your business runs on people remembering the right thing on the right day, and you know it.
- You want AI eventually, and you'd rather do the unglamorous work first than pay for a build that guesses.
The honest fine print.
Engagements start at $1,000 and are scoped to the workflow. One thing we say plainly rather than bury: the AI Readiness Audit fee credits toward an AI build, not toward this work. Foundations is its own job with its own value, and it pays for itself whether or not a build ever happens, because a documented business runs better with or without AI.
Questions
Before you ask.
What does Operational Foundations cost?
Engagements start at $1,000 and are scoped to the workflow. Pricing scales with how much has to be documented.
Does my AI Readiness Audit fee credit toward this?
No. The audit fee credits toward an AI build, not toward this work. Foundations is its own job with its own value, and it pays for itself whether or not a build ever happens.
What do you actually deliver?
The one workflow you care about most documented all the way through, SOPs written so a stranger or a machine could run the process, decision rules made explicit in writing, and a foundation an AI build can actually stand on.
Do you document my whole business?
No. We document the one workflow you actually want to improve first, all the way through, and leave the rest for later. Simplicity is king here.
Is this only worth doing if we're adding AI?
No. The method is business-agnostic, and a documented business runs better with or without AI. The work pays for itself even if a build never happens.
Start with the workflow that matters most.
Tell us which process runs on memory and workarounds today. We'll scope the documentation work around it, deliberately narrow, and priced from $1,000.