Customer Context + Organizational Context: Why You Need Both

Imagine you're getting ready for an important customer call.

You pull up HubSpot.

You can see who the customer is, what they've purchased, recent sales and service activity, emails, meetings, open tickets, and where they are in the customer lifecycle.

You've got a pretty good picture of the customer.

Then you need to answer a different set of questions.

• Why did we originally recommend this approach?

• What did the implementation team learn six months ago?

• Why did we make an exception to our normal process?

• What's our current process for handling this situation?

• Has another team dealt with something similar before?

• Those answers probably aren't sitting neatly in the customer record.

They might live in documentation. Meeting notes. A project retrospective. A Slack conversation. Or, everyone's favorite knowledge-management system: the memory of whichever employee happened to be there.

Knowing the customer isn't the same as knowing everything your organization needs to serve them well.

You need customer context.

You also need organizational context.

At media junction, we've spent nearly 30 years helping companies connect their websites, CRM, data, marketing, sales, service, and technology. As our work has expanded into organizational memory and AI, we've become increasingly interested in what happens when you connect two different types of business context.

For us, HubSpot and Notion provide a useful way to think about it.

HubSpot helps you know the customer. Notion helps you remember how to serve them.

Bring those two forms of context together, and you start creating something much more useful: shared context.

What is shared context?

Shared context is the customer and organizational knowledge people and AI need to understand what's happening, why it matters, and what should happen next.

We can break that into two parts.

Customer context helps you understand the person or company you're serving. Who are they? What have they done? What have they told you? Where are they in their journey? What's happening in the relationship right now?

Organizational context helps you understand your own business. How do we handle this? Why do we do it that way? What have we tried before? What did we learn? What should we remember?

Put them together:

Customer context + organizational context = shared context.

And the distinction matters because those two types of information don't always belong in the same system.

That's not necessarily a problem.

The problem is when the context remains so disconnected that the people—or AI—trying to do the work can't bring the two sides together.

How does HubSpot provide customer context?

HubSpot provides customer context by connecting customer data and interactions around a shared customer record.

Calling HubSpot a CRM isn't wrong, but it doesn't fully describe what the platform has become.

HubSpot describes its Smart CRM as a shared data layer and system of record connecting its broader customer platform. It brings together customer data that might otherwise live across disparate sources and supports marketing, sales, service, and other customer-facing activity.

HubSpot's overview of its customer platform and Smart CRM explains how those pieces connect.

The important part for this conversation isn't the feature list.

It's the questions that customer context can help your team answer.

Who is this customer?

Contacts, companies, associations, properties, segments, and other structured CRM data establish the customer record.

What's happened in the relationship?

Sales activity, emails, meetings, marketing engagement, service interactions, tickets, and other activities help build a timeline.

Instead of every department holding its own version of the customer, teams can work from a more consistent history.

Where are they now?

Lifecycle stages, deal stages, ticket statuses, ownership, and other structured data help employees understand what's currently happening.

That matters because customer context isn't only historical.

It helps determine what should happen next.

What should we do next?

Customer data can trigger workflows, handoffs, follow-ups, nurture, sales activity, service processes, and other actions.

That's where HubSpot becomes more than a database.

Customer context becomes customer action.

Your CRM can tell a salesperson this prospect has already downloaded three resources and spoken to someone on the team.

It can tell service that this longtime customer has an open issue.

It can tell marketing that someone has moved into a different lifecycle stage.

It gives your people—and increasingly AI—a structured view of the customer relationship.

But it still doesn't know everything your organization knows.

And it shouldn't have to.

How does Notion provide organizational context?

Notion can provide organizational context by preserving the decisions, processes, standards, lessons, history, and internal knowledge people need to understand how the organization works.

That's a different job.

HubSpot might tell you a customer has an open ticket.

Organizational context helps answer:

• How do we handle this kind of issue?

• Have we encountered it before?

• What did we learn last time?

• Is there an approved exception to the standard process?

• Why does our process work this way in the first place?

• This is where Notion becomes particularly interesting to us.

Notion positions its enterprise workspace around connecting company knowledge and work, with information organized so employees can search and use it.

Its Enterprise Search can also search across connected applications such as Slack, Google Drive, Microsoft Teams, Jira, and others, returning answers with citations back to the underlying sources. Notion's Enterprise Search documentation explains how that retrieval works.

