A Value-First Guide to Surviving the SaaSpocalypse

Part III — Architecture

Chapter 7

The Architecture


What does a platform look like when it's built to be an operating system? Not a CRM you bolt AI onto. An operating system for people and AI working together.

Parts I and II were about understanding: what the SaaSpocalypse was, why context is the advantage that lasts, and which conditions your organization needs to reach. But understanding without architecture is philosophy, and philosophy doesn't survive contact with operations.

This chapter gets concrete. What does a platform look like when it's built as an operating system: one environment where people and AI agents share context, coordinate work and create value together?

The principles here don't depend on any one vendor. We build on HubSpot, run as what our methodology calls a Customer Value Platform: "a unified business system that enables organizations to recognize, create, deliver, and multiply customer value across all functions — replacing fragmented tool stacks with coherent operational capability." But the principles apply to any platform that can bring context together and support AI working inside it. The details change from platform to platform. The structural requirements don't.

Five layers

The model we use describes any organization as five layers, stacked from the bottom up. In canon's words, the five layers are "the five layers of an AI-Native Operating System." The same five layers are present in every organization. What changes isn't which layers exist. It's whether they work together.

Here they are, with the one-line description our methodology gives each.

  • Layer 1: Data, Identity, Context. "Sources of truth, memory."
  • Layer 2: Customer Value Model. "What the data means."
  • Layer 3: Intelligence. "Who has context + capability."
  • Layer 4: Trust. "Why the work can be trusted."
  • Layer 5: Interface. "Every surface where humans meet you."

The stack reads from the bottom up. Each layer earns the weight of the one above it. The AI-Native Shift walks the Five-Layer Model in depth, as the map of the change. Here's the short version, told as the architecture underneath the views.

Layer 1: Data, Identity, Context

The foundation. This is where the record of who your customers are lives: how they're related to each other, and every interaction they've had with you. Not data scattered across databases. Not the same person entered three times in three systems. One foundation every other layer reads from.

Without this layer, nothing else works. AI agents working on inconsistent data give inconsistent answers. Dashboards built on duplicate records give misleading reports. This layer isn't exciting. It's essential.

In practice it means one record for each person, however they first showed up. The person who downloaded a guide, the person who opened a support ticket and the person who received an invoice: if they're the same human, they're one record. It also means the relationships, not just "who are our contacts?" but how people relate to companies, to each other, to what they've bought and to the conversations they've had.

The layer's name is broader than records, on purpose. In our methodology, identity also means who your organization and its brands are, and context means everything the organization knows, including what's written down outside the CRM. The canon puts the stakes plainly: "Most 'AI projects' that fail are actually Layer 1 problems wearing AI clothing."

When you take this layer seriously, expect to find your data in worse shape than you thought. Cleaning it up isn't glamorous. It's some of the most important work in the whole architecture, because every layer above inherits whatever mess this one holds.

Layer 2: Customer Value Model

This is where your understanding of how customers progress with you becomes something the platform can run on. Canon calls it "the explicit model of what creates value for your customers, for whom, and why."

In an organization still stuck in the old way, this layer is filled with internal-process words: the stages and scores a business uses to describe how it handles a relationship. In an organization that has made the shift, it holds the model each of the Four Unified Views needs, and it maps to the Value Path: eight stages that describe how people move through a relationship with you, from the first moment of learning to becoming a champion. Signals replace scoring. Readiness replaces qualification. Natural progression replaces manufactured stages.

This is where most of the architectural thinking happens. You're deciding what counts as a signal of readiness at each stage. Which signs, showing up together, tell you a person has moved from Researcher to Hand Raiser? Those aren't arbitrary definitions. They're hypotheses about your customers, and the platform can test them as the record grows.

Layer 3: Intelligence

This is where judgment lives: pattern recognition, reasoning about a situation, putting context together into a decision. Canon names two participants at this layer: "Your Humans and Your Agents."

The first edition of this book called this the Agent Layer, and that name sold it short. The layer has always existed. Every organization has always needed intelligence here. What's new is that it now runs on human and artificial intelligence together, where it used to rely on people alone.

The agents do specific jobs. Agents that prepare and share content based on what your audience is paying attention to. Agents that research an account and get a conversation ready with the whole relationship history in view. Agents that answer routine questions knowing who the person is and what they're trying to do. Agents that watch patterns and flag what would take an analyst days to find.

