# Growth motions: the plays that fit your business, and what each needs

> Growth motions are the plays a business wins customers with. Your AI growth team picks the ones that fit you now, and says what each one still needs.

Canonical: https://www.runtheworld.ai/guides/growth-motions-for-your-business

Updated: 2026-10-21

## A motion is a play your business can repeat

A motion is a repeatable way a business wins, keeps or grows customers, like asking for reviews, winning back people who stopped, or running a seasonal promotion.

Your growth team picks the motions that fit your business's stage and says what each one needs. On your team page, Which motions fit? shows how many are ready and how many wait on a step.

## Ready, or waiting on something

Each motion that fits shows as Ready, or with how many things it waits on. Ready means everything it needs is in place, so the team can propose it now.

The team can still propose a motion that waits on something, and it says what it waits on.

## Every need says who can sort it out

Each thing a motion waits on says who meets it: a connection, your engineers, or you.

- Connect: something Runner can check once it's connected, like a verified sending domain.
- Your engineers: a change to your website or app.
- You decide: things only you can choose, like a real offer for a seasonal sale, a launch date, or the review site your business is judged on.

## Your stage is your revenue, read from Stripe

Your stage is your monthly revenue, read once a day from your own Stripe account and never estimated.

Motions that pay off at a later stage are listed as Later, so you can see what's ahead. Until Runner has a revenue reading, the motions that pay from the Traction stage up wait.

Motions that don't suit the way you sell aren't shown, like a save-at-cancel step for a business with no subscription. If Stripe shows no revenue yet, or while you run a waitlist, the team also works from a pre-launch playbook.

## With or without engineers

Without code connected, you still get plain steps to hand your engineers. Connect your code, and the team names the exact change for your stack.

With your code connected, you can also ask for the change as a pull request. An owner or admin approves it first, and Runner's GitHub App needs permission to write to your repository.

If your business has no code, the team never asks you to connect any, and offers only connections and your own decisions.

## Running a motion, inside your rules

When one of your leads runs a motion, its drafts are written to that motion's rules: a review is never paid for or rewarded, and a sale ends when it says it ends.

For some ready motions, you can start a ready-made journey. It starts as a draft and sends nothing until an approved email is picked, and only people who agreed to hear from you enter it.

Motions are advice, never a gate: your approvals, consent rules and spending limits still decide. Nothing goes out until you approve it or switch the team on, and then only inside the limits you set.