Notion's AI Meeting Notes can also transcribe meetings and identify key points and action items, turning conversations that might otherwise disappear after the meeting into searchable information. Notion's AI Meeting Notes documentation provides more detail on the feature.

But technology is only part of the equation.

A meeting transcript isn't automatically useful organizational context.

Neither is a giant folder of process documents.

Organizational context requires some intentionality around what's worth preserving, what's current, what can be trusted, and what people will need later.

That's the larger idea behind organizational memory: preserving the knowledge and context your company has accumulated so people can find, trust, and use it when they need it.

Notion gives organizations a place to make more of that memory durable, structured, searchable, and available to people and AI.

Why isn't customer context enough?

Customer context tells you what's happening with the customer. It doesn't always tell you how your organization should interpret or act on that information.

Let's go back to our support example.

HubSpot tells you:

• This customer opened a support ticket about an integration problem.

That's useful customer context.

Now imagine your organization has dealt with the same integration problem before.

Your team discovered the obvious workaround creates another problem downstream. Someone worked with a technical expert to develop a better solution. The process was updated, and the reasoning was documented.

That's organizational context.

Put them together and an employee now knows:

This customer has this problem + here's what our organization has learned about solving it.

That's shared context.

Without the customer side, you have a playbook without the full situation.

Without the organizational side, you understand the situation but may not know what your company has already learned about handling it.

Neither view is as useful alone as they are together.

Why isn't organizational context enough?

Great organizational knowledge doesn't replace the need to understand the specific customer in front of you.

You can have beautifully documented processes.

Your employees can know exactly how your company works.

Your AI can retrieve the latest service playbook in seconds.

But customers aren't generic inputs you run through a process.

Imagine the process says a certain customer request should be handled one way.

HubSpot shows that this particular customer has been with you for eight years, recently experienced two service problems, has an active renewal opportunity, and discussed the same concern with another employee last week.

That's important context.

The playbook tells you how the organization handles the situation.

The CRM helps you understand the customer experiencing it.

Or, to put it another way:

Notion helps you remember how to serve customers. HubSpot helps you remember the customer you're serving.

What happens when customer and organizational context work together?

This gets more interesting when we stop talking about systems and look at actual work.

A prospect becomes a customer

During the sales process, HubSpot can preserve the structured customer history:

• Who was involved?

• What was the deal history?

• What marketing and sales interactions happened?

• What did they purchase?

• Where are they in the lifecycle?

But a successful handoff may require additional organizational context.

• What did the sales team learn during discovery that the delivery team needs to understand?

• Why was a particular approach recommended?

• Were any unusual expectations discussed?

• What lessons from similar engagements should the team consider?

When both forms of context are available, the delivery team doesn't have to begin the relationship by reconstructing everything that happened before the deal closed.

A customer runs into a problem

HubSpot provides the customer timeline.

Who are they? What's the relationship history? What support interactions have already occurred? Who owns the relationship?

Notion can provide the organizational knowledge.

What's our process? What have we learned from similar issues? What exceptions exist? Which documentation is current?

Together, the employee gets both the customer story and the organizational playbook.

An employee asks AI a question

Now imagine someone asks:

• How should we handle this customer's request?

An AI system with customer context might understand who the customer is and what has happened in the relationship.

But it may not understand your internal process, previous decisions, lessons, or standards.

An AI system with organizational context may understand your process perfectly.

But it may not know what's happening with this particular customer.

The more complete answer requires both:

Here's what's happening with this customer + here's what our organization knows about handling this situation.

That's where shared context becomes especially powerful.

Why does shared context matter even more for AI?

AI becomes more useful when it has access to trustworthy customer and organizational context—not simply more data.

Businesses are quickly discovering that access to an AI model is the easy part.

Giving your AI enough reliable context to understand your business is harder.

Notion has leaned heavily into this idea. Its Enterprise Search can search across the Notion workspace and connected tools, while linking answers back to their sources so users can verify them.

Notion itself describes its enterprise AI as being powered by a team's knowledge and workflows rather than operating only as a generic AI tool.

HubSpot is approaching the other side of the equation by putting AI alongside the customer data and activity in its Smart CRM and customer platform.

