The pod
A pod is put together for the project it’s on.
Three to eight roles depending on the service, a cadence you can plan against, and one lead who runs it from the first call through delivery.
What is
What a pod is
A working unit assembled for one project
The roles that project needs, a rhythm your company can plan against, and one lead who answers for the result. What you deal with is the unit — one point of contact, one place the work comes from, and one place the accountability sits. The composition is set by role, so the unit survives any one person leaving it.
Composition by role
What the project needs, agreed before it starts.
A cadence you can plan around
Fixed at the start, in the same document as the scope.
One lead
Your point of contact from the first call through delivery, and the one who answers for the result.
The composition
How a pod gets put together
The composition comes out of the mapping
Which disciplines the work touches, which parts need depth, and which need somebody who works on that one thing all day. A pod that has to migrate a system carries architecture and infrastructure; one that has to rebuild a brand carries art direction and a verbal system. Two projects in the same service rarely end up with the same pod, which is why the roles are named for each one before the work starts.
Decided against the problem.
The roles come out of the mapping, not out of who’s free.
Specialists for the parts that need them
Depth where the work is hard, not coverage everywhere
Written down before it starts
The composition is named for each project
Custom software
Architecture
Engineering
QA & Integration
Product and interface design
Infraestructure and deployment
Process automation
Lead
Process mapping
Integrations
Data
QA
AI agents
Lead
Conversation design
Knowledge base
Integrations
Conversation QA
Branding
Lead
Brand strategy
Art direction
Identity design
Verbal system
Motion identity
Web design
Lead
Research and UX
Interface design
Front-end
Content
Accessibility review
GTM (Go to market)
Lead
Market and competitive research
Entry strategy
Messaging and positioning
What it ask
What it asks of your team
Three things, agreed at the start. Access to the systems and to whoever knows why they were built the way they were. Decisions at the points where the decision is yours, which reach you with the options and the tradeoffs already worked out. And one person at your company who can make those calls without carrying each one through three approvals.
The pod holds its own planning and review, so status and coordination stay on our side. Your team spends the rest of its week on its own work.
Phases
The same three phases, whatever the service
What changes between one service and another is which roles are on the pod. The sequence holds for all six.
The Pod
You see the work as it goes
The pod delivers in pieces at a fixed rhythm, and each one comes with what changed and what it needs from your side. Review happens on the piece in front of you, on the systems where it will actually run, so a decision about direction gets made while the work behind it is still small. Nothing waits for a single reveal at the end.
On the call we go over the cadence and where your decisions land.
The Pod
What you keep
Process automation
The integrations, plus the map of the process they run on.
AI agents
This one works differently, and we say so before you start: the agent runs on a platform that’s operated month to month, so it stops when the operation does.
Branding
The source files, the system, and the guidelines for applying it.
Web design
The site and its design system.
GTM (Go to market)
The research, the positioning and the messaging built on it.
How long
How long a pod stays
Some pods finish what they were assembled for and close there. Others stay while the roadmap keeps needing them, month to month, and a pod that renews knows your company better each time — the mapping is already done and the composition is already proven on your systems. Which one yours turns out to be gets decided once we understand the problem.
Twenty minutes
Twenty minutes to see what a pod for this would look like.
Bring the problem. You leave the call knowing which roles it needs and how we’d go at it, and if it isn’t work we should take, we say so there.
Who We Work With
This is a fit
If most of this describes your company, there's something concrete to talk about on the first call.
You already have traction: paying users, real revenue, or recent funding
You can name what the problem is costing you
You can work in milestones
You want one partner accountable for the result
You're growing and something structural stopped keeping up