RETRICS — COMPANY
Twelve products.
One proof standard.
Twelve products. One proof standard underneath.
Predicts who buys again, and when
Quantity breaks checkout honors
Gifts priced $0 at checkout
Thank-you page upsells, one click
Order, payment and delivery rules
In-cart upsells, free-shipping bar
Preorder buttons, restock emails
Country redirects, store locator
Purchase-verified photo reviews
Answers, sells, acts, hands off
Keeps bots out of your numbers
Finds leaks, refuses doomed tests
STATUSES MATCH REALITY — NOTHING HERE CLAIMS CUSTOMERS IT DOESN’T HAVE
TWELVE PRODUCTS · ONE PROOF STANDARD
What one learns,
the rest can use.
ONE CUSTOMER GRAPH · ONE PROOF STANDARD · STATUSES MATCH REALITY
THE SHARED GRAPH
One graph, not a mesh of integrations.
Most suites are a bundle — separate tools with separate data, stitched together after the fact. Inside Core, Retention and its capabilities use one customer graph. Reviews is planned to join it when it ships; Geo and Chat keep their isolated boundaries and integrate explicitly.
15 CONNECTIONS TO KEEP IN STEP
Separate data in each tool, reconciled after the fact. Every new tool adds another edge to every tool already there.
6 READS FROM ONE PLACE
One customer, one record. A new product inherits what is already known instead of opening a new copy of it.
One customer graph
Inside Core, Retention and its capabilities use the same order and customer record. Reviews is planned to join that graph when it ships; Geo and Chat remain isolated and cross boundaries only through versioned APIs or aggregate events.
One proof standard
Every product answers to the same standard: a controlled send freezes its audience, withholds a control that is never messaged, and is read against that control’s own observed return rate; an audience too small to split carries no control at all and is read observationally against the fixed natural-return floor instead. One standard in every corner of the suite — and until the comparison counts only the customers a message actually reached, the recovered-dollar figure stays withheld rather than estimated.
It ships as merchants ask
Retention and Geo are live; the rest are in early access or on the way. A new Core product can join the graph that already exists; an isolated product integrates through a bounded contract instead of a direct database connection.
01 — OPERATING PRINCIPLES
Rules we don’t trade away.
The numbers are deterministic
Revenue, cohorts, and retention come from reproducible arithmetic on your ledger — around 130 SQL-backed metrics, never a model’s narration. The recovered-revenue figure is withheld today. The holdout is still carved and never messaged on every eligible send, so the evidence accumulates — but the comparison is being rebuilt to count only the customers a message actually reached, and Retrics won’t publish a dollar measured over anything looser.
The machine ranks. You write.
AI reads the store and ranks the move — the segment, the moment, the dollars at stake. AI drafting is off today: Retrics won’t send model-written copy until it can mechanically prove a draft carries no discount, deadline or offer you never authorised. You write the message — the audience, the holdout and the campaign-safe export are unchanged.
AI DRAFTING OFF · YOU WRITE THE MESSAGEAutonomy is earned
Every capability starts by suggesting. It graduates to acting with your approval, and only then — inside hard limits, with a kill switch — to acting alone.
Every action has a receipt
Suggestion, approval, execution, outcome: one auditable trail. If an outcome can't be attributed, it isn't counted.
02 — HOW WE WORK WITH MERCHANTS
Early, and honest about it.
Statuses are the truth
Live means you can run it on your store today. Early access means there is a build behind an entitlement, and the first brands on the list shape what ships. Coming soon means you can’t run it yet — Chat is planned with the build underway, Reviews is queued behind it, and the waitlist shapes what each one ships with.
No borrowed proof
There is no logo wall on this site because we haven't earned one. Concept interfaces are labeled as concepts. Illustrative numbers say so, in writing, next to the number.
Merchants set the order
Inside a phase, merchants set the order. A waitlist request is not a marketing email signup — it is the demand signal that moves a product up the build queue. The sequence itself is ours to defend: Chat is planned and in build because the plan needs it, not because the list voted.
A direct line
Write to hello@retrics.ai. Mail goes to the people building the product, and it gets read.
03 — CONTACT
Two addresses. Both read.
Retrics builds and operates the product. Legal notices and written correspondence: legal@retrics.ai.
QUESTIONS
Straight answers about us.
What is Retrics?
Retrics is 12 AI-native products for Shopify brands, each installed and priced on its own. Retention and its five capabilities read and write one customer graph today; all 12 report against the same standard — a number your own orders cannot settle is a number they do not show.
Do I have to buy all of them?
No, and nothing is bundled. Each product is its own Shopify App Store listing with its own price, installed on its own. Start with the one that matches the problem you have now; add another when it earns its place.
Why buy these from one company instead of the best-of-breed app for each?
Because the apps you already run cannot be compared to each other. Each reports its own win in its own frame, and the wins add up to more than the store made. Every Retrics product answers to the same standard and reports against the same orders, so what two of them claim can be put side by side. If that is not worth anything to you, buy one of ours and the rest elsewhere — they are separate listings for exactly that reason.
Who makes Retrics?
Retrics is built and operated by the team behind retrics.ai. The people who read hello@retrics.ai are the same ones building the product — there is no outsourced layer between you and the makers.
What does “twelve products, one proof standard” actually mean?
Twelve customer-facing products: Retention, the six AOV Boosters apps, and five specialists. 6 entities — Retention and its five capabilities — read and write a single customer graph today. Reviews is planned to join that Core graph when it ships. Products outside it share the standard every number is held to; Geo and Chat cross their data boundaries only through versioned APIs. The count is evidence of breadth; the standard is the claim.
How do the products share one graph?
Inside Core, Retention scores each customer’s reorder cadence, Campaigns targets that same cadence, and Autopilot reads the same store record rather than a drifting copy. Reviews is planned to join that Core graph when it ships. Geo and Chat stay in isolated databases and exchange only bounded, versioned API data or aggregate events.
What is live today, and what isn’t?
Retention and Geo are live — you can run them on your store now. Campaigns, Tiers & Rewards and Autopilot are in early access, shaped by the first brands on the list. Reviews and Chat are coming soon: Chat is planned with the build underway, in its own app, and Reviews is queued behind it. Statuses on this site match reality; nothing here claims customers it doesn’t have.
What’s the relationship between Retrics and retrics.ai?
Retrics is the product; retrics.ai is where it lives on the web and how you reach the team. Product, partnership, billing, and press mail goes to hello@retrics.ai; security reports to security@retrics.ai; legal notices to legal@retrics.ai.
Why is there no logo wall or customer list?
Because we haven’t earned one yet. There is no borrowed proof on this site: concept interfaces are labeled as concepts, illustrative numbers say so next to the number, and we don’t publish customer counts or testimonials we can’t stand behind.
How does Retrics decide what to build next?
The sequence comes from the platform plan, and merchant demand reorders the queue inside it. A waitlist request is a demand signal, not a newsletter signup — it moves a product up the build queue. Some products are built because the plan needs them: Chat is planned and in build without waiting for a vote.
How do I reach the people building it?
Write to hello@retrics.ai for anything — product, early access, partnerships, press, or billing. Security questions and vulnerability reports go to security@retrics.ai, and legal notices to legal@retrics.ai. Mail is read by the people building the product.
Enough about us.
Go see your numbers.
Connect a Shopify store and read your own ledger.