A Value-First Guide to Surviving the SaaSpocalypse

Part II — Context

Chapter 5

The Four Unified Views


Not features to implement. Conditions to achieve.

A feature is something a vendor sells you. A condition is something your organization becomes.

The beliefs underneath

Before the four conditions, it's worth naming the beliefs that shape how we build them. The Value-First approach rests on Five Core Beliefs. Each one is a deliberate turn away from a habit of industrial-age business, and each is written as "this over that." In canon's names, with the one sentence that defines each:

  • Natural Value Flow over Artificial Control. "Value exists and wants to flow naturally through human systems, independent of our efforts to control it."
  • Empowerment over Learned Helplessness. "Organizations thrive when people are empowered to create and share value naturally rather than waiting for permission or instruction."
  • Wholeness over Fragmentation. "Value multiplies through connection rather than division."
  • AI-Human Partnership over Replacement. "AI should multiply human capability, not replace it."
  • Emergence over Predictability. "Value creation thrives through continuous adaptation and growth."

They lean on each other. An organization that lets value flow also builds people's capability. An organization committed to wholeness creates the conditions for people and AI to work as partners. An organization that keeps adapting is one whose context keeps adding up. The four views that follow are what these beliefs look like when you build them. The Value Creation Protocol teaches the beliefs one at a time.

If context is missing, how do you build it?

Not by collecting more data. You already have too much, scattered across too many systems. Not by buying a tool; that's how you got here. Not by hiring a "Chief Context Officer." Adding a role to manage the problem is the people version of adding a tool to manage too many tools.

Building context means reaching specific conditions: business outcomes that change how information moves, how decisions get made and how your organization understands the people it serves. Four of them, specifically.

These are the Four Unified Views.

Not features. Conditions.

Before the definitions, be clear about what these are and aren't. The methodology's own reference puts it this way: the Four Unified Views are "not features to implement, but conditions to achieve."

You can buy a "360-degree customer view" feature from a dozen vendors. That doesn't mean you have a Unified Customer View. The view exists when the people who serve a relationship can see what they need, in the place they already work, without switching tools or asking for a report. The feature is a part. The condition is the change.

Think of it like health. A gym membership is a feature. Being fit is a condition. You can buy the membership without reaching the condition, and you can reach the condition by many different routes. What matters is the outcome, not the purchase.

One more thing the reference says that's worth holding onto: "A unified view is assembled across systems for the person using it; it is not a claim that one system holds all the data."

Here are the four, in canon's words. Each has a one-line definition, and each is paired with one of the four Value Cornerstones: the one it answers to.

The Unified Customer View

"Every relationship signal in one place." Its Cornerstone is Value for the Customer.

The plain test the methodology gives for it is a single question: "is everything we know to be true about this person here?" It covers every relationship that can create value, not only customers. The people who serve a relationship see the context they need for the decision in front of them, in the place they already work. Not a separate dashboard to check. Not a report to request.

Just in case. Your salesperson walks into a renewal, and the customer brings up a support problem. The salesperson has never seen it; it's in the support system. The customer reads the blank look and thinks, "They don't care about my problems." Trust slips. The conversation turns into a negotiation.

Just in time. Your salesperson opens with: "I want to make sure the integration problem from last month is fully sorted. I saw it was fixed." The customer thinks, "They pay attention." The renewal isn't a negotiation. It's the next step in a relationship.

The change, in the reference's words: from "a view rebuilt by hand before every board meeting, or carried in one person's head" to "a standing view the people who serve the relationship trust and work in."

The Unified Revenue View

"Shared clarity on the whole commercial picture, from the first signal of demand through every promise made, kept and paid, to what comes next." Its Cornerstone is Value for the Company.

If the Customer View shows you who your customers are and what's going on in each relationship, the Revenue View shows you where value is moving, where it's stuck and where it's at risk. It holds the whole commercial picture: the early demand and the conversations before anything is booked, and then delivery, payment, further orders and renewals after.

What it tracks is the promise, and a promise is often much more than a payment. The reference holds every promise through four statuses at once, "booked," "billed," "earned" and "paid," and it's careful to say they aren't steps in a line. It also says something I'd underline: money is read as the wake of value. It's recorded after the value, and it's never the thing the view steers by.

Just in case. First week of the quarter. Sales has one number. Finance has another. Customer success says three renewals are at risk that sales hasn't flagged. The forecast meeting becomes an argument about whose number to believe.

