The Value Creation ProtocolContents
Part III — The Core Framework Traps
Chapter 8
The Leads Trap → Value-First Humans
When industrial logic meets human relationships, everyone loses
In June 2025 I hosted a series of conversations, one trap at a time. George B. Thomas, the HubSpot Helper, took the Leads Trap. Early in our conversation he said:
"This world that we live in where we call humans leads, it's kind of like calling your spouse a roommate. Now in some cases that might be technically accurate, maybe, but it's emotionally … it should be absolutely not."
Technically accurate. That's the part that keeps this trap alive. Nobody in your company is lying when they say "lead." The record exists. The form was filled in. The stage is correct. And the person on the other end wouldn't recognize themselves in any of it.
What this is
Here is the Leads Trap in one line:
Treating humans as objects to be captured, scored, and converted rather than relationships to be developed.
My read is that it began as housekeeping. A growing company needs some way to keep track of the people it might serve. Then the keeping track turned into processing, and the processing got its own vocabulary. The trap's fuller description names it:
"The Demand Waterfall created artificial stages—MQL, SQL, SAL—fighting natural buying behavior. Organizations optimize for internal process rather than customer value."
The belief this runs against is Wholeness over Fragmentation. That belief says people are complete humans, not partial resources. The Leads Trap fragments humans into data points: a job title, a company size, a count of pages viewed.
Its Value-First alternative is Value-First Humans, and its principle reads: "People are complete humans with context, history, and potential—not data points to be processed." George says the same thing in his own words: "We have to stop thinking of humans as data points … and start treating them like the humans they are."
One thing before the signs. In August 2025 I wrote about teams doing conference outreach that they knew felt wrong, and I said of them: "These aren't bad people. They're good people stuck in bad systems." That goes for everyone who has ever carried a quota of names. This chapter is about the system.
How to tell where you are
The clearest picture I know is conference season. That same piece laid out the pattern around one big industry event. It starts with a budget question: "We spent $50K on [the conference]. How many leads will we generate?" Then come the purchased attendee list and the thousands of templated emails. Then the scorecard: "Success gets defined by badges scanned and meetings booked, not relationship quality."
You don't need a conference to check. Any ordinary week will show you the same thing:
- The nouns. Sit in one sales or marketing meeting and listen for "leads," "MQLs" and "conversion rate." Then count how many times a person was mentioned by name.
- The download test. Pick one thing a person can download from your site and follow what happens to them next. If the answer is a score and a string of emails they didn't ask for, you're in it.
- The repeat. A person explains their situation on a form, again to the first person who calls, and again to whoever starts the work.
- The argument. One team says the names it was handed are no good. The other says nobody followed up. Both are right.
- The bill. More names come in every quarter, each one costs more to get, and fewer of them turn into a relationship.
- The stage. Someone gets moved along because of what your process needed that week. Nothing they said or did put them there.
What to do
- Ask who you mean. For one week, every time the word comes up, ask which person, and where they are. "Lead" flattens people at very different points into one thing you can process. The Value Path gives them back their own names. An Audience member is saying "I am learning." A Researcher is saying "I am researching." A Hand Raiser is saying "I need help." A Buyer is saying "I am buying." Chapter 3 has all eight stages.
- Walk one path as them. Take one person who became a customer recently and one who went quiet. Write down every time they had to tell you something you already knew, and every place they had to bend to your process to keep going.
- Stop doing things to people who haven't asked. List everything that fires on its own: the email sequence after a download, the phone call after a badge scan. For each one, ask whether the person asked for it. If they didn't, turn it into something they can pick up when they want it.
- Decide what a real signal is, and answer it the way a person would. A signal is something a person actually did: "a real question, a repeat visit, a reply, a booked call." Read it as movement in a relationship. Never turn it into a score, a rank or a target attached to that person. When a hand goes up, a human answers, with what you already know about them in front of that human.
- Give the relationship one keeper. The practice is that Value Stewards own entire relationships, not single stages. Chapter 18, on the Three-Org Model, teaches the role. You can try it small before you reorganize anything. Pick a handful of relationships and let one person stay with each of them from the first conversation through delivery.
- Carry two questions into every conversation. I wrote them for that conference crowd and they travel well. The first: "Am I seeing them? (As whole people with complex challenges, not just potential transactions)". The second: "Am I hearing them? (Understanding their actual situation, not projecting our assumptions)".
None of this bans a number. A score living inside the Unified View of that relationship is different; scoring in place of understanding is the trap. Chapter 19, on the Four Unified Views, shows what that view holds.
How you know it worked
The proof comes from the people you used to call "leads."
- They stop repeating themselves, and they notice. Someone picks up the conversation where the last person left it, and the person on the other end tells you they didn't have to explain it all again.
- They raise their own hand. They write or call and say, in whatever words are theirs, "I need help." Nobody chased them there.
- They answer like a person. What comes back is about their situation: a question, a detail, a "not yet, but here's what's going on."
- The ones who don't buy still come back. They return when things change, or they send you someone you can help.
Inside the company you'll hear a difference too. People get talked about by name and by situation. That's a good sign, and it isn't the proof. Neither is the number of names in your system, whether it went up or down. The proof is what the person says and does.
Where it goes wrong
Next door is the Qualification Trap (Chapter 11). The two work together on the early part of a relationship. Here is how it starts. You retire the word "lead," you start calling people "signals," and then you sort the signals into hot and cold with a threshold for who gets a call. It's the same machine with kinder labels.
We caught this in our own wording. An earlier version of this trap's definition ended by describing people as "signals to be recognized." That phrase came out, because our change note says it was "still susceptible to dehumanization." A "signal" can be collected and scored exactly the way a "lead" can.
More ways this slides back:
- The record system is built for stages. If the tool only knows how to move an object from one column to the next, people will be treated like objects in columns. That's the B2B Trap underneath this one, in Chapter 5.
- Pay is tied to the count. If someone's bonus depends on names delivered, names will be delivered.
- The word changes and nothing else does. New vocabulary on the old process teaches your team that the vocabulary doesn't mean anything.
- Each department still owns a slice of the person. Three teams, three versions of the same human, and the human can tell.
Read further
- The AI-Native Shift (Book 3). Chapter 3, "The Complexity You've Normalized," shows this trap and the three nearest to it as one posture. Chapter 7, "Structure Follows Value," has the table that retires the industry's words against the Value Path's, and it introduces the Value Steward.
- A Value-First Guide to Surviving the SaaSpocalypse (Book 1) tells the story of how business software came to treat people as objects to be processed. Its chapter on assessing the traps is where the download test above comes from.
- The Value Era (Book 0) explains why only the person who received the value can say it happened, which is why this chapter's proof comes from them.
- Value Accounting (Book 4) is the handbook for writing down what that person told you and checking it with them.