This is The Agentic Commercial Model, Season 2: the build. Issue 02 laid out the operating model as a loop. This is the half issue that decides whether it survives contact with your org chart.
Walk into your commercial organisation tomorrow morning. Pick anyone. A rep, a CSM, a marketer, an ops analyst, someone three levels down who was not in the strategy session. Ask them one question.
What did you do yesterday that moved a customer through the loop, and how would you prove it?
If the answer comes back fast and specific, you have an agentic commercial organisation. If what comes back is activity, meetings attended, tickets closed, sequences sent, decks built, pipeline reviewed, then you have the old organisation wearing new language, and the operating model in Issue 02 will be dead inside two quarters.
That test is the entire issue.
Here is the principle underneath it, and it is not negotiable. A completely new commercial operating model for the agentic era demands a completely new commercial organisation, redesigned from the ground up, one hundred percent aligned to the loop it exists to turn. Not a reshuffle. Not a renaming. Not a transformation workstream running alongside business as usual. Every function, every objective, every individual, pointed at land, realise, expand, advocate. Not understood once at a town hall and referenced quarterly. Lived and breathed every day, by everyone, as the way the work is done.
Which produces the hardest sentence in this issue. There are no water carriers left.
No roles that exist to service the process rather than the customer. No teams busy being busy, manufacturing internal artefacts that move nothing outside the building. No individual who cannot name, without hesitation, which stage of the loop they own, which metric they move, and what they moved it by yesterday. One loop. Clear KPIs. Clear metrics. Every person in the commercial organisation able to trace their day's work to value realised for a customer, and able to say so out loud.
That is a brutal standard, and I hold to it for a simple reason. The loop only compounds if it turns every single day. An organisation where the loop is genuinely understood by the twenty percent who attended the offsite is an organisation whose loop stops turning the moment those twenty percent get busy. Which is roughly week three.
And I have watched exactly that happen. Three times, three different ways, three different businesses. The failure modes are so consistent I can now predict which one a company is about to run, usually from the org chart alone, sometimes from a single reporting line.
The first is the reorg that reverts. New model announced, slides circulated, town hall applause. Two quarters later the pipeline review is back to stage progression, the QBR is back on the calendar, and someone has quietly recreated a renewals desk because the numbers needed owning. Nobody decided to go back. It simply grew back, the way a path reappears across a lawn.
The second is the rename. Customer success becomes "value realisation." Same people, same headcount ratios, same reporting line into the same leader, same quarterly cadence, new email signatures. The company believes it has changed its operating model. It has changed its stationery.
The third is the pod that collapses. The seller and the CS lead are put in a pod, told to share the customer, told to collaborate. Then comp season arrives and the seller is still paid on bookings while the CS lead is measured on retention. Within one quarter they are competing for the same conversation, and within two the pod exists only in the org chart.
Three failures, one cause. In every case the company changed what people were told to do, and left untouched what the structure made rational for them to do. Structure eats intention for breakfast, and then it eats the transformation programme for lunch.
So this issue is about the harder half. Not the model. The org that has to hold it.
Why the line grows back
Understand the mechanism and the rest of this issue writes itself.
The old operating model was a line, and the org that ran it was a relay. Marketing carried the baton to sales, sales carried it to onboarding, onboarding to customer success, customer success to renewals. Each function owned a segment of the track, was measured on getting the baton to the next hand, and was structurally indifferent to what happened after the handoff. That indifference was not a culture problem. It was the design working exactly as intended, because in a world where value was delivered annually as access, segmenting the track was efficient.
Now put a loop on top of that relay. Nobody owns the loop, because the org has no unit that spans it. Every function still owns a segment. The metrics still measure segment throughput. The incentives still reward getting the baton away, not what it produces two stations later. So the loop is described in the strategy deck and executed as a relay, and within two quarters the relay reasserts itself, because the relay is what the structure is actually built to run.
This is why the announcement never sticks. You cannot instruct a relay to behave like a loop. You have to stop running a relay.
The organising principle: build the org around the loop, not the funnel
Here is the call, and it is the one that will cost people their empires.
The new commercial organisation is structured around the four stages of the loop, land, realise, expand, advocate, not around the legacy functions of the funnel. That is not a cosmetic remapping of who reports to whom. It means the fundamental unit of the org stops being the function and becomes the customer's journey through the loop, and every team is defined by which part of the value cycle it owns rather than which activity it performs.
What that looks like in practice, described as functions rather than as job titles you can hire off a template, because the titles will vary by business and the functions will not:
Landing. Owns time to first value, not deal size. This function's number is the distance between signature and the customer's first verified outcome, and it holds that number all the way through activation rather than handing it off at contract. That single change kills the most expensive lie in SaaS, the one where sales celebrates a close that implementation quietly fails to convert into anything real for seven months.
Realisation. The centre of gravity, and the function most companies do not have. It owns verified value delivered per customer, on a monthly cycle, with the instrument from the next issue underneath it. Crucially it is a commercial function, not a support function, and I will come back to why that reporting line is the single most consequential decision in this entire issue.
Expansion. Owns growth discovered from usage telemetry rather than growth argued at renewal. It sits with realisation rather than opposite it, because the expansion signal and the value signal are the same data read by the same people. Separating them is what creates the classic pathology where CS knows the account is thriving and sales finds out at renewal.
Advocacy. Owns the conversion of verified outcomes into public, machine readable proof. In the old org this was a marketing afterthought that begged CS for references. In the loop it is a standing function with a quota, because as Season 1 established, that proof is now the top of your funnel. If nobody owns it, the proof evaporates and the machine that shortlists you never learns you delivered anything.
Notice that these four functions are sequential in the customer's experience and simultaneous in the org. Every account is in all four stages at once, at different depths, which is precisely why the relay cannot model it and why the org has to be built to hold four concurrent motions on one relationship.
Now push the design down to the individual, because this is where most redesigns stop and most redesigns fail. Four functions with four numbers is an org chart. It becomes an operating model only when every objective, at every level, cascades to one of those four numbers. Not loosely aligned. Traceable. If a person's objectives cannot be walked back to time to first value, verified value delivered, expansion discovered, or proof published, then either the objective is wrong or the role is. There is no third option, and refusing to name which one it is is how you end up carrying the same water for another year.
Run that audit honestly and it is uncomfortable, because a meaningful share of what a commercial organisation currently measures survives only because nobody has asked it to justify itself against a customer outcome. Activity dashboards nobody acts on. Reports produced weekly for an audience of one. Internal reviews that generate a decision that could have been made in a Slack message. Every hour of it is capacity the loop needs and is not getting. This is not an efficiency drive bolted onto a transformation. In an org where every objective ties to the loop, the inefficiency has nowhere to hide, because anything that does not move one of four numbers is visibly not moving anything at all.
The casualty list
If you build the org around the loop, some roles stop existing. I am going to name them, because the polite version of this issue would let every reader assume it applies to somebody else's team.
The SDR function as currently constructed. Built to manufacture first contact with a buyer who now arrives pre-decided from an AI shortlist, most of the activity is expensive noise aimed at a stage of the journey that has moved. McKinsey's work on redesigning technology workforces for the agentic era already documents SDRs among the roles being displaced, alongside renewal managers and support engineers, as part of a 20 to 30% net impact on workforce composition. The capability that survives is research and targeting. The volume-outreach machine does not.
The renewals manager. A role whose entire existence is an artefact of the annual event. When value is verified monthly and commitments refresh administratively, a specialist whose job is to negotiate a number once a year is a role built around a ritual you have abolished. Keeping it is how the ritual survives.
The CSM as a coverage ratio. Not the people, the model. Sizing a team by accounts per CSM is a support-desk logic applied to a commercial function, and it collapses when the product delivers the service and the human delivers the value case. The companies that restructured early are running customer success at 20 to 30% lower headcount without a drop in NPS, and the ones that got that right did it by changing what the function owns, not just by cutting it.
The account manager as a separate species from the CSM. The classic distinction, CSM owns the product journey and AM owns the commercial journey, is a distinction the loop does not permit. When value realisation and expansion are the same signal, splitting them across two roles guarantees the seam where accounts go to die. One of these roles is going to absorb the other. Decide which, deliberately, or watch them fight about it.
The QBR industry. Not a role on paper, but in most businesses it is three to five full-time equivalents of slide production, internal review and calendar management, generating a retrospective artefact for a meeting that tells the customer in month nine what your telemetry knew in week two. Replace it with the monthly value review and reclaim the capacity.
And the ones already going quietly. Customer marketing operators, community managers, advocacy leads and loyalty managers are being absorbed as agents take on the executional work of drafting communications, pulling signals and computing health scores. The strategic question in the loop is not who performs those tasks. It is who owns the outcome they used to serve.
None of that is a headcount argument. Every function above holds capability the loop still needs. The point is that the containers are wrong, and if you keep the containers you will keep the relay, whatever you call it.
The reporting line that decides everything
One structural decision matters more than all the others, and it is the one most companies get wrong for defensible-sounding reasons.
Realisation must report into revenue leadership. Not into support. Not into operations. Not into product. The moment value realisation reports anywhere other than the commercial line, it is framed as a cost centre, and that framing decides its budget, its calibre of hire, its seat at the forecast, and ultimately whether the loop has a centre of gravity or a service desk where its centre of gravity should be. When customer success reports into support or operations it will always be treated as a cost, and reporting into revenue leadership changes budget conversations, hiring plans and how success is defined.
There is a version of this that is worse than getting it wrong, which is getting it half right. Several businesses I have worked with moved realisation under the CRO and then left the operating cadence, the metrics and the comp untouched. What they built was a sales organisation with a retention team attached, which is the second failure mode from the top of this issue with a better org chart. The reporting line is necessary and it is nowhere near sufficient. Structure, cadence, metric and incentive have to move together or the strongest of the four pulls the other three back.
Which is the honest reason this is a half-issue and not a full one. The org design cannot be completed until the instrument exists to measure realisation and the comp plan exists to pay for it. Those are the next issues. What this issue does is stop you building the loop on a chassis that will reject it.
To the CRO, plainly
Let me finish where the resistance actually lives, because it is not in the middle of the organisation.
If you run revenue today, this issue proposes dismantling most of the structure you built, and probably some of the structure that got you the job. The functional hierarchy, the specialist teams, the stage-gated pipeline, the segmented ownership, all of it was competent design for the model it served, and all of it is now the thing preventing the model that replaces it. Your empire is the problem. Not your people, not your intent, not your ability. The shape.
I have watched more of these transformations die from senior self-preservation than from any failure of strategy, and it never looks like resistance. It looks like sequencing. It looks like phasing. It looks like a pilot in one region, a working group, a decision deferred to next planning cycle, and a structure that is still standing three cycles later while a competitor with a loop compounds past you. Nobody ever says no. They just protect the shape, and the shape wins by default, because the shape is what people are paid inside.
So the question is not whether you agree with the loop. Most CROs I speak to agree with it in the abstract within about ten minutes. The question is whether you will restructure an organisation you designed, dissolve boundaries you defended, and hand ownership of the customer to a function that did not exist when you drew the chart. If the answer is no, be honest that the answer is no, because the alternative, agreeing publicly and phasing indefinitely, is how the line grows back while everyone congratulates themselves on the transformation.
The CRO who does this first in their category will own the compounding. The rest will run a relay against a loop and wonder why the gap keeps widening.
Build the model the product deserves. Then build the org which underpins the new agentic commercial operating model, not one that quietly rebuilds the old one.
Next issue: Building the Instrument. Value Realised Retention, specified to the level you could hand your RevOps lead on Monday. The org above cannot function without it, which is why it comes next.
First published in the Agentic Commercial Model newsletter on LinkedIn, August 13, 2026. Read the original on LinkedIn.