More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Growth Review: Zero-Cost Revenue Playbook

    2

    Find the one thing holding your revenue back, from your own Stripe, Paddle, Lemon Squeezy, Gumroad or Shopify exports, and get a 90-day playbook of moves that cost time, not money. 8 Python check scripts.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    5.0 (1 review)
    Growth Review: Zero-Cost Revenue Playbook

    Growth Review: Zero-Cost Revenue Playbook

    Example session with this skill installed

    We're an AI meeting-notes tool for small agencies, 19/49/129 USD a month, no ad spend. I want 48,000 USD MRR within a year and have about 15 hours a week. Attached: our Stripe payments export (all statuses), AI inference cost per customer for three months, and monthly funnel counts. Review our growth and write a playbook.

    • Read your context and instructions
    • Compiled the growth review

    I ran check_exports.py, revenue_metrics.py, cohort_retention.py, funnel_check.py, unit_economics.py, pricing_check.py and revenue_levers.py on your exports.

    The answer

    MRR is 24,182 USD and growing 5.7% a month, but at today's acquisition and churn it levels off near 42,900 USD, below your 48,000 goal. The constraint is early retention: 65% of a year's customer losses happen by month 3, and only 33% of sign-ups connect a calendar. A quarter of churn (42 of 165 in six months) follows a failed card: fix that first, it is free.

    Playbook (zero cash)

    #MoveEvidenceHoursRead onStop if
    1Payment retries, card-update and expiry emails25% of churn follows a failed payment2 once1 Jancomplaints about the emails
    2A finished sample note before calendar setup; day 1, 2 and 5 emails to non-connectors33% connect a calendar5 a week11 Jancalendar rate not above 36%
    3Fair-use limit on Team, a plan for heavy users14 customers cost more than they pay3 a week2 Febmore than 3 of 14 cancel
    4Grandfathered Pro (29 USD) to 49 with 60 days' notice26 customers, about 500 USD MRR2 once31 Marmore than 5 of 20 cancel

    The goal

    With moves 1 and 2 working (churn down 30%, half of failed cards recovered), month-12 MRR is about 40,000 USD. 48,000 also needs about 30% more new customers a month; that combination crosses it in month 13. A/B testing the calendar step would take about 31 weeks at your traffic, so we measure before and after against your six-month history.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most growth advice is a list of tactics. This skill starts with your numbers: it reads the billing exports you already have, finds the single constraint on your revenue, and turns it into 3 to 5 moves that cost hours, not money, each with a metric and a date to judge it. It works in Claude Code, Codex and any agent that reads SKILL.md.

    What it does

    • Measures where revenue comes from and where it leaks. MRR and its movements (new, expansion, reactivation, contraction, churn), churn that follows a failed card, net and gross revenue retention, the quick ratio, and concentration. For shops and one-off products: repeat purchase, days to second order and returning revenue.
    • Finds the ceiling. The level where MRR stops growing at today's acquisition and churn. If your goal is above it, the skill says so plainly and models which combination of levers gets there, and by which month.
    • Shows where customers leave. Cohort retention by start month, the funnel step that loses the most people who already signed up, and whether churn is front-loaded (an onboarding problem) or steady (a value problem).
    • Checks the money per customer. Margin per customer and per plan, including AI inference costs: the heavy users who cost more than they pay, and the free or churned accounts still using the product.
    • Finds revenue you already earned. Failed payments nobody retried, customers still on old prices, discounts nobody ended, with the break-even for each price move.
    • Writes the playbook. Each move has the evidence, cash cost (zero), hours a week, the metric today, a read date and a stop rule. It drafts the first one (dunning emails, a price-change notice, an onboarding sequence) for you to approve.

    8 scripts, standard library only, no network

    check_exports.py (what your exports contain), revenue_metrics.py, cohort_retention.py, funnel_check.py, unit_economics.py, pricing_check.py, revenue_levers.py (which lever moves revenue most, with scenarios) and experiment_plan.py (whether an A/B test can work at your traffic). Stripe payments, subscriptions and invoices, Paddle, Lemon Squeezy, Gumroad, Shopify and Recurly exports are detected automatically; any CSV with a customer, a date and an amount works.

    Honest benchmarks

    Every benchmark was checked at the organisation that collected the data (November 2026), with sample, date and an evidence grade, plus a list of popular figures that turned out to be unsourced or misquoted. Your own history comes first; benchmarks are context.

    Private by design

    Customer ids and emails are hashed on load and never printed. The scripts make no network requests and read no environment variables.

    What it will not do

    Invent benchmarks or a growth score, promise revenue, recommend ad spend you said you do not want, or email customers, change prices or edit billing settings without your go-ahead.

    Works from your exports, so its numbers are only as complete as they are: failed payments must be in the export to measure involuntary churn, and 13 months are needed for 12-month retention. MRR from payment exports is an approximation; reconcile it with your billing platform's MRR. The levers model is arithmetic on today's rates, not a forecast. Benchmarks were checked in November 2026; re-check anything older than six months. Not legal, tax or accounting advice.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Requires

    Python 3.8+ (standard library only)
    Google Analytics MCP

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Shell: runs the bundled Python scripts on your exports. Read files: billing, cost and funnel exports you provide. Write files: the review and the scripts' report files, only where you ask. Network: none; the scripts make no requests. Environment variables: none are read. Customer ids and emails are hashed on load and never printed.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    It computes your numbers first: MRR movements, churn after failed payments, cohorts, margin per customer and the ceiling your current rates imply. Every recommendation points at a number from your own exports, with a metric and a date to judge it.

    A billing export is enough to start: Stripe, Paddle, Lemon Squeezy, Gumroad, Shopify, Recurly or any CSV with a customer, a date and an amount. Per-customer AI or usage costs and monthly funnel counts make the review sharper. Without any data, it runs a first-customers plan instead.

    Yes. Shops and one-off products get repeat-purchase and cohort analysis, service businesses get utilisation, rate and concentration checks, and pre-revenue founders get a 30-day plan for the first paying customers.

    The scripts run locally, make no network requests, and hash customer ids and emails on load, so reports never contain them. It can also write a hashed version of your export that is safe to share.

    No. It drafts the price notice, the payment-recovery emails or the onboarding sequence, and you decide. Anything that reaches customers needs your go-ahead.

    Yes. It joins inference costs to revenue per customer, finds the heavy users who cost more than they pay, includes usage by free and churned accounts in the real margin, and sets fair-use limits and overage prices from your own cost data.

    New in Research & Analysis