Team transformation
Your team using AI on real work, every Tuesday afternoon.
We stay until it sticks. Picking the tools, building the first AI workflow in your stack, training your people to extend it after we leave.
What you get
Four outcomes. All of them load-bearing. Skip any one and the rest stops compounding.
A working workflow on your stack
Not a recommendation, not a vendor shortlist. We ship the first AI workflow on the tools you already pay for.
Hands sharp enough to extend it
Your team learns by using it, editing it, and shipping the next version. They leave the engagement with a skill, not a transcript.
Two or three internal champions
We pick them with you, train them deep, and hand off cleanly. The ones who carry the workflow forward after we leave.
Steady follow-up that makes it stick
Newsletter, office hours, the slow work that turns a pilot into the way things are done now.
How it goes
The four moves, in order. Each one earns the next.
Phase 01
Discover
We sit in the day-to-day until we know how your team actually works. Real shadowing, not a workshop. The output is a short brief on what to build first and why.
Phase 02
Pilot
One real workflow, end to end. Built in your stack, used by your team, refined every few days from what we hear in the work. We ship the thing people use on a Tuesday afternoon.
Phase 03
Champions
We find two or three people inside who'll carry this past us. They learn to edit prompts, read the agent loop, and ship the next version without calling us.
Phase 04
Embed
We stay through adoption. A short newsletter on what's changing in the space, office hours for the questions that come up around month two, and the steady work that makes pilot-to-habit actually happen.
What lands on your desk
Real artifacts from the engagement, not slideware.
What this typically produces
Honest hedged numbers from past engagements. Yours will differ; we'll set realistic targets in discovery.
What it costs
Fixed-fee pilot, scoped during discovery. No surprises, no per-seat math, no scope-creep invoices.
Scale phase is monthly, sized to your team. If the pilot doesn't earn its keep in four weeks, we don't scale it. The pilot is the cheap part on purpose.
Who it's for
The right fit, both ways.
When we say yes
- Leadership is in the room.
- You have a workflow that hurts.
- Your team is curious, not scared.
- You're investing in adoption.
When we politely say no
- You want a tool demo, not a team change.
- You want a deck for the board, not a working workflow.
- You want fast, not lasting.
- AI is being delegated to a VP nobody listens to.
Who you'll work with
A small team, operator-grade. The same people who run discovery run pilot and embed. You won't be handed off to a junior consultant in month two. We work with one team at a time per phase. The output of the work is owned by you.
Questions worth asking
How much does it cost?
Fixed-fee pilot, scoped after discovery. Scale phase is monthly. Most engagements concentrate cost in the first three months when the workflow is being built; the rest is steady follow-up.
How big does our team need to be?
Five to two hundred is the comfortable range. Smaller and there's no team to transform yet. Larger and we'd want to scope which team we're embedding with first.
Do we have to switch AI vendors?
No. We work inside the stack you already have. If we recommend switching something, we'll tell you why and what the migration costs.
What about our data?
Stays with you. We work inside your tools and accounts, not ours. No data leaves your perimeter, and we don't keep copies after the engagement.
What if the pilot doesn't work?
Then we don't scale it. The pilot is the cheap part of the engagement on purpose. If it doesn't earn its keep in four weeks, we say so and stop.
Remote or onsite?
Both. Discovery usually has at least one onsite week so we can shadow the real work. After that mostly remote, with periodic in-person check-ins if the workflow calls for it.
What does “embed” mean exactly?
A regular cadence after the pilot ships: weekly office hours, a short newsletter on what's changing in the space, and a check-in on the workflows we built. Usually six to twelve months, ending when your champions are clearly running it without us.
Let's see if we're a fit.
Tell us a bit about your team and the workflow that hurts. We read every note and reply ourselves.
Start the conversation