— Loading
Download a working automation JSON
Can AI answer engines cite your site?
Outreach scripts that get replies
Find the 3 workflows costing you sleep
200+ prompts, ready to ship
12-month posting plan in 60 sec
Brand voice doc in 4 steps
Runway / Pika / Sora / Veo formats
The pressure to "do something with AI" is real, but nobody's mapped which of your workflows it moves and which it just decorates. So you guess, buy tools on a hunch, and can't tell six months later whether any of it earned its keep.
ChatGPT, Claude, Gemini, Copilot, a dozen wrapper apps. Every person picked a different one, prompts differently, and gets a different result. Nothing compounds because there's no shared playbook — just scattered individual habits that fade by Friday.
A generic vendor ran a four-hour webinar on "intro to prompting," everyone nodded, and three weeks later the team is back to the old way. Courses teach the tool. They don't teach your ops manager how to clear her inbox faster on Tuesday.
Someone's already pasting customer data into a free chatbot with no retention controls and no policy. You don't have an AI problem — you have an ungoverned one, and the first you'll hear of it might be a breach, not a memo.
A short, ranked plan: the three workflows where AI pays off now, the ones to wait on, and the ones to never automate. Prioritised by hours saved, not hype. You stop guessing and start with the move that actually returns.
Hands-on sessions tied to your people's real work — their inbox, their contact list, their actual Tuesday — until each person ships a workflow they'll use tomorrow. Enablement, not entertainment. The skill stays after I leave.
One place every role pulls from: role-specific playbooks, a curated prompt library, and voice profiles for company comms. Good prompts get reused instead of reinvented, so output stops depending on who's at the keyboard.
A written line on what data can and can't go into which tool, which tiers are sanctioned, and the rules where GDPR or HIPAA apply. Shadow AI becomes governed AI — your team sleeps better, and so does your legal team.
I interview your team leads and shadow the key roles for a half-day each, mapping the five tasks per role where AI fits and the five where it doesn't. This is where the clarity comes from — real workflows, not a generic maturity survey. (Week 1)
You get the plan: ranked priorities by hours saved, the role-specific playbooks, a prompt library, and a written AI policy. Short enough to read in an afternoon, specific enough to act on Monday. (Week 1-2)
Live workshops in small groups on your real work — every session ends with a shipped workflow — then 30 days of office hours and adoption checks so the habit forms. I hold the line past the point where generic training quits. (Week 2-4)
After role-specific training, a team runs its own AI workflows internally — sales drafting, ops triage, founder review — without me in the loop. Adoption tends to hold past day 30 because the program is real work plus accountability, where generic vendor webinars stall out in the first few weeks.
90-min team training + playbook.
Multi-session program + tooling setup.
Fractional AI lead for the team.
I send fixed scope back within 48 hours of your brief, so you know exactly what the audit, roadmap, and workshops cover before any money moves. Every engagement ships with a recorded Loom handover and a 14-day window where I fix anything in the playbooks or policy that doesn't match how your team actually works.
30-min discovery call. I'll find where AI actually moves your numbers, tell you straight where it doesn't, and have fixed scope back in 48 hours.
Start the briefSame fixed-scope build, delivered remotely to any US state. The per-state breakdown is being rewritten — it carried first-party performance figures we could not substantiate, so it is withheld rather than shipped unverified. Ask on the call and you will get the local detail directly.
Delivered in all 48 states