The Value Creation ProtocolContents
Part II — The two foundational traps
Chapter 5
The B2B Trap → Value-First Customer
We treat humans like objects to be processed, and then we don't understand why we can't measure anything related to that effectively.
I said that in a conversation in the fall of 2025.
Here is what it looks like from the inside. Someone on your team knows a customer well. They know what that person is trying to get done, what was promised, what went sideways last year. Then somebody new takes over the relationship, a person or an AI, and we tell them: just log into the system, you'll see the data, and then you'll know what to do.
No. That's not how it works at all. The system has the record. It never had the relationship.
What this is
The B2B Trap, as the methodology defines it:
Treating humans as database objects to be processed through stages rather than relationships to be understood.
It is one of the two foundational traps. The other is the SaaS Trap, in the next chapter, and the two are a pair. The B2B Trap makes it normal to think of people as objects. The SaaS Trap breaks up the context you would need to think of them any other way. Together they are the conditions that make the other ten traps possible.
The methodology describes what the trap does to the work in three short sentences:
CRM systems optimize for reporting rather than relating. Context dies at every handoff. Teams work around systems to do their actual jobs.
Don't be thrown by the letters. The trap is named for the world it was built in, and what it describes is people: a business purchase involves human beings, and the trap is treating them as an entity moving through your stages.
Its way out is Value-First Customer:
Customers are humans in relationships with your organization, not database records moving through stages. Shift from tracking activities and properties to understanding progression, context, and value creation.
The principle underneath it is to "design around natural human value creation patterns, not internal processes." In practice that is one change of direction. Today customers adapt to your systems. Afterward, your systems adapt to the customer's reality.
One of the Protocol's five claims says this from the other side: "Relationships are the unit of value creation; transactions are events within relationships." Chapter 1 has it in full.
How to tell where you are
These are the trap's five signs, in the methodology's words, each with something to go and look at this week.
- "CRM optimized for reporting, not relating." Open one customer's record and read it as though you had to call that person in ten minutes. Does it tell you what they are trying to get done? Or does it tell a manager what was done to them?
- "Context lost at every department transition." Follow one customer across their most recent handoff. Ask the colleague who received them what they knew on the first day. Ask the customer how many times they explained themselves.
- "Activity measured but outcomes unexplained." Pull the report your team looks at most. It can tell you how many calls, emails and meetings happened. Ask it why one customer stayed and another left.
- "Best people succeed despite systems, not because of them." Sit with the person on your team that customers ask for by name. Ask them to show you how they actually keep track of a relationship. Watch where they go.
- "Shadow systems (spreadsheets, Slack) hold real intelligence." Ask to see the spreadsheet. There is one. It was built by someone who needed to understand a customer and couldn't do it in the official place.
If you can attach a real example to any of these, you have a place to start. Finding them is nothing to be ashamed of. Nobody in your company chose this.
What to do
Pick one customer and write down the relationship the way they lived it. From their first question to today, in their words wherever you have them. Map the human's path, not your internal handoffs. Use the Value Path from Chapter 3 to say where they are now.
Mark every point where they had to explain themselves again. Each one is a handoff where the context died. Count them for this one customer. You'll use that list in the next move.
Write down what you know to be true about this person, and where each piece lives. One page. The record, the inbox, the spreadsheet, someone's memory. The plain test, which you'll meet again in Chapter 19 on the Four Unified Views, is a question: is everything we know to be true about this person here?
Change one thing so the system adapts to them. One handoff, one form, one layout of one record. Choose the point on your list where the customer was asked to repeat themselves most, and make that the place where what's known travels with them.
Change what you keep on that record. Less of what you did to them. More of where they are, what they're trying to do and what has changed for them. The methodology's words for it: progression, context, and value creation.
Have the next person who serves this customer start from that page. Then ask the customer how it went.
Then do it for a second customer. This chapter doesn't ask you to rebuild your systems. It asks you to design around one human at a time until the pattern is plain enough that the systems have to follow.
How you know it worked
The customer doesn't have to start over.
Someone new picks up the conversation and the customer notices that this person already knows. They say so, in whatever words they use. Or they just get to the point faster than they used to, because they've stopped expecting to be asked.
A second voice confirms it. The colleague who received the handoff tells you they didn't have to go and ask anyone what the story was.
What doesn't tell you it worked: fields filled in, records updated, the number of customers sitting in each stage. Those can all improve while the customer is still explaining themselves to the fourth person this year.
Where it goes wrong
- Blaming the software. People want to call this the CRM Trap. That isn't its name, and it isn't the problem. The system did what it was asked to do, which was report. If you replace the system and keep the thinking, you get the same trap with a new login.
- The Leads Trap and the Qualification Trap. The methodology says these two work together to dehumanize early relationships, and the B2B Trap is what makes that look normal. If you fix how you treat existing customers and keep scoring and filtering the new ones, the object-based thinking is still coming in the front door.
- The SaaS Trap, next door. The natural response to "we can't see the customer" is to buy something that promises to show you. That is the other foundational trap, and it is the next chapter.
- Doing it faster with AI. The AI Replacement Trap threatens to accelerate every other trap at machine speed. An AI that processes people through your stages more efficiently is this trap, sped up.
- Calling it done when the record looks better. The record was never the point. Go back and ask the person.
Read further
- A Value-First Guide to Surviving the SaaSpocalypse (Book 1) tells this trap as story, as the deeper problem underneath what happened to software.
- The AI-Native Shift (Book 3), Chapter 2, "The Org Chart Is a Confession," draws this trap as architecture. Chapter 6, "The Meaning Layer," explains why context dies at every handoff.
- The Value Era (Book 0), Chapter 14, "Only the person who received it," is why the test in this chapter is the customer's word and not your record.
- Value Accounting (Book 4) is the practice of showing a person the value you believe you created for them and letting them confirm it or dispute it.
- In this handbook: the SaaS Trap is next. The Leads Trap and the Qualification Trap are Chapters 8 and 11. Chapter 19, on the Four Unified Views, teaches the Unified Customer View, where the one page you wrote in the third move becomes a standing thing.