The Value Creation Protocol

Part IV — How the organization is built

Chapter 18

The Three-Org Model


Pick one customer you know well. Trace how they got to you and what has happened since, and write down every time they met a new face.

Your list might read like this. Somebody's content reached them first. Then somebody booked a meeting. Somebody else ran the meetings and got the signature. Then they were introduced to the person who would set things up, and later to the person who would "manage the account," and later still to whoever answers when something breaks.

Every one of those people may have been good at their part. That's what makes this hard to see from the inside. From the customer's side it was one relationship, and they had to restart it each time.

What this is

The Three-Org Model is the organizational architecture for Value-Led Growth. It replaces the usual functional silos with three organizations, each with one clear job.

The Customer Org is everyone who creates and delivers value to clients. It holds the whole Value Path, from Audience through Champion. There's no split between "getting" customers and "keeping" them, and no handoffs between stages. A relationship is stewarded continuously. It is never passed from one specialist to the next. The role that leads it is a Chief Customer Officer. Some companies will call it a Chief Value Officer.

The Operations Org is AI-powered coordination that makes the Customer Org effective. It holds the systems, the data quality, the process work, the documentation and the platform. Its principle is that operations should be invisible to clients. They experience things working. They don't see the machinery. The coordination stays invisible, and the capability it builds is the client's to hold and carry. The role that leads it is a Chief Operations Officer.

The Finance Org is resource stewardship and value accounting. It tracks the money, and it also measures value delivered. That second job changes investment decisions, pricing and where resources go. The role that leads it is a Chief Financial Officer, with a wider scope than the title usually carries.

Three orgs. Three leaders. One mission: maximize value created and received across all relationships.

These are roles, not headcounts. In a small company one person may hold more than one of them. What matters is that each job is somebody's.

The Value Steward is the main role inside the Customer Org. The definition:

A person, working with AI, who carries a whole relationship all the way through — full context, real depth, no handoffs. AI handles the breadth so the human can go deep.

AI takes the research, the documentation, the coordination and the pattern-watching. The human brings judgment, trust, creative problem-solving and presence in the hard moments. The model's own working figure is that one Value Steward partnered with AI might steward 50 to 100 relationships through their whole journey. The old arrangement gives a person hundreds of records to move through a single stage.

Why the Operations Org can be small. In a traditional company, operations takes large teams, because people do the coordinating by hand. In this model AI handles coordination at scale and humans focus on judgment, strategy and the edge cases. That's a statement about where the coordination goes. It is not a statement about cutting people.

The arithmetic. The traditional shape is seven or more functional silos, each with its own goals and often its own operations team, multiplied by the coordination between them and the loss at every handoff. The Three-Org shape is three organizations with clear boundaries and coordination carried by AI.

Each org also looks after one of the Four Unified Views. The Customer Org stewards the Unified Customer View, the Finance Org the Unified Revenue View, and the Operations Org the Unified Operations View. Business leaders steward the Unified Strategy View. Stewardship means looking after a view. It isn't an access rule and it doesn't create a new silo. Every team reads and adds to every view. Chapter 19 teaches the views.

In the Value Creation Protocol, the Three-Org Model is the structural model the Protocol operates within.

How to tell where you are

Signs you can check this week:

  • The trace you just did has more than two or three new faces in it. The model's picture of the traditional company has seven handoffs, with context lost at each one.
  • Your customers repeat themselves. They explain their situation again to each new person.
  • Ask "who owns this relationship?" about a customer you've had for two years. If the honest answer is a department, or "it depends what they need," nobody does.
  • Each function has its own operations people. Revenue operations here, marketing operations there, and each one has its own version of the data.
  • Each team hits its own goals and the customer still had a rough year.
  • Finance can tell you what each customer paid. It can't tell you which relationships are compounding and which are fading.

What to do

These are the model's own moves, in order. Do not skip to the second one.

  1. The pilot: prove the model. Start with proof, not proclamation. Select someone who already fights against handoffs. You know who they are. Give them full Value Path ownership for 20 accounts. Provide AI partnership. Measure outcomes, not activity. Build the proof before you restructure anything.
  2. The collapse: unify the Customer Org. Once proof exists, bring sales, marketing and customer success together into one Customer Org. Eliminate the handoff processes themselves. Moving the boxes under one leader and leaving the handoffs in place changes nothing the customer can feel. Make the Value Path the operating language, so people say where a customer is in the same words.
  3. The separation: clean operations. Pull every operations function together: revenue operations, marketing operations, sales operations, customer success operations. One team, with one mandate: make the Customer Org effective.
  4. The evolution: value accounting. Finance widens its scope beyond revenue to include measuring value delivered. It starts asking new questions. What's the value delivered per dollar invested? Where does value compound, and where does it dissipate? Value Accounting is the handbook for that work.

Read your progress from three milestones, and read them from trust, not from the calendar.

  • Foundation: when core relationships demonstrate the new model works.
  • Capability: when teams operate confidently in the new structure.
  • Multiplication: when results compound and the change sustains itself.

One thing to say to your people early, in plain words: this model reorganizes responsibility. It does not require firing your marketing team.

How you know it worked

Ask the customers in the pilot. They're the ones who can say.

  • A customer picks up a conversation where it left off and never has to re-explain. Context accumulates. It doesn't evaporate.
  • Asked who they work with at your company, they give a person's name and they don't need to think about it.
  • When something new comes up, they bring it to that same person. They don't hunt for the right department.
  • They never mention your process. If operations is working, the customer has nothing to say about it.
  • A year in, they trust you more than they did at the signature. Trust deepened. It didn't reset with each new face.

And one from the inside: the steward tells you this is the first time they've been able to see a relationship all the way through. They're a receiver of value here too.

A cleaner org chart doesn't count. Fewer boxes, with the same customer experience, is a drawing.

Where it goes wrong

The B2B Trap sits under this whole chapter. It's defined as treating humans as database objects to be processed through stages rather than relationships to be understood. Handoffs are what that looks like in a structure. If your pilot steward still "passes" a customer to somebody at a stage boundary, the trap came along into the new model.

The AI Replacement Trap sits beside the Operations Org. Its definition: believing AI's primary purpose is to replace human workers rather than enhance their capabilities. The Operations Org can be small because coordination moved to AI. The moment someone presents this model as a way to cut headcount, they've left the model.

The other failures the model itself names:

  • Treating it as just a new org chart, or a restructuring exercise.
  • Mapping your old departments one-to-one into the three orgs and calling it done.
  • Creating handoffs inside the Customer Org. That defeats the purpose.
  • Keeping operations fragmented while claiming the model.
  • Measuring only revenue, with no value accounting beside it.
  • Putting the structure in without the philosophy. Chapter 17 comes first for a reason.

Read further

Stop 1 of 6: What this is

Back to contents