Spring 2026 2 Embed slots open · Q3 2026 · see what's available
001 — Infrastructure / Spring 2026

Leverage AI inside your company.
Outpace the ones that won't.

AI Champion for mid-market leadership teams. I ship the AI systems that capture market share — production code, week one. Embedded alongside the team, not above it.

Live · 5 active engagements
Currently Embedded · mid-market AI
Available 2 slots · Q3 2026
Range Assess · Train · Deploy · Embed
Reach me
Spiritus · live daily summary sent
Bowman · live 3 trips booked today
Embed · day d-3 / 90
Deploy · ships tonight 02:00 EST
Live · last 24 hrs
02:14Spiritusdaily summary sent · 47 vendors 04:00Bowmanavailability sync run 06:30Horizon2 inbound voicemails handled 08:15Homegrownvendor onboarding email · #28 11:23B2Bembed retrospective drafted 12:08Spiritusretreat workbook v2 published 13:45Bowman3 trips booked through site 14:30Horizonmonthly route plan generated 15:12Homegrownvendor cohort report sent 02:14Spiritusdaily summary sent · 47 vendors 04:00Bowmanavailability sync run 06:30Horizon2 inbound voicemails handled 08:15Homegrownvendor onboarding email · #28 11:23B2Bembed retrospective drafted 12:08Spiritusretreat workbook v2 published 13:45Bowman3 trips booked through site 14:30Horizonmonthly route plan generated 15:12Homegrownvendor cohort report sent
Operating today, in production —
Spiritus Bowman Fly Fishing Horizon Hygiene Homegrown + confidential B2B
002 — The Thesis

A note on the new wiring.

Software used to be a product you bought. A line item. A logo on a slide. That era is closing.

Mid-market companies are sitting on the biggest unfair advantage of the decade — and most of them can't reach it. Leadership knows AI is the wedge that captures market share from larger, slower competitors. But the team is stuck in the day-to-day. There's no one inside the org chart whose job is "champion the AI systems that move us faster than the competition."

That's the role I play. I come alongside leadership and build the systems that compound growth across every area of the business — sales, marketing, ops, customer support — in your highest-impact lanes first. Not advice. Not a deck. Production systems, shipping in week one.

A team of four with the right wiring outproduces a team of forty without it. Not because the four are exceptional. Because the process overhead disappeared. The translation layer between strategy and execution — the meetings, the handoffs, the slow build cycles — it just isn't there anymore. I'm what makes that gap collapse inside your company.

The role · AI ChampionEmbedded with leadership. Building the systems that capture market share. No handholding. Just execution.
AI is no longer the product. It's the infrastructure. — The thesis, in eight words
003 — The framework, in motion

The Embedded Loop.

Three motions, repeated. Train leadership. Deploy in week one. Embed alongside the org chart — each new system layered on top makes every other one faster. The loop compounds.

Operator 5 active engagements · running
Train Deploy Embed ↗ where the operator lives
(centered, never delegated)
{ 4 system spokes
voice · email · content · data }
i. Train

Leadership gets fluent.

Sixty minutes to multi-day. I sit with you and the team. We map the highest-impact lanes — sales, marketing, ops, support — and find what's quietly costing market share three layers below the one on the deck.

Live · 64 hrs of context loaded today
ii. Deploy

First system, week one.

Production AI system shipped in week one. Not a prototype. Not a dashboard demo. Real code in the live environment, used by the team — by day seven you have the first compounding piece of wiring.

Live · ships nightly to production
iii. Embed

The flywheel compounds.

Ninety-day minimum. The team runs the live systems while I'm building the next one. Each layer makes the wiring faster. Speed up, revenue up, costs down — every sprint.

Live · 5 active

A team of four with the right wiring outproduces a team of forty without it.

— what compounds, year over year
004 — Three motions, three engagements

Train. Deploy. Embed.

i.
Train
60 min → multi-day · 1–8 people

Leadership gets fluent.

Live working session with leadership and the team. We use your real workflows, your real data, your real bottleneck. You leave knowing where AI captures market share — today, this quarter, this year.

10:04claude.session.start
10:18workflow.captured
10:42runbook.draft.v1
11:30team.fluent
ii.
Deploy
30–60 days · 1 system, shipped

First system, week one.

Production AI system in your live environment. Voice agent. Cold email at scale. Auto-CRO. Whatever the highest-impact lane needs. By day seven, code is shipping. By day thirty, the second one is too.

d-00scope.locked
d-07first.deploy.staging
d-14first.deploy.prod
d-30handoff.complete
iii.
Embed
90-day minimum · ongoing

The flywheel compounds.

I sit alongside leadership, building the next system while the team runs the last one. New AI surface area every sprint. Each layer makes the previous ones faster. Speed up, revenue up, costs down — month over month.

w-01embed.start
w-04surface.+1
w-12team.extends
wiring.compounds
005 — Time to production

