SVC · 03 · OPS
AI that ships into your operations. Not another pilot deck.
A fixed-scope, $5,000 flat engagement that finds the workflows in your business where AI genuinely buys back time, builds them, and leaves them running on your infrastructure with your team trained. We run our own practice on workflows like these. You’re buying the discipline, not a demo.
02
What this is
Not AI consulting. AI operations.
The AI consulting industry sells two products: a strategy document about what you could do, and a pilot that never leaves the demo environment. Both let everyone feel modern without anything changing about how Tuesday actually works.
This engagement is the opposite shape. We audit your real workflows — intake, scheduling, drafting, reporting, the repetitive work your best people resent — pick the ones where AI demonstrably buys back time, build them, integrate them with the tools you already use, and train the people who’ll run them. It ends with working systems in production, documented well enough that they’re yours.
Who it’s for: service businesses with real operational volume — enough intake, content, or admin work that hours saved per week compounds into headcount-scale leverage. Who it’s not for: anyone shopping for an “AI strategy” document, a board-meeting talking point, or a pilot. If what your business needs is a deck, we are the wrong vendor and we’ll say so on the first call.
03
What you get
Working systems, documented, in production.
Workflow audit
D·01
- Mapping of your operational workflows with time-cost estimates
- Shortlist of AI-suitable candidates, ranked by leverage
- Scope agreement: exactly what gets built, signed before build starts
Build & integration
D·02
- Working AI workflows built on your accounts and infrastructure
- Integration with your existing tools — CRM, inbox, calendar, CMS
- Human-review checkpoints designed in wherever judgment matters
Training & documentation
D·03
- Hands-on training for the people who will run each workflow
- Plain-language runbooks: how it works, how to adjust it, how to turn it off
Handoff
D·04
- Everything on your accounts and your infrastructure from day one
04
How it runs
Audit. Build. Train. Hand off.
Fixed scope, flat price, defined end. The engagement is designed to finish — the workflows stay, we leave.
01
Workflow audit
We sit inside your operations — calls with the people doing the work, not just the people managing it — and map where the hours actually go. Output: a ranked shortlist and a scope agreement you sign before anything gets built.
WEEK 1
02
Build
Scoped workflows get built on your infrastructure and integrated with your tools. Human-review checkpoints go wherever the work needs judgment — the point is leverage, not unsupervised automation.
• WEEKS 2–3
03
Integration + training
Workflows go live in production. The people who run them get trained on them, hands-on. First ship lands inside 30 days: real workflows, doing real work, on your accounts.
WEEK 4
04
Handoff
Runbooks delivered, access confirmed. The engagement is designed to end. If you want more built later, that’s a new scoped engagement — not a retainer you forgot to cancel.
END
05
What it costs
$5,000. Flat. Scoped before we start.
Flat price because the engagement has a defined shape: audit, build, train, hand off. You know the cost before the first call ends; we know the scope before the build starts.
AI Operations Engagement
$5,000 flat
Fixed scope, defined end
- Workflow audit with ranked shortlist
- Scoped workflows built and integrated
- Hands-on training for your team
- Plain-language runbooks
Best for: service businesses with real operational volume and no appetite for an AI strategy deck.
Scope agreement signed before build. What’s out of scope is named in writing, not discovered on the invoice.
06
Common questions
Answered honestly.
Which AI tools do you use?
Whichever fit your stack and your constraints — the audit decides, not a reseller agreement. We have no affiliate relationships with tool vendors; the recommendation is the one we’d run ourselves.
Do we need engineers on staff?
No. The workflows are built to be run by the people who already do the work, and the runbooks are written in plain language. If a workflow needs an engineer to keep alive, we scoped it wrong.
Will AI replace anyone on my team?
That’s not what this is for, and businesses that frame it that way build the wrong workflows. The leverage is in buying back the hours your best people spend on repetitive work — so the judgment work gets more of them, not fewer.
What happens when the models change?
The runbooks document how each workflow is wired so adjustments are tractable. Beyond handoff, ongoing maintenance is a conversation, not an automatic fee.
Is this a retainer?
No — flat engagement, defined end. If you want more workflows built later, that’s a new scoped engagement at the same flat structure. We don’t do the retainer-you-forgot-about business model.
Can you just tell us our “AI strategy”?
No. A strategy document about workflows nobody builds is exactly the product this engagement exists to not be. If you want to know what’s possible, the audit week answers that with specifics — and ends in working software either way.