Source: https://www.orchestro.org/docs/grow
Updated: 2026-09-30

# Growth work, on a loop.

Updated September 30, 2026[Read as Markdown ↗](https://www.orchestro.org/docs/grow.md)

Campaigns and experiments, run as loops: declared metric, guardrails, owner approvals, measured outcome.

**Design-partner preview.**

Growth loops are being scoped with a small set of partners. The implemented reference is the repair loop; campaign integrations are not shipped. The example below is illustrative.

## One campaign loop, week by week

A team wants more trial sign-ups from content. Their loop declares one primary metric — qualified trials per week — plus guardrails: spend cap, brand voice, and no publish without owner approval.

| When | What changes | What Orchestro retains |
| --- | --- | --- |
| Week 1 | Baseline measured: 40 qualified trials, same offer. | Metric definition, population, window, baseline |
| Week 2 | Two variants drafted; you approve one to publish. | Hypothesis, approved variant, publish receipt |
| Week 3 | 55 trials measured; spend and voice guardrails hold. | Outcome sample; movement recorded, not proof of cause |
| Week 4 | Results favor one angle; the loop proposes round two. | Decision history; losing variant retired with reasons |

## What carries over from the repair loop

*   **Success contracts:** one primary metric plus a few guardrails, declared before work starts.
*   **Approvals stay yours:** spend, publish and voice decisions need the owner; drafting does not.
*   **Doing ≠ certifying:** whoever drafts the variant never declares it a winner alone.
*   **Honest attribution:** before/after movement is movement, not proof the loop caused it.

## Shape it with us

Grow partners bring one campaign or experiment with a metric they already read. We scope the loop together, starting from measurement — never from automation.

[Join as a Grow partner](https://www.orchestro.org/early-access?track=grow)