Two Versions of the Same Meeting
Let me describe two versions of the same meeting. Same time. Same room. Same agenda. Entirely different experiences.
In the first version, the advisor walks in and opens with: "So, where did we leave off?" The client pauses, recalibrates, and spends the first fifteen minutes re-establishing context that was already established in the last session. The advisor nods along, making notes, occasionally asking a clarification question that the client answered three weeks ago. The conversation eventually finds its footing, but by then a third of the session is gone. The client leaves feeling like something was accomplished, but also like something was wasted.
In the second version, the advisor walks in and says: "Last time, you mentioned the board meeting coming up on the 15th and the concern about how the operations team would present the integration timeline. I have been thinking about that, and I also noticed that the new VP you hired started last Monday. How is that changing the dynamic?"
The client pauses — but differently this time. Not to re-establish context, but because they feel something unexpected: they feel known. The conversation starts at depth instead of working its way there. Forty-five minutes later, the client leaves with more clarity than they have had in weeks, and a quiet certainty that this relationship is different from the others.
Same meeting. The only difference was context. And context, in my experience, is the most underestimated form of care in business.
The Problem Is Not Data
Organizations do not lack information about the people they serve. They are drowning in it. Every interaction is logged somewhere. Every email is archived. Every session has notes — scattered across Notion pages, Google Docs, email threads, chat messages, and someone's personal notebook.
The problem is not that the information does not exist. The problem is that it does not arrive at the moment it matters.
When someone sits down to prepare for a session with a person they serve, what do they actually have access to? Usually: a record in their platform that shows the commercial basics — what was purchased, when it started, who signed the contract. Maybe some notes from the last interaction, if someone remembered to write them. Maybe a task list of open items.
What they almost never have: the full arc of the relationship. How it started. What the person was worried about six months ago. What they said in that offhand comment that turned out to be the most important signal of the quarter. How their questions have evolved — from tactical to strategic, or from confident to uncertain. What their organizational dynamics look like and who the real decision-makers are.
This is not a data problem. Organizations have this information. It is a context problem — the information is scattered across systems, trapped in formats that are hard to synthesize, and organized around transactions rather than relationships.
The Four Unified Views
In Surviving the SaaSpocalypse, we describe a framework called the Four Unified Views that addresses this directly. It is not a technology solution. It is a way of thinking about what you need to know and when you need to know it.
The first view — the Unified Customer View — asks the most fundamental question: "Who is this person, really?" Not their company size, not their industry, not their contract value. Who are they? What are they trying to accomplish? What does their world look like? What pressures are they facing that they might not have articulated?
The second view — the Unified Relationship View — asks: "How is this relationship evolving?" Not as a static snapshot but as a story. Where did it start? What has changed? What moments defined it? Is it deepening or cooling? Are we engaging with the right people, or has the relationship narrowed to a single point of contact while the rest of the organization drifts away?
These two views alone — UCV and URV — would transform most organizations' ability to care for the people they serve. Not because the information is exotic, but because most organizations have never organized their knowledge around these questions.
They have organized it around transactions. Around deals. Around tickets. Around contracts. Every system is designed to answer "what did we sell?" and "what do they owe?" and "what is the open issue?" Almost none are designed to answer "who is this person and how is this relationship evolving?"
The views exist to reorient the architecture of understanding around the human, not the transaction.
What Preparation Actually Requires
I want to get practical about this, because the framework only matters if it changes behavior.
Genuine preparation for a session with someone you serve requires three things:
Continuity. What happened last time? Not just the action items — those are the surface. What was the emotional register of the conversation? Were they energized or exhausted? Did they express something that needs follow-up, even if it was not formally captured as a to-do? Continuity means the person never has to repeat themselves, never has to re-establish context, never has to wonder whether you remember who they are.
Awareness. What has changed since last time? Did they hire someone? Did they lose someone? Is there a board meeting coming up, a product launch, a budget cycle? Awareness means you walk in with the external context that shapes their world, not just the internal history of your interactions.
Anticipation. Based on everything you know — the relationship arc, the current situation, the signals you have observed — what does this person likely need from this session? Not what is on the agenda. What do they actually need? Sometimes those are the same thing. Often they are not. Anticipation means you are prepared for the conversation they need to have, not just the one that was scheduled.
Continuity. Awareness. Anticipation. Three capabilities that transform a meeting from a calendar event into an act of care.
The Five-Minute Problem
Most relationship management in business follows what I think of as the five-minute pattern. Someone has a session in fifteen minutes. They open their platform, scan the record, check the last note, glance at open tasks, and walk in. Five minutes of preparation for a sixty-minute interaction.
The five-minute pattern is not lazy. It is structural. The systems are not designed to deliver relationship context quickly and comprehensively. Notes are scattered. History is fragmented. The person preparing has to do the synthesis manually — pulling together information from multiple sources, trying to reconstruct a narrative from scattered data points — and there is simply not enough time.
So they walk in with fragments. The deal amount. The last task. A vague memory of something mentioned last time. And the first fifteen minutes of the session are spent rebuilding context that should have been available before the conversation started.
This is where architecture matters — not the technology specifically, but the intentional design of how relationship intelligence flows from capture to delivery. When the architecture is right, preparation does not require heroic effort. The context is assembled, synthesized, and available. The advisor walks in knowing the full story. The person they serve feels the difference immediately.
When the architecture is wrong — when information is trapped in systems organized around transactions instead of relationships — even the most caring person in the organization cannot overcome the structural barrier. They want to be prepared. The system will not let them.
Where AI Becomes Care
This is where I want to be honest about something. The kind of preparation I am describing — full continuity, deep awareness, genuine anticipation — is difficult for humans to maintain at scale. Not because humans lack care, but because the volume of information is genuinely overwhelming. Across many relationships, each with its own history, dynamics, and evolving context, no human can hold it all.
This is where AI stops being a buzzword and becomes something meaningful. Not AI that replaces the relationship — never that. AI that ensures the human in the relationship shows up fully prepared.
Imagine a system that reads every session synthesis, every transcript note, every interaction — and distills it into the three things you need to know before walking into the room. Not a data dump. A narrative. "Here is where this relationship stands. Here is what changed. Here is what to pay attention to."
Imagine a system that notices what you might miss: that someone's questions have shifted from tactical to strategic over the last three sessions, signaling progression. That they mentioned a concern about their operations team two months ago that was never addressed. That their engagement pattern has changed — fewer people in sessions, narrowing to just the executive sponsor — which is a sustainability signal worth watching.
Imagine a system that holds the institutional memory of every relationship so that when a team member is new, or a contributor joins for the first time, they do not start from zero. They start from understanding.
This is not theoretical. This is what well-architected AI can do right now, today, when the context architecture supports it. The technology is not the constraint. The commitment to building the architecture — to organizing information around relationships rather than transactions — that is the constraint.
As we describe in Surviving the SaaSpocalypse, AI without context is just faster noise. But AI with context — genuine, relational, human context — is care at a scale that no individual could achieve alone.
The Compound Effect of Being Known
I want to close with something I have observed consistently across many relationships, because it speaks to why this matters beyond any single interaction.
When a person feels known — genuinely known, not just tracked — something compounds over time. The first session where someone walks in prepared, they notice. The second time, they relax into it. By the third time, they start sharing things they would not normally share — not because they are asked, but because they trust that what they share will be remembered, respected, and used to help them.
This compounding effect is the most valuable thing in any professional relationship. It is also the most fragile. One session where someone walks in cold — one "so, where did we leave off?" — and the compounding resets. The person recalibrates. They share a little less. They protect a little more. The depth that was building recedes.
Context is care because it is the mechanism by which trust compounds. Every interaction that demonstrates genuine understanding reinforces the person's belief that this relationship is worth investing in. Every interaction that forces them to re-establish context signals that their investment is not being matched.
Organizations spend enormous resources trying to build trust through branding, through content, through carefully worded messaging. All of that has value. But nothing — nothing — builds trust faster than walking into a room and demonstrating that you know who someone is, you remember what matters to them, and you have thought about their situation before they had to ask.
That is context. That is care. They are the same thing.