Same AI. Same request. Very different output, depending on whether Layers 1 and 2 are feeding Layer 3. Agents are effective because they're contextual, not because they're clever.

And the human half isn't going anywhere. The people at this layer bring what our methodology calls Human Domain Expertise: hard-won expertise, written down in a form AI can meet and multiply. The preparation work that used to keep people from their best work, assembling context from five systems before a meeting, drafting the routine message, watching hundreds of relationships for a change, goes to the agents. The judgment stays with the people.

Layer 4: Trust

The first edition of this book called this layer Orchestration. Our methodology has since named it for what it provides: trust. Canon's definition: "Trust here is transparency and control: who may do what is decided and written down, what must never happen is guarded, the work is checked before it acts, and anyone can see what was done, by whom, human or agent, and why."

It has four parts, and all four have to be deliberate: Governance, Safety, Quality and Observability. Governance keeps humans and agents aligned with the operating model: who may do what, and who approves. Safety guards against what must never happen. Quality checks the work before it acts. Observability lets anyone see what was done.

This is also the layer that moves work through the system. When a customer's pattern of engagement starts to look like ones that came before a cancellation, the system doesn't wait for a quarterly review. It brings it to someone's attention and suggests what to do. When a relationship shows signs it's ready to grow, the system doesn't wait for a calendar check-in. It tells the people who look after the account and gets the context ready.

Not every signal needs action. Some only mean something in combination. One visit to a pricing page is noise. Several visits in a week, alongside reading your material on building a business case, is a signal. This layer recognizes patterns across single events and responds at the right level.

Without it, the coordination falls on a person, usually the same person, over and over, until they leave or burn out. Canon is blunt about it: "Nobody hands real work to anyone, human or agent, until they can see who is doing it, what they can reach, and what they did."

Layer 5: Interface

Every surface where people meet you. That includes the tools your team works in, and it also includes your website, your social posts and your newsletters: every place a person outside meets your organization.

Inside, this is where people see what agents did, what the data shows and where their judgment is needed. Not a data dump. A view of what matters now: which relationships need attention, which signals have shown up, which agent actions need a look, which exceptions need a person. The default is "here's what needs your attention," not "here's all the data we have." People can still explore everything if they choose.

This is where just-in-case dashboards give way to just-in-time views. The interface protects the most precious thing a person brings to work, their attention, by keeping noise away from it and pointing it at what matters.

How the layers connect

Data flows up. Action flows down. Context informs every layer.

A new interaction comes in at Layer 1: a customer sends an email, visits a page, opens a ticket. The record updates. Layer 2 checks whether it changes where the person is on the Value Path, or whether it's a signal. At Layer 3, people and agents work the signal: researching, preparing a recommendation, drafting a reply. Layer 4 routes it to the right person or agent, checks it and keeps the record of what was done. Layer 5 puts it in front of a person when judgment is needed, or lets it go ahead when the pattern is well understood and the trust is there.

The whole sequence can happen in seconds. Not because the technology is fast, though it is, but because the context is unified. No handoff between systems. No "let me check the other system." Every layer is working from the same truth.

No single layer works alone. The intelligence layer without the data foundation makes things up. The trust layer without a customer value model routes the wrong work. The interface without the intelligence layer shows data without meaning. It's one system, and it's worth more as a whole than any of its parts.

A Monday morning inside it

A diagram is useful. Knowing what Monday morning feels like inside this architecture is more useful.

Say you work in support. A ticket comes in. Before you've read it, you can see the customer's whole history, how they've set up the product, similar tickets from the past and how the relationship has been going. An agent has drafted a reply. But you notice something the draft doesn't account for: this customer has sent three tickets in two weeks after months of quiet. The agent flagged the pattern. It can't tell you what it means. You can, because you know this kind of customer. You make the call.

None of that took switching between systems or pulling data together by hand. The architecture makes intelligent work the default instead of the exception. Chapter 13 walks a whole day of people and agents working this way.

The five layers describe the structure. But the structure needs a model: a way of understanding a person's journey with your business that replaces manufactured stages with how people actually behave. That model is the Value Path, and it's the subject of the next chapter.

Back to contents