Save the team you keep rebuilding

Six · 5 min read · August 13, 2026

Save the team you keep rebuilding

Say you run a small agency, and every new client starts the same way. Before anyone talks strategy, you want a read on the client's market, an audit of what they already publish and a first content plan they can react to.

You've done this enough times to know which atoms you want on it. There's the one you hired for market research, the one who audits a client's site and the writer whose first drafts you've been happy with. The last kickoff went well with that group, so you'd like to start the next one with them too.

But every time a client signs, someone has to remember who was on the last kickoff, find those atoms again and put the group back together before the work can start. If the person who remembers is busy, the kickoff starts with whoever gets picked first, and nobody chose that group on purpose.

A pod gives that choice somewhere to live. In Supanova, you can group your atoms into a named pod and hand the pod the work. When the next client signs, you start from the group you already picked.

That's what a pod saves: the starting group. The kickoff itself still runs as a project, and that's where the plan and your review happen.

What a pod keeps

Go back to the kickoff. What you want to hold on to is the decision you made after the last one: these are the atoms you want in the room when a new client arrives.

A pod keeps that decision under a name you'll recognize, something like "New client kickoff." It stays in your workspace after the project ends, so it's there when the next client signs.

A saved pod answers three questions for whoever picks it up next: who belongs in the group, whether it's settled enough to use and what work it's for. You answer a fourth each time you hand it work: is this your preferred group, or must these atoms be included?

Ready means the group is set, not that the work is staffed

A pod can sit as a draft while you're still deciding who belongs in it. Once the group is settled, you mark it ready, and a ready pod is one you can hand work to. When the work stops coming around, say you stop running kickoffs that way, you archive it.

"Ready" is easy to read as more than it is. It means the group is in place. It doesn't mean every atom in it will work on the kickoff at the same time, and it doesn't mean the work will come back faster or better because it went to a pod.

Say how firmly you mean it

When you hand a ready pod a piece of work, you also say how firmly you mean it. Either the pod is your preferred group for the work, or its atoms must be included.

For the kickoff, the difference is practical. If the pod is simply where you'd like to start and you'd be fine with another capable group, preferred fits. If the atoms in the pod worked on this client's pitch and you want them on the kickoff too, must include is the stronger instruction.

Take both literally. They record who you want. They don't say what gets done first, what needs your review or what happens when the client changes the brief halfway through. Those questions belong to the project you hand the pod.

Where the kickoff runs

Once a group has a name, it's easy to expect it to run the kickoff by itself: split up the work, decide who does each part and check what comes back.

A pod doesn't do that part. It holds the group. The plan and the check-ins happen in the project you hand it, and you choose how often your workforce checks in there: every step, every task, or once per project. If you choose once per project, you green-light the kickoff and your team runs it end to end. The finished work comes back for your review, and nothing ships without you.

That split is easiest to forget when things go well. If the last three kickoffs were good, it's natural to credit the group. But the group was only where the work started. The kickoffs went well because you said what each one should produce, read the site audit before it went to the client and caught the content plan that missed the brief. That review happened in the project. Keep it there, even when the group feels proven.

Save a group you'd pick again

The most useful pod isn't every atom you might ever need. It's the group you'd honestly choose again for one kind of work you start often.

The kickoff is a good fit because it comes around with every new client and starts the same way each time. A one-off rebrand for a single client probably isn't. You'd be saving a group you may never use again, and the next person who sees it in the workspace won't know why it's there.

Even with a good pod, each kickoff starts with one decision that's still yours: whether this client needs the usual group, or a different research atom because their market is unfamiliar.

Questions to ask before you save a pod

  1. What work is this group for? If the answer is "everything," it's too broad to help. "New client kickoff" is an answer. "Marketing" isn't.
  2. Who chose these atoms, and why? A pod should hold a choice someone can explain. If nobody remembers why the writer is in the kickoff pod, sort that out before the next client signs.
  3. What would make this group wrong for a particular client? Name the exception before you need it, so whoever starts the next kickoff knows when to change the group.
  4. When you hand it work, do you mean preferred or must include? If it matters that these exact atoms are on the kickoff, it's must include.
  5. When you hand it a kickoff, how often should your team check in with you there? The pod sets who starts, and the project carries the rest.

If you can't answer these yet, leave the pod as a draft.

Repeat the setup. Keep the judgment.

A pod takes one chore off every kickoff. When a client signs, nobody has to remember who was on the last one and put the group back together. You start from the atoms you chose.

The pod doesn't know the client changed the brief. It doesn't know this client needs a different research atom, or whether the content plan is good enough to send. You do.

Think about the work your team starts most often. Who did you put on it last time, and would you choose them again? If the answer is yes, that's a pod worth saving. You can set one up at supanova.team.

Sources

atomsAI agent teamsTeam DesignAutonomous OperationsPods