Does Oikos run on the whole web book?

Yes. Oikos runs across the connected web book, so subscriber treatment, reporting, lifecycle logic, and billing operations stay consistent. If you already have web billing, that usually makes you a stronger fit — we extend the rail you already have, then bring app-store cohorts onto it over time.

How is Oikos different from CRM or lifecycle tooling?

CRM and lifecycle tools usually target segments and trigger campaigns. Oikos connects subscriber signals, branded surfaces, billing events, and payment outcomes, so decisions become actions on your rail and feed back into the next motion.

What role does Kairos play?

Kairos is the decisioning engine inside Oikos. It reads subscriber signals, decides the next approved motion for each subscriber, and learns from outcomes across payments, renewals, saves, upgrades, and win-backs.

Recurr OikosGrowth platform

Grow your whole book, on a platform you own

Q: What does Oikos include?

Oikos includes the operating layer for your connected web book — subscriber surfaces, billing and account flows, lifecycle motions, Kairos decisioning, cohort reporting, and the integrations needed to run them.

Once your book is home, Oikos runs the surfaces, lifecycle motions, and Kairos decisioning that grow every subscriber from first touch to lifetime value.

Run the audit See pricing

Operating Layer

Everything the web book runs through

Oikos is the standing platform for your connected web book — subscriber surfaces, billing and account flows, lifecycle motions, Kairos decisioning, and cohort reporting in one operating layer.

Your web book

subscribers · plans · events · outcomes

Oikos

operating layer

surfaces · billing flows · reporting

Kairos

decisioning engine

signals · decisions · learning

context · motions · outcomes

Your payment rail

payments · renewals · upgrades · recovery

Lifecycle Coverage

One platform across the subscriber life

Oikos runs the motions that keep the web book growing — acquire new subscribers on web, mature new store cohorts onto your rail, retain the subscribers you have, and grow each one over time.

Web-firstAcquire

Convert new subscribers on web before they reach the app stores.

OnboardingMigrate

Move new store cohorts onto your rail as they mature.

In-lifeRetain

Detect churn risk, recover failed payments, and save subscribers before they leave.

ExpansionGrow

Find the right upgrade, win-back, or expansion moment for each subscriber.

Nostos brings the existing book home. Oikos keeps every new and migrated cohort growing from there.

Subscriber Surfaces

Every touchpoint, in your brand and on your rail

Oikos runs the surfaces subscribers actually use — email, checkout, billing, and help. Each surface carries your brand, connects to the same subscriber record, and gives Kairos a place to run the next approved motion.

MessagingEmail

Branded migration and lifecycle email, timed to each subscriber and motion.

PaymentCheckout

Wallet-first web checkout on your rail, carrying the right offer and account context.

Self-serveBilling portal

Plan changes, payment methods, invoices, and billing support in your brand.

SupportHelp center

Guidance for migration, billing, cancellation, and recovery moments without sending subscribers back to the stores.

The decisioning engine inside Oikos

Oikos gives Kairos the surfaces and billing context it needs to act. Kairos reads subscriber signals, decides the next approved motion, and runs it across the web book one subscriber at a time.

Tenure2 yrsPlanMonthlyUsageDailyStateCard failing

Kairos

Payment recovery

Silent retry + card updater, on your rail

Walk a failing card back to active before access ever breaks.

Confidence HighMargin-safe Yes

The same loop runs across every enabled surface — signal, decision, action, outcome.

See how Kairos works

Why Oikos

It acts where the money moves

Point tools can identify a segment, send a message, or report an outcome. Oikos connects the decision to the subscriber surface and the billing event, so the next move runs on your rail instead of becoming another task for your team.

Point tools & CRMs

—Target segments
—Trigger campaigns
—Hand billing outcomes back to your team

Recurr Oikos

Decides at subscriber level
Runs approved motions on your surfaces
Learns from payment, renewal, save, and upgrade outcomes

Why it compounds

Three levers, one line to lifetime value

Oikos grows the same web book from multiple directions at once — keeping more subscribers active, recovering payments before access breaks, and finding the right upgrade or win-back moment for each subscriber. The gains compound because every motion runs on the same subscriber record and rail.

Retain

Subscribers stay active longer when the right motion reaches them at the right moment.

Grow

Upgrades, annual moves, referrals, and win-backs lift the value of each subscriber.

Recover

Failed payments, billing interruptions, and save moments return revenue that would otherwise leak.

Lifetime Value

One engine works every lever on the rail you own, so each outcome improves the next motion.

Pricing

One flat rate for the connected web book

Oikos runs at 2% of successful web payments on the subscriptions connected to Recurr. The rate covers the platform, subscriber surfaces, lifecycle motions, Kairos decisioning, and reporting — with no seat fees or per-motion charges.

See full pricing

Going Live

Connect the rail, then turn on the layer

Oikos starts from the systems you already use — your Stripe account, analytics, subscriber data, and branded surfaces. Recurr connects the layer, then activates the motions in the order your program needs.

Connect

Stripe, analytics, and subscriber data connect without re-instrumenting your app.

Activate

Start with the surfaces and motions needed for your migration and web book.

Run

Kairos reads the signals, runs approved motions, and reports what changes across the connected book.

Recurr Oikos

See where Oikos starts on your book

Oikos grows the web book you own. The audit shows the margin you could reclaim through Nostos, then where Oikos and Kairos go to work first.

Run the audit See pricing

Questions