A Value-First Guide to Surviving the SaaSpocalypse

Part V — People

Chapter 14

Teams in an Agentic World


In September 2025 I wrote about what had changed in my own work over the previous six months. "Six months ago, I was focused on live streaming as a form of content creation, but could never take the next step to effective repurposing. Today, I'm producing two daily podcasts that wouldn't exist without the AI toolset in HubSpot." One was Wake Up! Customer Platform, with Casey Hawkins and George B. Thomas. The other was Value-First AI Daily, with Nico Lafakis.

Here's how I described who did what: "The AI-powered toolset handles transcription, editing coordination, and distribution logistics. I bring strategic insight, authentic conversation, and creative synthesis. Casey, George, and Nico contribute their unique expertise and perspectives. Together, we're creating streams of value—platform insights, AI implementation guidance, community dialogue—that none of us could produce alone."

Look at the split in that description. The AI carries the production work that had kept me from taking the next step. The people do more of what only they can do. I put it in one line then: "This isn't time-saving. This is value expansion."

That's the shape of this chapter. When the operating model moves from "Just In Case" to "Just In Time," the roles move with it. This isn't the replacement story that fills the headlines. The roles that existed to maintain industrial-age infrastructure turn into roles that create value.

What changes by function

Marketing stops being a campaign factory. AI carries content production and distribution. People put their time into original thinking, emerging themes, and the ideas that make your voice sound like you and not like everyone else's AI.

Sales stops managing a pipeline and starts carrying relationships. Signals show readiness, AI prepares the context, and the right situation reaches the right person. People build the trust that turns a transaction into a partnership, and they use judgment about whether a relationship is good for both sides.

Service stops being ticket resolution. AI handles routine questions with the full context in hand. People are freed for proactive outreach, deep problem-solving, and the kind of partnership that prevents problems instead of only fixing them.

Operations changes most of all, and it gets the next chapter to itself.

How roles change

Across every function the movement is the same.

The person who ran the reports becomes the person who says what they mean. The person who gathered data becomes the person who interprets it: context arrives on its own, and meaning still takes human understanding. The person who followed the process becomes the person who handles the exceptions, and exceptions stop being failures, because that's where new patterns turn up. And the individual contributor becomes the person running a small team of people and agents: directing the agents, reviewing their work, and deciding how far to trust it.

That last change asks for a different way of thinking about the agents themselves. On the live broadcast that launched A Value-First Summer, in June 2026, I tried to put it into words: "If you can humanize AI and give them characters and roles, the way you think about what they need to be successful dramatically changes. And when you can get there, even to the point of, hey, can we put this agent in a position to be successful?" Then the contrast: "you won't get there if it's like, oh, can you put this tool in a position to be successful? That makes no sense, right?"

In the same broadcast I put the human version of the question next to it: "what resources do we need to put this other human in a position to be successful?" It's the question a good manager has always asked about people. The new part is asking it about an agent too.

Capability multiplication

This isn't about doing more with less. It's about doing better with what you have.

The team doesn't shrink. What the team can do grows. The growth question changes from "how many people do we need to hire?" to "how much capability can we unlock in the team we already have?"

Growth comes through multiplying capability, not adding headcount in a straight line.

Chapter 5 introduced the view where this shows up, the Unified Operations View, and the change it describes, from linear scaling to capability multiplication. One line in the methodology's description of that view is worth reading twice here: "A person saying 'that felt faster' is a reported experience worth keeping; it is not, by itself, measured time saved."

That sentence is the AI Replacement Trap turned around. The trap measures what AI removed. The view keeps track of what people can now do. The Value Creation Protocol teaches the view in its chapter on the Four Unified Views.

The Three-Org Model

If the roles change this much, the org chart has to change too. The methodology's answer is the Three-Org Model:

An organizational architecture that replaces the usual tangle of functional silos with three organizations, each with one clear job: the Customer Org (everyone who creates and delivers value, owning the whole relationship with no handoffs), the Operations Org (AI-powered coordination that makes the Customer Org effective), and the Finance Org (resource stewardship and value accounting — measuring value delivered, not just revenue captured). Three orgs, one mission: maximize value created and received across every relationship.

Think about what that does for a customer. In the old shape, a customer meets marketing, then sales, then onboarding, then account management, then support, and explains themselves again at every door. In the Customer Org, one relationship is carried the whole way through, by people working with AI, and the context travels with it.

The Operations Org is what the next chapter is about. The Finance Org's job of measuring value delivered, not only revenue, is the subject of a book of its own, Value Accounting, Book 4. The model itself, with its roles and how to stand it up, is taught in The Value Creation Protocol.

Three organizations. Three functions. One mission.

Back to contents