The machine
Layer 2: The Path
The rungs, and what earns each one.
Milestones make readiness observable, and visible readiness kills the batch blast forever. Progress, events, triggers, calendar moments: attach each held-back offering to the milestone that earns it. Random timing produces random revenue.
In this layer
-
Contraction isn't a renewal-time event. It's a purchase-time decision arriving late: the buyer reprices everything they received against what they actually used, and the gap becomes the discount they demand.
-
Most companies instrument one expansion signal, product usage, and call it health. METAL names all five channels: Milestones, Events, Them, Actions, Lifecycle. The framework behind the milestone map and the orchestration motion, in print for the first time.
-
Ready is one of three conditions and the only one a trigger can see. Willing and able are produced by orchestration, ahead of the milestone. The gap between them is roughly forty percent take-up against eighty-five.
-
The objection underneath most pushback on expansion, and the people who hold it have usually watched it happen. They are describing something real. They are also describing the absence of a readiness gate, which is the same missing piece that inflates the forecast. One hole, two failures, reported to two different people.
-
Upselling doesn't hurt trust. The wrong thing, to the wrong person, at the wrong time hurts trust. Those are three separate variables, and conflating them leads teams to throw out the whole conversation instead of fixing what's actually broken.
-
A mid-market CRM vendor stopped chasing net-new and built an expansion system instead. They added $1.66M in ARR in nine months without touching their pipeline.
-
The most accessible growth opportunity in most SaaS businesses isn't in the pipeline. It's in the existing book of business — expansion that makes complete sense for customers, that nobody has uncovered yet.
-
Reactive expansion captures a fraction of the revenue that orchestrated expansion does. The difference isn't effort, it's design. Expansion attached to milestones is expansion your operation drives, not expansion that happens to you.
-
Everyone agrees that pushing expansion on your own calendar damages the relationship. The popular fix is patience, which is the same move with a longer fuse. Both put you in charge of timing that was never yours.
-
Renewal is twelve months after somebody signed a piece of paper. It has no relationship to the customer's progress, and the only emotional content of the moment is not wanting to get screwed. Then the compounding loss, which is the number that actually hurts.
-
The vocabulary got adopted. The mechanism didn't. Ask what the paths actually are and the answers come back: buy more volume, prepay discounts, tier upgrades. Stacking isn't ascending.
-
Happy customers are not a growth strategy. Happy doesn't have a pipeline. Happy doesn't have plays.
-
Most teams treat expansion as an event. That framing is why expansion is so hard. Expansion is behavior sequencing — a series of specific, observable customer actions that make the next step not just possible but obvious.
-
Two customers. Same product, same expansion, same lifespan. One is worth $4,000 more. The only difference is when the expansion happened.
-
Desired Outcome is not a goal-setting exercise. It's the lens through which every CS decision should be made.
-
One-time services get treated as low-quality revenue that dilutes the multiple. Some of it isn't revenue at all. It's the cheapest instrument you have for moving a customer to the milestone that unlocks recurring revenue, and your reporting shows it as the worst line on the page.
-
Vendors have always operated on an implicit assumption: customers have to do certain things to get value. But what if we've been asking the wrong question? Instead of 'how do we get the customer to do this?' — what if we asked 'why does the customer have to do this at all?'