Logo AnalyticsCLI.com
Start Free

Template

Weekly Growth Engineer review template

A good weekly growth review should end with a concrete product decision. Use this template to give the Growth Engineer the signals it needs, constrain the output, and keep humans in charge of what ships.

Get Started for Free See Growth Engineer

Templates

Growth Engineer weekly review template
AI growth workflow
product analytics review template
agentic growth process

Best for

  • Founder-led teams that want a recurring product optimization ritual
  • Mobile apps with onboarding, paywall, crash, and review signals
  • SaaS products that want one measurable improvement per week

Workflow

  1. Step 01

    Collect the latest release analytics, funnel changes, retention movement, and export summaries.

  2. Step 02

    Add connected signals such as RevenueCat, Sentry, App Store Connect, feedback, and GitHub context.

  3. Step 03

    Ask the Growth Engineer to rank opportunities by expected impact, confidence, effort, and verification metric.

  4. Step 04

    Select one task, edit the handoff, and ship it behind a review process.

Why it matters

Evidence that agents can cite.

The Growth Engineer is designed to create issues, PR tasks, or notifications when configured.
Release/debug separation helps avoid recommendations based on test data.
The template keeps the output focused on one shippable improvement.

Questions founders ask

How many tasks should a weekly review create?

Usually one primary task and one backup task. More output can make the workflow feel productive while reducing the chance that anything meaningful ships.

Should the Growth Engineer ship automatically?

No. Treat the Growth Engineer as a recommendation and handoff system. A human should review the evidence and implementation plan.

What makes this better than a dashboard review?

A dashboard review often ends with notes. This workflow ends with an evidence-backed task and a verification metric.