A business that grew steadily for years flattens. The instinctive response is tactical: change agencies, add a channel, refresh the ads, post more. Activity rises. The line stays flat. Everyone gets a little more tired and a little more certain the market has turned.

After enough of these conversations a pattern emerges. The tactics are usually fine, or at least fine enough. The loss is happening between them, in the handoffs no single function owns, and it compounds down the whole chain.

Where does a growth plateau actually live? #

Plateaus live in the joints of the growth engine: the handoffs between positioning and site, site and content, content and channels, channels and lifecycle, lifecycle and data. Each function can score well on its own metrics while the connection between it and the next quietly leaks, and the leaks multiply rather than add.

This is why plateaued businesses so often report a confusing picture. The paid team hits its cost targets. The content calendar ships on time. The email platform sends on schedule. Every dashboard is green and the revenue line is flat, because dashboards measure functions and revenue is produced by the chain.

The chain view also explains why hiring rarely fixes a plateau. A new head of growth inherits the same joints. A better agency optimises its own link harder, which can even make things worse: more traffic poured into a leaking handoff is more expensive leakage.

What does the full chain look like? #

Six links, five joints. Positioning feeds the site. The site feeds content. Content feeds channels. Channels feed lifecycle. Lifecycle feeds data, and data should feed decisions back into all of it. Loss at any joint discounts everything upstream of it, which is why joint order matters more than link quality.

Walk it forward. If the positioning is unclear, the site says five things at once, so even excellent traffic bounces confused. If the site is clear but content is generic, the channels have nothing distinctive to distribute. If the channels deliver but nothing follows up, lifecycle leaks the demand the channels paid for. If lifecycle runs but the data never comes back as decisions, the whole engine flies blind and repeats its mistakes with confidence.

The compounding is the cruel part. A modest loss at each of five joints multiplies into a chain that delivers a fraction of what its parts suggest. Teams feel this without being able to see it, which is why plateau meetings so often end in mutual, unresolvable frustration.

Which joints carry most of the loss? #

In practice a small number of joints carry most of the loss, and it is usually the earliest broken one. The 80/20 of plateau repair: find the first joint in the chain that fails its test, fix it, and re-measure before touching anything downstream. Upstream repairs re-rate every link after them for free.

The two most common culprits sit at the ends. At the front, the positioning-to-site joint: the business knows what it is but the site does not say it, so every channel pays a confusion tax on arrival. At the back, the lifecycle-to-data joint: demand is captured and then decays in an unworked list, and nobody can see it happening because nobody is measuring decay.

Notice what this means for spend. A business with a broken early joint should not buy traffic, and a business with a broken late joint should not buy more content. Diagnosis ordering is the whole game, which is why we treat plateau work as architecture before tactics, always.

How do you inspect your own engine this week? #

Run the Joint Inspection below. One test per joint, each answerable inside an afternoon with data you already have. Do them in chain order and stop at the first hard failure: that joint is your project for the month, and nothing downstream of it deserves budget until it passes.

The discipline is resisting the interesting downstream fix. A lifecycle automation project is more fun than admitting the homepage claim is mush. Fix the first failure first. The engine will tell you, in revenue, whether the diagnosis was right.

Stop tuning the parts. Walk the joints.

The Growth-Engine Rebuilder use caseHow engagements work