ROADMAP
Gates, not dates.
Retrics ships in gated phases — each opened by proof, never by a calendar. A gate is a floor, not a schedule.
DIRECTION, NOT COMMITMENT · THE SEQUENCE IS THE PROMISE, THE TIMING IS NOT
TODAY
Where each product stands.
Statuses below are the same ones on every product page. When one changes, the changelog records why.
HOW TO READ THIS PAGE
Four rules keep it honest.
A roadmap is the easiest thing on a marketing site to inflate. These are the constraints that stop this one from drifting into wishful thinking.
A gate is a floor, not a schedule.
No phase starts before its gate clears. Clearing one opens the next door — it never sets a date on a calendar we would then be tempted to protect.
Sequence is the promise. Timing is not.
The order below is committed; later phases depend on foundations the earlier ones lay. We would rather be late and honest than early and wrong.
Proof opens doors, not optimism.
Every gate is a measurable threshold — active brands, a published recovery figure once the comparison is rebuilt, an MRR band, a clean safety record — not a feeling that something is ready.
Status is never rounded up.
The pills here and on every product page read from one registry. A product is Live, in Early access, or Coming soon — nothing in between, nothing upgraded to look further along.
THE BUILD ORDER
Five phases. Each opens on proof.
No phase starts before its gate clears, and calendar pressure never overrides a gate. There are no dates on this page on purpose.
PHASE 0A foundation worth trusting
01 / 05Releases, migrations, and app installations made boringly repeatable. Tenant isolation, backups, and observability strengthened. Every consequential action leaves an audit line. Autopilot's automation stays suggest-only, with a kill switch, until later phases earn more.
EXIT GATE · REPEATABLE RELEASES · ISOLATED INSTALLATIONS · EVERY MATERIAL ACTION AUDITED
PHASE 1Prove Retention with design partners
02 / 05Ten repeat-purchase Shopify brands run Retention — free or discounted for three months, in exchange for a weekly call and case-study rights. This phase runs in parallel with the Phase 0 foundation work. Geo grows its Shopify App Store distribution independently. Partner calls steer the order inside each phase; Chat sits outside that queue — it is greenlit and already in build as its own app.
EXIT GATE · 10 ACTIVE BRANDS RETURNING WEEKLY, WITH A RECOVERY FIGURE RETRICS WILL PUBLISH
PHASE 2Campaigns general availability, Autopilot suggests
03 / 05Campaigns — email and WhatsApp — reaches general availability inside the Retrics app. Autopilot launches in suggest-only mode: read-only diagnosis and recommendations, no external changes. Revenue, spend, costs, customers, and conversations come together in one coherent model.
EXIT GATE · $2,000–3,000 MRR
PHASE 3Reviews launches as its own app
04 / 05Reviews ships as a standalone Shopify app, feeding verified UGC into Campaigns and the shared customer graph. Chat no longer waits on this gate — it is greenlit and in build as its own app, on its own database, joined to the graph through versioned APIs. Reviews still depends on the Phase 0 multi-app installation model.
EXIT GATE · $5,000+ MRR
PHASE 4Loyalty general availability, Autopilot earns autonomy
05 / 05Loyalty reaches general availability inside the Retrics app. Autopilot advances one step at a time: approval-based external changes first, then narrowly bounded automation inside explicit policies, budgets, rollback, and kill switches. The full cost and contribution-profit graph — COGS, shipping, fees, returns — completes the picture.
EXIT GATE · PLATFORM VALUE EXCEEDS STANDALONE WEDGE REVENUE · ZERO SERIOUS AUTOPILOT SAFETY INCIDENTS
WHY THE ORDER HOLDS
One brain,
lit one node at a time.
SEQUENCE IS THE PROMISE · TIMING IS NOT
WHAT COMES FIRST
Some work has to come first.
Before any product graduates, the platform underneath it has to hold. These are the foundations every later phase quietly depends on — and the reason the order cannot simply be reshuffled by whoever asks loudest.
PHASE 0 IS THE FLOOR EVERY LATER PHASE STANDS ON
Isolated installations
Every store's data stays walled off. Multi-app installs, OAuth scopes, webhooks, and uninstall state are handled before another app is allowed to launch.
A receipt for everything
Every consequential action — a suggestion, an approval, a send — leaves an audit line before any autonomy is allowed to grow past it.
Autonomy is earned
Autopilot stays suggest-only with a kill switch. Approval-based changes come first, then narrowly bounded automation inside explicit policies — one gated step at a time.
Deterministic proof
Business metrics stay separate from AI reasoning, so a recovery figure is arithmetic over a withheld control, never narration — the one standard every later product is held to, and the reason the figure stays unpublished until that arithmetic counts only the customers a message reached.
WHO STEERS THIS
Design partners order the queue.
What early brands ask for on the weekly call moves up. What nobody asks for waits — with one exception: Chat is greenlit and in build, decided by the plan rather than by the queue. When a phase clears its gate, the changelog records what shipped, so you can judge the pace instead of trusting it.
QUESTIONS
How the roadmap works.
Why are there no dates on this roadmap?
Because a date is a promise about time, and a gate is a promise about proof. We commit to the order of what gets built and to the thresholds that open each phase — not to a calendar we cannot honestly keep. The sequence is the promise; the timing is not.
What exactly is a gate?
A measurable floor that must be true before the next phase starts — for example, ten active design-partner brands returning weekly, and a recovery figure Retrics is willing to publish, or a specific MRR band. No phase begins until its gate clears, and calendar pressure never overrides one.
How can I influence what gets built next?
Become a design partner. What early brands ask for on the weekly call moves up the queue; what nobody asks for waits. Chat is the exception: it is greenlit and in build regardless of the queue, because the plan needs it.
How do I know a phase actually shipped?
The changelog records what shipped and why each time a gate clears. The status pills on this page and on every product page come from one shared registry, so you can judge the pace against what was promised instead of taking it on faith.
Can the order change?
The sequence is deliberate: later phases depend on foundations the earlier ones lay, so it cannot simply be reshuffled. Within a phase, partner demand reorders the queue — but a gate is never skipped to look faster.
What is live today, and what is not?
Retention and Geo are live. Campaigns and Autopilot are in early access. Reviews, Loyalty, and Chat are marked coming soon — Chat is planned with the build underway, as its own app, and Reviews and Loyalty are queued behind it. The pills at the top of this page are the honest, current state, never upgraded to look further along.
Is Autopilot allowed to act on its own?
Not yet. It launches suggest-only — read-only diagnosis and recommendations, with a kill switch and no external changes. It earns approval-based changes, then narrowly bounded automation inside explicit policies and budgets, only as later gates clear with zero serious safety incidents.
Why gate on proof instead of just shipping fast?
Because shipping to look busy is how software quietly lies. A feature that cannot clear its gate is not ready to be trusted with a merchant's customers or budget. We would rather be late and honest than early and wrong.
THE PROMISE
The sequence is the promise.
The timing is not.
Judge the pace instead of trusting it.