Just in time. Same meeting. One picture, and everyone can see how it was put together. The conversation is about what to do: these relationships are growing, those two need attention now.

The change: from "each team holds its own number, and nobody can see how they connect ('Which number are we using?')" to "one shared picture of the whole commercial relationship, from first signal through commitment, delivery and payment to what comes next."

The Unified Strategy View

"Strategic intelligence embedded where decisions happen." Its Cornerstone is Value in Context.

The first two views give you sight of customers and revenue. The third brings everything else the business knows, its market, its strategy, how it operates and what its people know, to the moment someone has to decide. It also keeps what was decided, what was tried, how it turned out and what the team learned, so the next decision starts from there instead of from scratch.

Just in case. A leader thinks manufacturing is your fastest-growing segment. The analytics team spends days pulling data from four systems. The slide deck arrives after the decision was already made on instinct. The intelligence shows up after the decision has moved on.

Just in time. Same question, asked in plain language, answered while it still matters: manufacturing is growing in revenue, but another segment is showing the kind of engagement that has come before growth in the past. The leader adjusts the plan before deciding.

The change: from "intelligence trapped in heads, side systems and decisions nobody wrote down" to "contextual intelligence where decisions happen."

The first edition of this book called this view Unified Business Context. Our methodology renamed it the Unified Strategy View in October 2026, and this edition uses the new name.

The Unified Operations View

"People resourced with capability, context and safety; each person owns their process in the shared system; AI carries the coordination; and delivery is visible to every team." Its Cornerstone is Value for the Community.

This is where the context becomes everyday work: people and AI working together, each doing what they do best. The reference describes it as "teams amplified by AI partnership, not replaced by automation," where "capability grows faster than headcount, so the people you have can do work they could not do before." It also holds how the work felt to the people doing it, kept alongside what the work produced.

Just in case. Your team is talented, committed and drowning. Support spends most of its time on routine questions. Sales spends half the day getting ready for conversations. When growth comes, the only answer is to hire. The organization grows in headcount but not in capability.

Just in time. Same team, different leverage. Routine questions are handled by AI that has the full context. Preparation is done before anyone sits down. The team spends its time on relationships, the work that moves things. Growth comes and the team handles it. Not through heroics. Through leverage.

The change: from "linear scaling requiring proportional hiring" to "capability multiplication through human-AI partnership."

The first edition called this view Unified Team Enablement. It's the Unified Operations View now, and it's never to be confused with any software product of a similar name. The views are outcomes, not features.

How the views lean on each other

The first edition of this book said the four views had to be built strictly in order, one, two, three, four, and that each had to be finished before the next could start. That was too strict, and our own definitions now say so.

Here's what the methodology says instead. "Customer understanding comes first wherever possible, because every other view leans on it. No view waits for the one before it to be complete: another view can begin as soon as the supporting context it needs is usable." What lets the next view begin isn't a finished earlier view. It's a specific signal that the context it needs is ready. For the Revenue View, that signal is that the people and organizations in each promise sit on one joined record the people serving them trust.

The views draw on each other. The Strategy View, in particular, "arrives largely from the first two views": once the Customer View and the Revenue View stand side by side, most of the context a decision needs is already there. The reference puts it in shorthand: "1 + 2 = 3."

And building is different from talking. A conversation about the views can start at whichever one answers the problem the person in front of you has.

You also don't measure a view by whether something was built. The methodology reads each view through three milestones, "Foundation → Capability → Multiplication," and reads them "from what people do with the view, never from whether something has been built." Foundation is when people agree what the view should show and can reach it. Capability is when they use it, again and again, to do their work. Multiplication is when they improve it, or help others carry it, without anyone pushing.

How long does that take? It depends on readiness, not on a calendar. Some organizations start with good data and reach the first milestones quickly. Others are starting from deep fragmentation. Each milestone is reached when its signal shows up, not when a date arrives.

An organization that had built these views before February would not have been scrambling. Its context would be unified, its intelligence within reach, its teams already working with AI. When the market panicked, it would have had the architecture that makes panic unnecessary.

An organization that was scrambling is likely one that looks at the four views and finds it hasn't reached the first milestone on the first one.

Both can get there. The Value Creation Protocol teaches the four views for the desk, with the signs and the moves for each, in its chapter on the Four Unified Views. But first it's worth seeing why context built this way is more than better visibility. It's the one advantage that's hard to copy.

Back to contents