Operations
What a Pod actually is, and when you do not need one
Plainly: what you get, what it costs you in control, and the cases where the honest answer is that you should not buy one.
2 min readNazmul Hasan
Pod is a term I use constantly, so it is worth writing down plainly rather than leaving it as branding.
The definition
A Pod is a pre-composed operations team led by a senior operator, with AI workflows built in. Specialists across customer support, community, content operations, data and admin, and automation. The client talks to one person, the Pod Operations Lead, who is accountable for the output.
The unit of sale is the team, not the seat. That distinction is the whole thing. When you buy seats you are buying labour and you still own the management problem. When you buy a Pod, the management problem is the product.
What it is not
- Not a VA agency. A VA agency sells you people and leaves you to run them.
- Not a generic BPO that sells seats and makes you write the SOPs.
- Not an AI tool wearing a services costume. Real people do the work, with AI underneath it.
What it costs you
Some control, honestly. You are not picking each individual. You are picking a standard and an accountable lead, and trusting the composition.
For founders who enjoy managing people, that trade is annoying. For founders who are managing people because nobody else will, it is the entire point.
When you should not buy one
Three cases where I say no, or say wait.
- The process does not exist yet. If the work is still being invented week to week, it cannot be handed over. Run it yourself until it has a shape, then hand over the shape.
- The volume is not there. Below a certain size, one good hire is better value than a team, and I will say so.
- The problem is actually acquisition. If the pipeline is empty, more operational capacity makes the burn worse. Fix the front of the business first.
That last one comes up more than the other two combined. Operations problems are more comfortable to work on than sales problems, so people reach for them first.
What good looks like
On the engagement that started PodFleet, a single Pod took the founder from more than forty hours a week in operations down to nine, saved eleven thousand dollars a month against the previous staffing, and cut ticket resolution time by 2.4 times.
The hours number is the one I care about. The others are consequences of it.