A feedback loop feeds a system's output back into its own inputs, so the system improves from its own results instead of standing still. It's the only component of the Scaffold Model that compounds. Anyone can copy your prompt and call your model. Nobody can copy the months your loop spent correcting itself.
01 / Why is the model never the moat?
Because access is equal. The same model you call is one API key away from every competitor you have. Whatever advantage the raw model gives, it gives to everyone at the same price, on the same day.
A better model doesn't change that. When the next model ships, it raises the floor for the entire field at once. You get sharper, and so does everyone who upgrades. Nothing about a shared model can separate you from the people sharing it.
The model is the floor everyone stands on. It was never going to be the thing that lifts you above them.
02 / What actually compounds?
The loop. It's the one component built from things that aren't for sale: your data, your signal, and time. Each pass makes the next pass better, and that improvement stacks in a direction no competitor can shortcut.
| A better model | A running loop |
|---|---|
| Raises the floor for everyone at once. Available to your competitor the moment it ships. An upgrade, not an advantage. The gap between you and a copy stays exactly where it was. | Raises your floor alone, from signal only you have. Unavailable at any price because it's made of time. The gap between you and a copy widens every week it runs. |
Tool access is bought in an afternoon. A loop is earned in months. That asymmetry is the whole game.
03 / How does a feedback loop actually work?
Four stages, and the fourth feeds the first. That's what makes it a loop instead of a line. Miss the return path and you have a pipeline that runs once, not a system that improves.
01. Produce
The system generates output. This is the part everyone builds and the part everyone stops at. On its own it's a pipeline, not a loop.
02. Capture
You record what was produced and what happened next. Not just the output, but the outcome: did the user accept it, edit it, ignore it, act on it? The outcome is the signal.
03. Judge
You decide whether the output was good, using the signal you captured. This can be a rating, a rule, or a downstream result. The judgment turns raw output into a lesson.
04. Adjust
You feed the lesson back into the inputs, so the next run starts smarter. New examples, tighter constraints, a changed default. Then it produces again, and the loop closes. Adjust feeds back to Produce, and the cycle starts over one step better.
04 / How do you close the loop cheaply?
You don't need a training pipeline to start. You need one honest signal, captured consistently. Most builders skip the loop because they imagine it's expensive. The cheap version works, and the cheap version compounds too.
- Pick one signal you already generate: an accept, an edit, a reply, a conversion.
- Capture it every time, not occasionally. Consistency matters more than volume.
- Feed the clearest cases back as examples or rules before you build anything automated.
- Automate the return path only once the manual version has proven the signal is real.
A loop closed by hand still compounds. The expensive version is a reason people never start, not a reason it doesn't work.
05 / Frequently asked
Read next
- The Scaffold Model. The pillar. Why you architect the system around the model, not the prompt inside it.
- Prompts are not the system. The five components that sit around the prompt, and the failure you get when each is missing.
Want a loop that compounds?
Conversion landing pages and AI automations from €500. I close the loop so the system gets better while your competitors stand still. Same outcome your agency promises, in days instead of quarters.
Drop me a line →