Thirty days to shipped. Not twelve months to strategy.

The traditional consultant ramp peaks at month six. The embedded operator peaks at day thirty — when the system is already running in production and the team is already trained on the keys.

Embedded operator production by day 30 → then compounds
Traditional consultant first deliverable around month six
d-0 d-30 d-90 d-180
Same outcome. 150 days sooner. 5× faster to first production system
↓ ship
006 — What the first 90 days look like

Embed, week by week.

Day 0 · Discovery

Map the wiring.

Sit with the team. Walk every workflow. Find the actual bottleneck — usually three layers below the one on the deck.

Day 7 · First system

Production ships, week one.

First AI system live in your environment, used by the team. Not a prototype. Real code in the loop by day seven.

Day 30 · Compounding

Three systems layered in.

Each new system makes the previous ones faster. The team is running them in production. I'm building the next one.

Day 90+ · The flywheel

Speed up. Revenue up. Costs down.

Every system compounds. More output per hour. More qualified leads. Lower cost to serve. The wiring keeps accelerating.

007 — Engagement structure

Four ways to engage. One conversation to start.

Assess$1,500 · 2 wks
TrainFrom $4,500 · 60 min+
DeployCustom · 30–60 days
Outcome
A market-share map. Where AI hits hardest first.
Leadership fluent on AI. This week.
A production system. Live in 30 days.
An AI Champion inside the org chart. The flywheel compounds.
Format
Async + 1 working session
Live working session(s)
Full build cycle, weekly checkpoints
Embedded, weekly review, +1 system / sprint
Deliverable
Architecture brief + impact roadmap
Runbook + recordings
Live system + ops docs
Build + run + extend
Best fit
Leadership curious where to start
Mid-market teams onboarding to AI
Companies with one critical lane to ship
Mid-market companies serious about market share
Capacity
Open
Open
1 slot · Q3
2 slots · Q3
Most engagements start with the $1,500 Assess — about 1 in 3 converts to Deploy or Embed.
008 — The operator stack

The infrastructure I run on.

Production tooling I have shipped in real engagements. Not "we use Claude." Eight layers, named, live, currently deployed on at least one client today.

/operator-stack · live
execClaude Code · Opus · Sonnetlive
voiceRetell AI · ElevenLabs · Twiliolive
computeModal · Vercel · Cloudflarelive
browserPlaywright · Puppeteer · Chrome MCPlive
emailInstantly · SendGrid · Resendlive
dataApify · Airtable · GA4live
visionClaude Vision · fal.ai · Geminilive
mediaRemotion · FFmpeg · ElevenLabslive
$ tail -f /var/log/operator.log
↗ ships nightly
009 — Evidence

Bowman Fly Fishing.

An outfitter that ran on word-of-mouth and a phone.

━━▶
In a single season · revenue lift
Situation
A guide running ten miles of private water. Phone-based booking. No site, no email list, no way for new anglers to find or trust him.
Move
Built and shipped a booking site with live availability, integrated payments, automated SMS confirmations, and a review-capture loop. Thirty days to first paid booking through the site.
Result
4× revenue in one season. Bookings now 80% inbound through the site. Daniel runs the wiring himself; I check in monthly.
Principle
A small operator with the right wiring outscales a small operator with a phone, every season.
Wiring shipped · architecture
3 sources → 1 wiring layer → 3 production systems · captured 2026-05-07
{ 4× in one season }
I'm a fly fishing guide. He turned that into a business. Daniel Bowman, Bowman Fly Fishing ↗

The same wiring that 4×'d a fly fishing guide compounds the same way at $50M ARR. Different scale, same multiplier — and at mid-market scale, the absolute dollars are an order of magnitude bigger.

The companies that win the next decade will have an AI Champion inside the org chart. Not a vendor. Not a deck. An operator.

— the role mid-market is missing
010 — Operating today, in production

Five active engagements. Different verticals. Same wiring.

↗ same operator
different verticals
{ 4 systems
shared underneath }
VOICE EMAIL CONTENT DATA AI CHAMPION — me Spiritus COACHING Confidential B2B · MID-MARKET Bowman OUTFITTER HORIZON SERVICES Homegrown SAAS · OWN
SPIRITUS daily summary engine, retreat workbook
▸ click any node to see what's wired
5 verticals · 4 system spokes · 1 operator
the wiring is the moat, not the verticals
011 — By the numbers, this year

Live infrastructure. Real numbers. Running tonight.

+1 just now
Trailing 12 months · pulled live
0

Emails sent autonomously through systems I've shipped. Across Spiritus, Bowman, Horizon, and the SprayEngine pipeline.

Articles · Webflow CMS
0+
Programmatic SEO articles, published live to client Webflow sites
Leads contacted · cold pipeline
0
Across Homegrown + SprayEngine
Uptime · last 90 days
0
Across all production deployments
↻ Numbers refresh nightly from /api/stats · Webflow + Instantly + Retell
↘ refreshes every 30s
012 — What's running, this minute

