The Value Creation Protocol

Part IV — How the organization is built

Chapter 17

Value-Led Growth


In September 2025 I published an article with a dedication at the top, a few lines each to customer teams, product teams, operations teams and business leaders. The lines to product teams ended like this:

"Please stop focusing on how much time you are saving me and ask me how much additional value you are helping me to create."

That sentence was aimed at one team. This chapter aims it at the whole company.

Think about the last meeting where your company talked about growth. Maybe somebody wanted more salespeople. Somebody else wanted the product to sell itself. Somebody wanted more content, and somebody wanted a community. If that sounds familiar, notice what those answers have in common. Every one of them names a team.

What this is

Value-Led Growth is the philosophy the rest of this handbook sits inside. It starts by changing the question.

The growth models you already know ask, "Which team drives growth?" Sales-Led Growth says build a sales team and work the pipeline. Product-Led Growth says let the product sell itself. Marketing-Led Growth says generate demand through content and campaigns. Community-Led Growth says build tribes that advocate and refer.

Value-Led Growth asks, "What drives growth?" And it answers: value delivery and recognition. Not which team leads, but whether value is being created, demonstrated and compounded at every stage of the customer relationship.

It comes down to organizing the entire company around a single question: Are we creating more value today than yesterday?

That question only works if you know what you mean by value. The definition belongs to The Value Era, and I'll give it here exactly as it stands there:

What a person or organization can now do that they could not before. Not what they were sold, not what was produced for them, not a promise about the future — value is the real change in what someone can do, and only the person who received it can say it happened.

Hold on to the last part. Only the person who received it can say it happened. Everything in this chapter's test of success comes from that.

One more idea sits under this one, and it also started in that 2025 article. I called out what happens when a company focuses on saving time: it ends up "treating human capability as a fixed cost to minimize rather than an abundant resource to multiply." Turn that around and the staffing question changes. The question isn't "How many people do we need?" The question is "How much value can each person create?"

Value-Led Growth has four working parts. Each one has its own chapter, so here I'll only say what each is for.

  • Where: the Value Path. Eight stages that describe how a person actually moves toward value and then creates it. It isn't a funnel to push people through. It's a way to recognize where someone is and what value they need there. See Chapter 3.
  • Who: the Three-Org Model. Three organizations in place of the usual functional silos: a Customer Org, an Operations Org and a Finance Org. See Chapter 18.
  • What: the Four Unified Views. Four business outcomes that transform fragmented operations into unified capability. See Chapter 19.
  • How: the Value Steward. The main role inside the Customer Org, a person partnered with AI who stays with a relationship through the whole Value Path. Chapter 18 covers the role along with the org it lives in.

In the Value Creation Protocol, Value-Led Growth is named the growth pattern the Protocol enables. Chapter 1 has the Protocol's five claims.

I want to be straight about one thing before you go on. Value-Led Growth isn't a claim that the other models are wrong. It's a different question, not a better team. Selling still happens. The product still matters. So does content, and so do the people who talk about you. What changes is what you believe is driving all of it.

How to tell where you are

You can check these this week, in your own company.

  • When growth comes up, the first argument is over which team owns the number.
  • Your growth plan is a hiring plan. More revenue means more people, in roughly the same proportion.
  • You keep customers mostly through contract terms, and you find out how they feel at renewal.
  • The people who write your content and the people who hold your customer relationships sit in different groups with different goals. What the content says and what the relationship is actually like don't match.
  • The questions in your leadership meeting are about activity: how many, how fast, how much.

Then do the plain version of the audit. Look at your org chart. Count the coordination roles. Measure the handoff overhead. Count the management layers. Notice what gets measured and what gets rewarded.

If what you find is an organization that spends more energy managing itself than creating value for customers, you've found the trap. No shade there. Nearly every structure on that chart was a reasonable answer to a limit that was real when it was drawn.

What to do

  1. Ask the first question with your leaders in the room. "Is your organization designed to create value, or to manage complexity?" Let people answer honestly before anyone defends anything.
  2. Put the one question on the weekly agenda. "Are we creating more value today than yesterday?" Make the rule that an answer has to name a person and what they can now do. A volume isn't an answer.
  3. Change the staffing question. The next time a plan says "we need more people," ask the other one first: how much value can each person here create, and what is in their way?
  4. Learn to say where a customer is. Use the Value Path's stage names for real people you serve. If your team can't agree where a given customer is, that's your first finding.
  5. Prove it small before you redraw anything. Start with proof, not proclamation. Chapter 18 walks through the pilot: one person, a small set of relationships, the whole path, no handoffs.
  6. Keep your words honest while you do it. If you describe Value-Led Growth in the vocabulary of leads, pipeline and conversion, you've brought the old model back in through the language.

Don't promise anyone a timeline or a return on this. The pace is set by trust, not by the calendar. Chapter 21 has the readiness milestones.

How you know it worked

You know by what the people who received the value say and do. The second half of the Value Path gives you their own words for it.

  • A customer tells you, in their words, what they can do now that they couldn't before. On the Value Path that's the Adopter: "I realize your value."
  • They tell someone else without being asked. That's the Advocate: "I tell others about you."
  • When renewal comes around, the conversation is about what's next. Nobody is negotiating over whether to stay, because the value kept coming and leaving would make no sense to them.
  • Someone on your own team tells you they did something this quarter they couldn't have done last quarter. Your people receive value too.

What doesn't count: more content shipped, more meetings held, more records in the system. Revenue going up doesn't settle it by itself either. Money is one Value Wake that value leaves behind, and it gets counted later. Value Accounting is the handbook for booking the answer properly.

Where it goes wrong

The Measurement Trap is right next to this chapter. It's defined as optimizing for activity metrics that feel productive while missing outcomes that create value. It starts quietly. You adopt the one question, and within a month somebody has turned it into a weekly count of things done. If the answer to "are we creating more value today than yesterday?" is a number nobody outside your building would recognize, you're in it.

Three more ways this slips:

  • Treating it as a sales method. It's a philosophy for the whole organization. A Value Steward isn't a super salesperson. The role carries the full relationship, not a better close.
  • Hearing the staffing question as a headcount cut. That's the AI Replacement Trap: believing AI's primary purpose is to replace human workers rather than enhance their capabilities. "How much value can each person create?" is a question about multiplying people.
  • Restructuring before proving. Redrawing the org chart on the strength of an idea is how good ideas get a bad name. Pilot first.

Read further

Stop 1 of 6: What this is

Back to contents