FIG. 01 — AFTER LAUNCH
Launch was the starting line.
Three weeks after launch, every founder asks the same question: “now what?” You shouldn’t have to guess. The Growth Package runs the Compound Loop as a subscription — every month, the data picks the next move, you approve it, and it ships. Friday deploys, unchanged.
For Sprint and Accelerator graduates — and for any post-launch team whose roadmap has quietly become a guess.
FIG. 02 — THE COMPOUND LOOP
The data decides. You approve.
COMPOUND is stage six of the Omega Method — the only stage that repeats. Each cycle is the method in miniature: one loop, every month, on evidence. Not five bets. One — with its proof attached.
- 01 — DATA REVIEWWEEK 1
We read what your product earned.
Metrics against your Omega Statement, user interviews, support-ticket themes. You do nothing yet.
- 02 — ONE BET CHOSENWEEK 1 · DAY 5
The evidence nominates. You approve.
A 60-minute Loop Session: you see the evidence, the bet it points to, and the metric it should move. The mini Omega Statement gets signed.
- 03 — BUILD + FRIDAY DEPLOYSWEEKS 2–4
The bet goes to production.
Friday deploys, demo links, changelogs — the Sprint cadence you already know, continued.
- 04 — MEASUREMONTH END
One page. Misses included.
Metric movement, what we learned, the next bet — reported in the same type whether it moved or didn’t. The report feeds the next review.
We don’t ask what you’d like next. We ask what the data earned next.
Not a bag of hours. Not a ticket queue. Every bet has to cite its evidence — the metric it moves, the user behavior behind it, the tickets that back it. Two artifacts every cycle: the signed mini Omega Statement going in, the one-page report coming out — misses included, in the same type as the wins.
FIG. 03 — THE CADENCE
You always know what week it is.
No status-call theater. Two fixed meetings a month — the Loop Session and nothing else you didn’t ask for — and a deploy every Friday you can click.
- WEEK 1
Evidence review — metrics, user behavior, ticket themes, read and weighed.
LOOP SESSION · 60 MIN + DEPLOY - WEEK 2
Build — the signed bet in progress.
DEPLOY + DEMO LINK - WEEK 3
Build — working software, not status updates.
DEPLOY + DEMO LINK - WEEK 4
Ship + measure — the bet lands, the numbers get read.
DEPLOY + REPORT DELIVERED
EVERY FRIDAY: A LINK, NOT A SLIDE DECK
FIG. 04 — TERMS, IN PLAIN TYPE
Easy to start. Easy to stop. That’s on purpose.
Monthly, in advance. $12,500/mo, flat. No hourly billing, no true-ups.
3 months. Long enough for the loop to compound once; short enough to be a decision, not a marriage.
Month to month. Stop with 30 days’ notice.
Pause once per 6 months, up to 1 month, with 2 weeks’ notice. Fundraises and freezes happen; we’d rather pause than pretend.
Your code, your accounts, your data — from day one, so leaving is a meeting, not a migration. Clean handover promised in writing: docs current, credentials yours, last report delivered.
If we’re not earning the next month, we shouldn’t get it.
When the backlog outgrows the monthly capacity two months running, the honest move is the Scale Package — a dedicated squad on a quarterly rhythm. We’ll raise it before you have to.
FIG. 05 — STRAIGHT ANSWERS
Retainer questions, answered like terms.
What does the monthly capacity actually cover?
A fixed monthly capacity of senior design + engineering, spent on the month’s signed bet plus continuous deployment, monitoring, and dependency upkeep. What it never covers: unbounded “just add this real quick” — everything routes through the Compound Loop. A full new product is a new Sprint, and we’ll say so.
Can we pause the retainer?
Yes — once per 6 months, up to 1 month, with 2 weeks’ notice. The product keeps running (deploys freeze, monitoring doesn’t), and the loop picks up where it left off.
How do we stop, and what do we get on the way out?
30 days’ notice after the 3-month initial term. Everything already lives in your repo and accounts, so offboarding is: final report, docs check, credential confirmation, done. No hostage code, ever.
What if we want more than one bet a month?
Then the data is telling you something. One bet keeps the loop honest — but when the backlog outgrows the capacity two months running, that’s the signal to move to the Scale Package ($32,000/mo): a dedicated squad, same method, quarterly rhythm.
- A second product line? A new 4-Week MVP Sprint →
- Backlog outgrowing the month? Scale Package →
- Leadership, not capacity? Fractional CTO →
FIG. Ω — THE END STATE
After launch: compound, don’t guess.
Bring last month’s numbers. In 30 minutes we’ll read them together and sketch your first Compound Loop cycle — what the data says to build next, and why.