The systems are live. Every dot is a real process.

99.94% uptime · 90 days
running
Spiritus Coaching
daily summary engine
last action 12s ago shipped142
running
Bowman Outfitter
3 trips booked today
last action 44s ago shipped47
running
HORIZON Services
2 voicemails handled
last action 1m 18s ago shipped186
processing
Homegrown SaaS · own product
vendor onboarding email · #28 sent
last action 6s ago shipped this week412
running
Confidential B2B
embed retrospective drafted
last action 3m 21s ago tierembed
Live · pulled from Modal · refreshed every 30s
Atlanta GA · Operator on call · add a dashboard for your team →
013 — A few clarifications

What this is not.

  • Not a generic AI strategy retainer. Not advice billed by the hour.
  • Not a deck. Not a roadmap you'll iterate on for six months while competitors ship.
  • Not me writing your prompts for you. Not a wrapper around ChatGPT.
  • Not a tool I'm trying to sell you. The shipped systems are the deliverable.
  • Not for solo founders or pre-revenue startups. Mid-market with an actual P&L.
  • Not for companies that aren't sure where they're losing market share. Run the Assess first →
014 — Operating principles

A working memory.

Seven sentences. Pinned above the desk. They survive every framework, every cycle, every cold-start of a new engagement.

  1. i.

    Knowledge is code. Code persists. People rotate.

  2. ii.

    Ship in week one or do not ship.

  3. iii.

    The deck is not the deliverable. The system is.

  4. iv.

    Build alongside the team — not above them, not instead of them.

  5. v.

    Strategy is free. Deploy is the moat.

  6. vi.

    Operators compound. Vendors expire.

  7. vii.

    The flywheel is the deliverable.

If a competitor is shipping AI faster than your team, we should talk.

— what the engagement opens with
Evan Knox
015 — How to start

Three steps. No intake form.

i.

Send a paragraph.

What lane you're losing market share in. What's stuck. No intake forms, no qualification questions.

ii.

I respond in twenty-four hours.

With a read on whether AI Champion is the right fit, and which engagement to start with.

iii.

We talk for thirty minutes.

Either we lock the engagement or I send you to a better-fit operator. Both happen often.

Email Responsewithin 24 hours · Mon–Fri LocatedAtlanta GA · embedded with US/EU teams Background5 exits across SaaS · ecommerce · services
Issue 01 · Summer 2026 · drafting

Get the essay when it ships.

Long-form notes on the wiring. About one a quarter. No spam, no funnels, no sequences. Issue 01: AI as Infrastructure — why software stopped being the product.

017 — Common questions

Before you ask.

What does "AI Champion" actually mean? +
The role inside your org chart that mid-market companies don't have yet — the operator whose only job is to ship the AI systems that capture market share. I'm in your Slack, in your weekly leadership meetings, and in your repos. Building. Not advising. Typically embedded with two companies at a time.
Why mid-market specifically? +
Mid-market is where the leverage is highest right now. Big enough to have real revenue and real workflows worth automating. Small enough that one operator with the right systems can move the needle company-wide in a quarter. Solo founders don't have the infrastructure yet. Enterprises have politics. Mid-market is the gap.
How does a 30-day production timeline actually work? +
Day 0–3: scope locked, environments stood up. Day 4–7: first system to staging. Day 7: first system in production. Day 7–30: second and third systems layered in. Each new system makes the previous ones faster. The aggressive part isn't the building — it's the scope discipline. We ship the highest-impact lane first, fully, before touching the next one.
Do you take equity? +
Sometimes — for embed engagements with companies I'd consider operating at full-time. Default is cash. Equity conversations happen after we've shipped one full deploy together and seen the flywheel start to turn.
What stack do you bring vs. what stays? +
I bring the stack listed in the operator stack section above. Your team owns the systems we ship — no vendor lock-in to me. If your company has standardized on different tooling, I adapt. The wiring matters more than which specific service runs each layer.
Where are you located? +
Atlanta, Georgia. I work async + a few synchronous hours daily during embedded engagements. Travel for kickoffs and quarterly leadership reviews is included.
What's the smallest engagement you take? +
$1,500 Assess. Two weeks. You get a market-share map showing exactly where AI hits hardest first inside your business. About one in three Assess engagements converts to Deploy or Embed.
Why "embedded" and not "fractional"? +
A fractional executive optimizes the org chart you already have. An AI Champion rebuilds the wiring underneath it so every future hire inherits leverage instead of maintenance. Different unit of work. Different durability. Fractional roles end with their hours; embedded engagements end with a flywheel that compounds without me on the calendar.
Do I need an internal AI lead before working with you? +
No. The point of the engagement is that I am the AI lead during the embed window — building, shipping, and training the team in parallel. By the time you hire a full-time AI lead (most companies eventually do), the wiring is already there and they inherit a working flywheel instead of a blank sheet.