How Fodge works
One workflow. One owner. One result. Three phases to get there.
Most teams we meet already own the AI tool sprawl — bought, integrated, demoed, abandoned in a shared drive. The fix is not a smaller pile of tools; it is a smaller pitch. One workflow, owned end to end by a single human, measured against one business number, run through three named phases.
The three-phase arc
Map. Ship. Run.
Each phase has a named owner, a written deliverable, and a number we can read on the way out. The phases do not repeat. Once the workflow is running on a Tuesday without us in the room, we close the chapter.
Phase
01
Map the workflow
Two weeks of paid discovery, named on both sides — your operator, our practitioner. We walk the workflow with the team, surface the bottleneck, and pin the one number the business already watches before anything is built. Outcome: a written map, a short vendor short-list, and a price scoped to the workflow actually being changed.
Owner
Your operator and our practitioner, named on both sides.
Outcome
A written map, a short vendor short-list, and a price scoped to the workflow actually being changed.
Phase
02
Ship the system
Three to six weeks of install, inside the stack your operator already uses. The prompts are written in your voice, the routing is rehearsed with the owner-of-the-workflow during their first real busy week, and the runbook lives in your wiki, not a vendor portal. Outcome: a workflow running on a Tuesday without us in the room, measured against the same number we pinned in Map.
Owner
The owner-of-the-workflow on your team sits in on the first sessions and runs the rest.
Outcome
A workflow running on a Tuesday without us in the room, measured against the same number pinned in Map.
Phase
03
Owner runs it
Ninety days of measurement on your side, with a written wrap at the end. Your team owns the runbook, the routing, the prompts; we come back at month one, month two, and month three to read the same number, not a new dashboard we invented. Outcome: the workflow keeps running, your team keeps owning it, and we close the chapter on the engagement.
Owner
Your team owns the runbook, the routing, and the prompts after handoff.
Outcome
The workflow keeps running, your team keeps owning it, and we close the chapter on the engagement.
What stays the same
One number. Pinned before anything is built.
First-reply time. No-show rate. After-hours capture. Whatever the business already watches, that is the number we pin in Map, measure against in Ship, and read at the end of Owner runs it. If the number does not move, the workflow was the wrong one — and we say so on the written wrap, not on a glossy quarterly deck.
01
Map the workflow
We pick the number together, in plain language, before any vendor or prompt is touched.
02
Ship the system
Every install step is held against the same number. New dashboards, invented metrics, and per-call meters do not replace it.
03
Owner runs it
We come back at month one, month two, and month three to read the same number — your team owns the workflow, not the report.
Example systems — In action
A voice AI handling the front-desk intake for a wellness center.
Map built it in two weeks. Ship rehearsed the prompts with the owner-of-the-workflow during the first real busy week. Owner runs it reads against first-reply time — the number the wellness center already watches.
A second and third worked illustration below — same three-phase shape, two different workflows. The retention picture looks like text drafts reviewed before send, not after-hours calls answered in under two rings. The marketing picture looks like trial- pass nudges drafted in the owner's voice, sent under her name. The owner-of-the-workflow still owns the send.
Map
01
Two weeks, paid discovery.
The owner-of-the-workflow + our practitioner named the gap: missed calls after 6pm. A voice AI covers after-hours with a single routing rule. The number pinned: first-reply time, already on her dashboard.
Ship
02
Three weeks, in your stack.
Prompts written in her voice — not ours. The routing tree + scripts live in her wiki, not a vendor portal. The first ten real calls rehearsed with her in week two.
Run
03
Six weeks in, owned by her.
The owner-of-the-workflow owns every Friday review. First-reply after 6pm is under one minute. The AI triage resolves in under two rings.
This is a worked illustration, not an engagement quote. The price for your workflow is scoped after Map — never on the marketing page.
Map
01
Twelve-week churn, scoped to one practice.
Four sessions over two weeks with the chiropractor + our practitioner named on both sides. The off-boarding text messages after a care plan are written by the front desk — half feel templated, the practice loses patients at week twelve. The number pinned: twelve-week retention, already on her quarterly review.
Ship
02
Three weeks of writes and reviews in your stack.
AI drafts the post-care messages in her voice — the same voice the patient remembers from the consult. Every draft lands in her queue with the source chart attached. The practitioner or the named front-desk lead opens each one, edits where it's wrong, and sends from her number. The runbook lives in her wiki, not a vendor portal.
Run
03
Eight weeks in, owned by the practice.
The practitioner owns Friday reviews. Every send is a human send — the AI never delivers a message without a name attached to it. Twelve-week retention is up; the front-desk lead keeps owning the queue. The role of the AI is to draft, the role of the human is to read and send.
This is a worked illustration, not an engagement quote. The price for your workflow is scoped after Map — never on the marketing page.
Map
01
Two-week discovery with the studio owner.
Two weeks of paid discovery named on both sides — the studio owner + our practitioner. The gap surfaces between day one and day seven of a trial pass: no follow-up, the trial expires before the second visit. The number pinned: second-visit rate, already on her weekly review.
Ship
02
Three weeks of writes in her stack.
AI drafts the day-3 and day-7 nudges in her voice, every draft lands in her queue with the trial-pass source attached. The studio lead opens each one, edits where it is wrong, and sends from her address. The runbook lives in her wiki, not a vendor portal.
Run
03
Six weeks in, owned by the studio lead.
Every send is a human send — the AI never delivers a message without a name attached. The studio lead owns the Friday review. Second-visit rate is up; the queue keeps moving through her, not around her. The role of the AI is to draft, the role of the human is to send.
This is a worked illustration, not an engagement quote. The price for your workflow is scoped after Map — never on the marketing page.
FAQ
The questions owners ask before a Fodge engagement. What the chapter actually looks like.
Scoped answers in our voice — how long Map takes, who runs the workflow after delivery, what human-led looks like day to day, what changes mid-engagement, and why no price is shown on this page. If yours is not here, the Contact page intake is the right place to send it.
Three exits · one chapter
Pick the next step that fits the chapter you just walked through.
No pricing on the Workflow Audit — that is scoped after one paid Map conversation, the same conversation pinned to the number the business already watches. The Starter Kit ships with the price you can see. The third exit is the shortest: drop your email for the welcome sequence and stay in touch on a monthly cadence.
Start shipping this week
AI Workflow Starter Kit — $97 one-time
Nineteen templates across four bonus modules, master guides inlined in the delivery email. The install you ship this week, owned by you from day one.
Single payment — no subscription, no per-call or per-seat fee stacked on top of the kit.
Recurring advisory
Workflow Audit
A mid-engagement option between the $97 self-serve starter and a full done-with-you install — a weekly cadence with prompt reviews, vendor selection, team training, and a monthly outcomes review.
Scoping comes after one paid discovery conversation — distinct from the demo or a self-serve kit purchase.
Low friction · stay in touch
Five short notes over three weeks
Drop your email. We send one welcome note the moment you confirm, then four more over the next three weeks — each a single piece of material you can put to use the same day.
No drip, no third-party list. One welcome sequence, then back to a monthly cadence — unsubscribe any time.
One workflow · one owner · one number · one chapter
Start at Map.
If none of the three above fit, start at Map — one paid discovery conversation and we come back with a written scope.
Book a discovery callAfter the discovery conversation, you get a written scope — the workflow, the phase plan, the deliverables, and the price. You can close the loop whether or not you sign on.