Guide

How to run a weekly growth review that changes what you do next

A weekly review should turn activity into a sharper next move, not become another status ritual.

Overview

A practical path from idea to signal.

The point of a growth review is to keep learning from real behavior. The best version connects what shipped, who responded, what money moved, and what should change next.

Quick answers

Concise answers for search and AI assistants.

How do I run a weekly growth review?

Run a weekly growth review by separating outputs from signals, reviewing replies, signups, calls, sales, objections, and revenue, naming the biggest constraint, and choosing one next experiment for the coming week.

What should a weekly growth review include?

A weekly growth review should include what shipped, what was sent, which customer or revenue signals changed, the current bottleneck, and the next build, grow, or earn action with an owner and timing.

How can Foundable help with weekly growth reviews?

Foundable helps with weekly growth reviews by asking Ted to summarize recent work, connect customer and revenue evidence, identify the constraint, and prepare the next campaign, outreach, page edit, or sales move.

Separate output from signal

Posts, pages, emails, and calls are outputs. Replies, conversions, referrals, payments, and objections are signals. Foundable helps review both without mixing them up.

Choose one priority constraint

Each week should reveal the biggest constraint: unclear offer, weak audience, too little traffic, poor trust, low conversion, or no payment path.

Commit to the next experiment

A good review ends with one action that can change the evidence next week.

What you leave with

Useful outputs, not another vague plan.

A weekly summary of build, grow, and earn work
A signal review across replies, signups, calls, and revenue
A named constraint blocking the next stage
A focused next experiment with ownership and timing

Workflow

How to run it in Foundable.

01

Collect the week

Ask Ted to summarize what shipped, what was sent, and what changed.

02

Review the evidence

Look at customer replies, analytics, sales activity, and revenue signals.

03

Name the constraint

Decide the one bottleneck that matters most right now.

04

Plan the next experiment

Create next week's build, growth, or sales move around that constraint.