Skip to content
Ryan Fong

Strategy board

One loop, many products.

Every Armalo mini-app runs the same flywheel: build it onapp.armalo.ai, launch it on its own subdomain, buy attention with paid social on Meta, convert it through a Stripe checkout funnel, and reinvest the profit into more campaigns and the next build.

This board tracks stage and proof only. Spend, revenue, and campaign detail stay in the private operating system.

The loop

Compound feeds build

  1. Build

    Being designed or tested; no public product surface yet.

    Advance when— The public surface is live and verified on its own subdomain.

  2. Launch

    Public surface live on its own subdomain, earning first users.

    Advance when— Real users hold the surface up and a paid campaign has a clear job.

  3. Acquire

    Paid social campaigns are driving measured traffic.

    Advance when— Paid traffic converts well enough to justify switching checkout on.

  4. Monetize

    Paid checkout is live, with business-verified proof.

    Advance when— The funnel covers its own ad spend, with business-verified proof.

  5. Compound

    Profit is funding campaigns and the next build.

    Advance when— Profit is funding campaigns and the next build — the loop restarts.

The board

41products
Build
Launch
Acquire

Open slot.

Monetize

Open slot.

Compound

Open slot.

How it runs

The catalogue is the shared surface of a two-person studio: one loop for building and shipping, one loop for campaigns and the funnel, both meeting here. New mini-apps are vibe-coded in the app.armalo.ai cloud editor and only join this board once there is a real public surface to point at.

Stages only move forward on evidence — the same access and proof discipline the catalogue already enforces. A product cannot claim the compound stage without business-verified proof, so the board never gets ahead of reality.