Workshops teach. Embedding ships.
A WORKSHOP
Great when your team needs to learn how — a week of structured practice, then they take it from there.
- I run the room, your team builds
- Fixed format, fixed dates
- You leave with the method
EMBEDDING
Right when you need the thing built — I join the team as an operator and we ship a real, scoped problem together.
- I build alongside your people
- Scoped to your actual problem
- You leave with working software and the method
How an embed works
01 · SCOPE
A fit call, then a one-pager
We get on a short call, find the one problem worth shipping, and I come back with a one-page plan: what we'll build, the timebox, and the price. No SOW theatre.
02 · BUILD
I embed and we ship daily
I work inside your stack and rituals — committing, shipping, and demoing as we go. Your team sees exactly how the thing gets made, not just the result.
03 · HAND BACK
You own it after I leave
You're left with working software in production, a clear handover, and a team that can keep building on it. No black box, no dependency on me.
A GOOD FIT IF
- There's a real product problem that keeps slipping the roadmap
- You'd rather see it shipped than added to a backlog
- Your team can give an embed access and a few hours a week
- You want the speed of one operator, not a six-week agency ramp
PROBABLY NOT IF
- You want a body to staff a long-term roadmap (hire for that)
- The work can't be scoped to a few weeks of shipping
- You only need a talk or a training day — that's a workshop