You automated your build. Your growth is still manual.

Mike Khristo is CEO and co-founder of Layers.

In July Liam Du wrote here about taking Wellspoken from 400 users to hundreds of thousands of downloads. At the end he lists what he learned, and the first lesson is that growth is a portfolio: no single channel got him there, several smaller wins stacked up.

That's true. I'd add one thing to it.

Read his story again and the components are wired together. Retention and engagement lift his App Store ranking, the ranking brings installs, and those installs produce the signals that lift the ranking again. His UGC operation finds a format that converts, the converted users leave reviews, and the reviews make the next batch of content convert better.

Every output is feeding an input. That's a loop, and he built a good one.

Most people run the same components as a checklist. The distance between those two things is most of the gap between apps that compound and apps that plateau.

Funnels end. A loop feeds itself.

A funnel is a sequence with an exit at the bottom. Traffic arrives, a fraction converts, and the only way to get more out is to put more in at the top. Every gain is linear and every gain is bought.

A loop routes its own output back to its own input. Users generate something (retention data, reviews, content, referrals) that makes the next cycle cheaper than the last one. The compounding is structural.

You already think this way. Your CI pipeline is a loop: a commit triggers a build, the build runs tests, the tests gate the deploy, the deploy produces telemetry, the telemetry shapes the next commit. Nobody would run those five stages as separate manual jobs with a person carrying artifacts between them. But that is how most apps run growth.

The three loops most apps can actually run

The store loop. Installs create behavioral signals that can help the stores understand which results are useful, while ratings, reviews and app quality can also affect discovery. Better visibility can then produce more installs. The interesting recent change is semantic relevance. In February 2026, Apple published research on an LLM-assisted App Store ranker that balances behavioral signals with how well an app actually matches a search. Its largest gains were on tail queries, where there's less historical behavior to learn from.

For a new app, that strengthens the case for targeting specific, semantically clear searches rather than relying only on broad category terms. Cycle time: weeks.

The content loop. You build something, capture it, post it, see what lands, make more of what landed. In a dataset of 23 million short-form videos, a follow-up on the same topic at the same length after a hit earned roughly 36% more views than switching subjects. The window is generous at first, so two hours later and four days later perform about the same, then it shuts after about a week. Cycle time: days.

The proof loop. Usage generates reviews and user content, that social proof raises conversion, and the higher conversion brings more usage. Liam's point about review prompts is the right one: the prompt harvests sentiment about the product already created. The loop only runs if the product earns it. Cycle time: continuous.

Notice the pattern. The content loop has the shortest natural cycle time of the three, and for most solo developers it's the one running slowest, because it's the most manual.

Loops fail in two places

Latency. A loop compounds at the rate it completes cycles. If you need two weeks to work out what performed, the context that made it perform has already moved. This is why the sequel window matters: the advantage is real and it expires. A winning post is evidence about a moment. Platforms tell you what worked and none of them tell you why.

Handoffs. Every point where a human copies context from one tool into another is a place the loop stalls. Keyword research lives in one place, content in another, scheduling in a third, ad platforms in a fourth, analytics in a fifth. The connective tissue is you, at 11pm, pasting things between tabs. Liam solved this with dozens of creators and a campaign manager, which works and is completely out of reach for most people reading this.

Why we built Layers

This is the part where the parallel to Expo is hard to miss.

Ten years ago, shipping cross-platform meant maintaining a toolchain: the right Xcode on the right machine, signing, submission, a separate "everything" for Android. Most of that work was connective tissue, and the connective tissue was a person. EAS collapsed it. A solo developer can now run an app at hundreds of thousands of users without opening Xcode because the steps between commit and store stopped needing someone in the middle.

The growth stack sits roughly where the build stack was. Same shape of problem, same disconnected steps, same person in the middle. We started Layers to close those handoffs, and one belief drives the design: generative systems are only as good as the structured context they get before they generate. Brand guidelines and a URL are thin context. Your codebase, your store listing and your usage data are thick context, and they're already sitting there.

That's the product argument and I'll leave it there. The useful part holds regardless of what you use: optimize for cycle time and number of handoffs.

What to do on Monday

Draw your loop. Four or five nodes, arrows showing what feeds what. Most people find they have a funnel with a hopeful arrow at the end.

Time each leg. How long from shipping a feature to content about it going live? From a post landing to a follow-up? From a retention gain to seeing it in your ranking? The slowest leg sets your compounding rate.

Remove one human handoff. Pick the leg with the worst ratio of time spent to judgment required. That's almost always a copy-paste step, and it's usually the one blocking the content loop.

Feed it something you're currently throwing away. Every app produces raw material continuously and most of it gets used once and deleted. Your changelog is content. Your support inbox holds the exact words people use to describe the problem, which is where your store copy and your keywords should come from. Generated output can carry the volume. The raw material has to come from you, and it's most useful the week it appears.

The loop is already there. The question is how fast it turns.