Early access · for Claude Code and Codex

You build it. zooi grows it.

The AI-native growth system: zooi moves your growth forward daily, sets direction weekly, hands the work to the Claude Code or Codex you already use, and measures what it did.

Request early accessInvite only for now. Email hello@zooi.ai about your product and the agent you use, and we'll send you an invite. Already invited? Sign in with that address. Watch a week in zooi

A week in zooi

A week in zooi

Real screens of zooi.ai. The product, acme.dev, and its numbers are examples.

A recording of zooi.ai: the week's plan arrives in the inbox, is reviewed like a pull request and approved; the week's board fills; a pull request shows as delivered, checked and live; two weeks later a reading is confirmed from the measured numbers.
Connects to
  • GitHub
  • Hacker News
  • PostHog
  • Plausible
  • npm
  • PyPI

01Every week

A growth plan arrives. Review it like a pull request.

Your agent reads the product, the numbers and the playbooks, then proposes this week's moves with the evidence and a measurement plan for each. zooi checks every item against the rules and your time.

  • Campaigns, actions, the reason for each, and what it costs you in minutes
  • Checks: authorization tier, locked objects, your weekly capacity
  • Approve the whole plan, or decline with a reason the next run reads
The plan review page: a plan waiting for approval with its summary, 3 of 5 checks passed, a new campaign with its metrics and hypothesis, and an Approve plan button.

02Then

The work happens where you already work.

Pull requests in your repository. Drafts for your accounts. Facts and talking points where only you may write. zooi checks every receipt before anything counts.

  • Delivered, checked and live are separate records
  • Your agent runs on your machine, on your own subscription
  • Pre-authorize your own repository once: your merge is the approval
An action page: a README quickstart, observing, with its pull request delivered on Oct 26, checked by zooi, live the same evening, and the activity from proposal to delivery.

03Two weeks later

Results are measured, then read. Never claimed.

Every action carries a measurement plan before it runs. zooi reads the metric over its window, your agent drafts the reading, and you confirm it. Confirmed readings shape the next plan.

  • Before and after on a metric you connected
  • A day with no data shows as “–”, never as 0
  • One reading is a hypothesis, not a cause, and zooi says so
A campaign reading page: quickstart completions before 23.86 and after 37.79 a day, a change of +58%, what the measurement rules suggest, the agent's draft and a Confirm reading button.

04Memory and method

It knows your product. It knows the methods.

Confirmed facts with their sources. Numbers connected once. 35 growth playbooks with entry conditions, steps and measurement, picked for your kind of product and its stage.

  • Profile facts stay when you switch agents
  • Playbooks for repositories, docs, launches, communities and pages
  • Your agent follows a playbook step by step and cites it
The product profile with its confirmed facts, and the library of growth playbooks grouped by growth domain.

05The whole lifecycle

All of growth, one system.

Reach, acquisition, activation: every stage has its numbers and its playbooks, and a dashboard across your products shows where to look.

  • Goals, campaigns and actions on one board
  • Numbers by stage, with what moved them
  • Retention and revenuePlanned
The Insights page: numbers by stage for an open-source project, with new GitHub stars, npm installs and quickstart completions over four weeks.

06Your name

Your name, guarded by rules.

Platform rules run on the server, not in a prompt. On Hacker News and Stack Exchange you write every word, from facts your agent prepared. Social posts are drafted and approved one at a time. No cold bulk outreach, ever.

A Hacker News reply waiting for the person: the agent's facts and talking points, the rule that the person writes it, and a field to hand in the link once posted.

Get started

Install, link your product, approve the first plan.

  1. 01

    Install the plugin

    In Claude Code or Codex, inside your product's repository.

  2. 02

    Link your product

    Your agent reads the README as a new user would and proposes the facts. You confirm them.

  3. 03

    Approve the first plan

    Next Monday, a plan is waiting in your inbox.

Install for
claude plugin marketplace add ZooiAI/zooi-plugin
claude plugin install zooi@zooi
# then, inside your product's repository
/zooi:onboard
codex plugin marketplace add ZooiAI/zooi-plugin
codex plugin add zooi@zooi
# then, inside your product's repository
$zooi:onboard

FAQ

Questions, answered plainly.

We grow zooi.ai with zooi.ai. It is product zero: an ordinary product, in the same loop as yours.

Does zooi run its own AI?

No. Planning, writing and analysis happen in your agent, on your own subscription or API key. zooi runs deterministic programs: it collects data, checks plans, schedules, verifies and measures.

Do I have to move my website?

No. Your repository, docs and existing site stay where they are. zooi hosts no pages; your agent changes yours through pull requests you merge.

Which agents does it work with?

Claude Code and Codex, through the open-source zooi plugin and an MCP connection you authorize.

What kind of product is it for?

It starts with developer and AI tools whose product lives in a GitHub repository. The goal is any kind of product.

Does zooi store my users?

No. It takes in the counts and sources your own signup or booking features produce, never the people.

What does it cost?

It's free during early access. Paid plans will come later, and we'll tell you before anything changes.

Give your product a growth loop.

Install the plugin, link your repository, and review your first weekly plan.

Invite only for now. Email hello@zooi.ai about your product and the agent you use, and we'll send you an invite. Already invited? Sign in with that address.