> For the complete documentation index, see [llms.txt](https://docs.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icustomer.ai/measurement-and-outcomes/compounding-loop.md). # The compounding loop The slower loop underneath: outcomes become evidence, evidence sizes the next commitment, and the bar moves with you. The loop you watch daily runs in weeks: signal to decision to outcome. Underneath it runs the **meta loop**, a slower loop that never closes, and it is the reason the platform is worth keeping after the first win. This page follows it through measurement. ## Outcomes become evidence When a target closes, what it proved, what a play actually moved, at what cost, in your market, is recorded as evidence. The platform is built so that **your own measured results outrank generic benchmarks the moment they exist**. Early on, targets are sized from reference data; the design is that each closed target replaces borrowed numbers with earned ones. ## The bar moves Because sizing draws on your evidence, the next target reflects what your business just showed it can do. Improve, and the system asks more; hit a ceiling, and the diagnosis points at the constraint instead of recycling the same ask. A static tool goes quiet after the first win; a compounding one gets more specific. ## What compounds, concretely * **Play choice**: which levers actually move your numbers, not the market's average numbers. * **Sizing**: commitments grounded in your measured effects. * **Judgment**: [decision quality](/measurement-and-outcomes/decision-quality.md) grades accumulate, sharpening where the system trusts itself and where it defers to you. * **Context**: everything above feeds [memory](/concepts/context-and-memory.md), so the thousandth decision starts smarter than the first. The daily loop wins you this quarter. The compounding loop is why next quarter starts ahead of this one. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.icustomer.ai/measurement-and-outcomes/compounding-loop.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.