Weekly Growth Engineer review template
End every weekly review with one concrete product decision—not another dashboard note.
Growth loop preview
Agent workflow in 60 seconds
OpenClaw and the Growth Engineer: signals in, reviewed issues and PR plans out.
A weekly workflow for turning analytics, RevenueCat, Sentry, App Store reviews, feedback, and GitHub context into one reviewed growth task.
Who this is for
Start here if the problem below sounds familiar. You do not need every connector on day one—just enough signal for the Growth Engineer to propose work you can review.
- Founder-led teams with a weekly optimization ritual
- Mobile apps with onboarding, paywall, crash, and review signals
- SaaS shipping one measurable improvement per week
How it works
The loop is the same across guides: connect evidence, let the agent read it, then ship a reviewed task with a verification metric.
- Collect release analytics, funnel changes, retention, and exports.
- Add RevenueCat, Sentry, App Store, feedback, and GitHub context.
- Rank by impact, confidence, effort, and verification metric.
- Pick one task, edit the handoff, and ship after review.
What you get back
The output should be concrete enough to review without opening five dashboards.
- Creates issues, PR tasks, or notifications when configured.
- Release/debug separation avoids test-data recommendations.
- One shippable improvement per run.
Common questions
Quick answers before you connect product data to an agent.
How many tasks should a weekly review create?
Usually one primary and one backup—more tasks often means less ships.
Should the Growth Engineer ship automatically?
No—humans review evidence and the implementation plan.
What makes this better than a dashboard review?
It ends with an evidence-backed task and KPI—not notes.