That gives us two valuable context layers.

But there's an important caveat:

• AI doesn't fix missing context.

If the CRM record is incomplete, AI doesn't magically know what the customer told your salesperson during an undocumented conversation.

If three versions of a process exist and nobody knows which one is current, AI doesn't automatically know which one your team actually follows.

If an important decision lives only in an employee's head, AI can't retrieve it.

We've written about what happens when institutional knowledge leaves with an employee and why information becomes so difficult to find at work because these problems don't disappear when AI enters the picture.

In some cases, AI simply makes them easier to see.

Does everything have to live in HubSpot or Notion?

No. Shared context doesn't require forcing every piece of company information into two applications.

Your accounting platform should probably keep doing accounting.

Your project-management platform should manage projects.

Slack and Microsoft Teams are useful for fast conversations.

Specialized operational systems may remain the best places for the work they're designed to handle.

The goal isn't to announce that everything must be migrated into HubSpot and Notion by Friday afternoon.

It's to make deliberate decisions about which systems own which types of context and how important context gets preserved and connected.

That's especially important because company knowledge has a tendency to spread.

A 2025 systematic review of AI and knowledge management found that legacy systems and knowledge silos can make information difficult to access and reuse across organizations. Researchers also found that fragmented systems and poor data quality can limit the effectiveness of AI-powered knowledge tools.

The peer-reviewed review of AI and organizational knowledge management examined 40 studies published between 2014 and 2024.

That's part of the problem we've started calling Knowledge Scatter.

Knowledge Scatter happens when useful information and context become fragmented across tools, documents, conversations, and people until finding and trusting the complete answer becomes unnecessarily difficult.

We go much deeper into that problem in the article above. For this conversation, the important takeaway is that connected context doesn't necessarily require one system.

It requires clarity about where trusted information belongs and how people can get the context they need without going on a company-wide scavenger hunt.

Shared context also needs governance

Connecting systems isn't enough.

Shared context only works when people can trust the context being shared.

If HubSpot contains duplicate customer records, missing lifecycle information, or years of questionable CRM hygiene, connecting it to more systems won't improve the underlying customer context.

If Notion contains outdated processes, conflicting documentation, or pages nobody owns, making all of it searchable won't automatically create reliable organizational memory.

In fact, better search can sometimes make bad information easier to find.

This is why governance matters on both sides.

For customer context, that can mean:

• Clear CRM ownership

• Consistent properties and lifecycle definitions

• Data-quality standards

• Duplicate management

• Intentional integrations

• Defined processes for updating customer information

For organizational context, it can mean:

• Clear content ownership

• Defined sources of truth

• Review and verification processes

• Naming and organizational standards

• Archiving outdated information

• Rules for what deserves to become durable organizational knowledge

Notion even supports page verification so teams can mark content as current, and its Enterprise Search follows existing permissions when surfacing information from Notion and connected applications.

Technology makes shared context possible.

Governance makes shared context trustworthy.

The goal isn't connected software. It's shared understanding.

We started with an employee preparing for a customer conversation.

HubSpot gave them one side of the story.

Who is this customer? What's happened? Where are they now? What do they need?

Notion gave them another.

How does our organization handle this? Why do we do it this way? What have we learned? What should we remember?

Neither system needs to become the other.

They become more valuable when each does its job well and the important context can come together when someone needs to make a decision.

That's the bigger idea we're working toward at Media Junction.

For years, we've helped organizations use HubSpot to create a clearer, more connected view of their customers.

Now we're also helping businesses think about the other half of the equation: the organizational memory their people and AI need to understand how the business actually works.

Our own approach to Notion reflects that philosophy. We're using it as a context layer for the decisions, processes, client history, project learning, standards, and knowledge that should remain useful beyond the moment when they're created.

Bring those ideas together and you get something bigger than an integrated tech stack.

You get people working from a more shared understanding of the customer and the organization serving them.

That's the foundation of what we call a Connected System.

If organizational context is the newer half of that equation for you, start with our Organizational Memory Guide. It explains why company knowledge becomes fragmented, what organizations risk losing, and how to make what your business already knows easier for people and AI to find, trust, and use.

Because connecting software is useful.

Connecting context is what helps people make better decisions with it.