Designing a recurring revenue loop from day one

Some businesses are like treadmills. Every month starts at zero: new customers must be found, convinced and sold to, and last month's customers are gone. That can work — many good businesses operate this way — but it is exhausting, expensive and fragile. A bad month in acquisition becomes a bad month in revenue immediately.

Other businesses compound. Customers who pay this month are likely to pay next month. Existing customers bring new ones. Each month starts from a base that is higher than the last.

At Oryvelon, step three of our new-company protocol asks a direct question: how does revenue repeat without constant manual effort? We ask it before the product is built, because the answer changes what we build. This note explains how we think about it.

Three ingredients of a recurring loop

Every recurring revenue loop we have seen work has three ingredients.

1. A recurring problem. The customer has the problem again and again — every day, every week, every term, every season. A problem that happens once rarely supports recurring revenue, no matter how clever the pricing.

2. A recurring moment of value. The product delivers something the customer notices, regularly. A daily briefing, a weekly match, a new reading, a term report, a restock. If value is delivered once and then becomes invisible, customers eventually ask why they are still paying.

3. A low-friction way to pay again. Renewal should be simpler than cancellation is tempting. That does not mean hiding the exit — it means making continued use effortless and fairly priced.

If any ingredient is missing, recurring revenue tends to leak, and no amount of marketing will fix it for long.

The loops we use across the group

Oryvelon companies serve very different customers, so their loops differ. Seeing them side by side is useful.

No single model is best. The right loop is the one that matches how often the customer has the problem and how value is delivered.

Subscriptions: simple, powerful and easy to get wrong

Subscriptions are the most familiar loop, and for products used regularly they are usually the right starting point. They create predictable revenue, make planning easier and align the business with long-term customer success.

But subscriptions have failure modes:

• Flat prices for variable costs. If some customers use far more than others — especially where AI costs scale with use — a flat price can make heavy users unprofitable. That is why MerchNivo combines a subscription with usage-based components. See Subscription plus usage: pricing logic for AI SaaS.
• Invisible value. A subscription for something that works quietly in the background risks being cancelled in a budget review. Products should make their value visible — through summaries, reports and reminders of what they did.
• Annual lock-in without annual value. Annual plans reduce churn on paper, but if customers feel trapped, the relationship suffers at renewal.

Usage and credits: pricing that moves with value

Usage-based pricing charges customers in proportion to what they use: per analysis, per report, per reading, per request. Credits are a friendlier version — customers buy a bundle in advance and spend it as they go.

These models work well when:

• usage varies a lot between customers;
• the cost of serving each unit is significant (as with AI);
• customers want to try the product without committing to a subscription.

ZodiVela combines subscriptions for regular users with credits and one-off premium readings for people who prefer to pay occasionally. The loop comes from giving people reasons to return — new readings, new formats — rather than from locking them in.

Licences: recurring revenue on institutional calendars

For education, the natural rhythm is the school year. EduRelia sells annual licences to schools in tiers — 100, 500 or 1,000+ students — alongside subscriptions for families. The school licence creates a predictable annual cycle, and renewal depends on whether teachers, students and families found real value during the year.

Licence loops have their own discipline: onboarding at the start of term matters enormously, mid-year support determines renewal, and the end-of-year report is effectively the renewal pitch. We describe the model in B2B2C in education: family subscriptions and school licences.

Repeat purchases: the commerce loop

A direct-to-consumer brand like Noveniq does not have subscriptions in the usual sense. Its loop is repeat purchase: customers who bought once come back when they change devices, need a replacement or want something new.

The ingredients still apply. The recurring problem is real (devices change regularly). The recurring moment of value is a new product that fits a new need. The low-friction path is a store that remembers nothing it should not, but makes reordering easy, communicates only when there is something genuinely useful to say, and treats customers well enough that they choose to return. See Running a direct-to-consumer brand as an operating business.

Marketplace loops: two sides, two reasons to return

A marketplace like CastLyra needs a loop on each side.

For businesses, the recurring problem is that content production never stops: new campaigns, new products, new seasons. A subscription makes sense if the marketplace reliably delivers relevant, verified talent whenever they need it.

For talent, the recurring problem is finding the next opportunity. A premium plan makes sense if it genuinely improves visibility or helps them manage requests better.

Over time, completed bookings can carry a commission, aligning the marketplace's revenue with successful matches. The loops reinforce each other: more active businesses attract better talent, and better talent keeps businesses subscribed. The hard part is starting the loop at all — see Two-sided marketplaces: thinking about the cold-start problem and Marketplace monetisation.

Report and partner loops: when the problem is episodic

Some problems are not weekly or monthly. Deciding whether to study, work or live abroad is a significant, episodic decision. KeşifAtlası's core product — an eligibility test followed by a paid personal report — does not naturally repeat every month.

The loop here comes from three places:

1. Life stages. A family may explore options for study now, work later, and residence after that. Each stage is a new decision.
2. Rule changes. When relevant rules change, an updated assessment has real value.
3. Partners. People who decide to proceed often need further help — the report can connect them to relevant relocation partners, which creates referral revenue without the product itself needing to become a service business.

Episodic products need to be especially careful about trust. A loop built on unnecessary upsells would undermine the core value. See From free test to paid report: designing a consumer funnel.

Designing the loop before the product

Why ask this question before building? Because the loop shapes the product in concrete ways.

It decides what the product must remember. A subscription product needs a reason to show value repeatedly, which may require keeping history — carefully, within the product's data boundary. A report product needs to know when a rule relevant to a past report has changed.

It decides what the product must measure. For a subscription, retention and engagement over time matter most. For credits, purchase frequency. For licences, usage across a term. The measurement plan follows the loop.

It decides the pricing unit. Per store, per student, per report, per reading, per booking. Choosing the unit early avoids painful migrations later.

It decides where AI costs must be controlled. If the loop depends on frequent AI-generated value, AI cost per customer must be sustainable at that frequency. See Cost discipline for AI products.

Healthy loops versus manipulative ones

There is a dark side to recurring revenue: products that are hard to cancel, subscriptions that renew silently at higher prices, "free trials" designed to be forgotten. These tactics can inflate revenue for a while. They also destroy trust, create complaints and invite regulatory attention.

Our rules are simple:

• cancelling should be as easy as signing up;
• renewal reminders go out before annual renewals;
• price changes are announced in advance and explained;
• credits and prepaid balances are clearly shown;
• customers can export their data when they leave.

A loop that works only because people cannot find the exit is not a loop worth building.

Measuring whether a loop is working

We track a small set of numbers for each company's loop:

• Retention over time for subscriptions and licences.
• Repeat rate and time between purchases for commerce and credits.
• Expansion: do customers grow into higher tiers or higher usage?
• Referral: do existing customers bring new ones?
• Cost to serve per customer, compared with revenue per customer.

These numbers feed directly into the continue, stop or scale checkpoints. A company with strong first purchases but weak repeat behaviour has an acquisition engine, not a business — yet.

Questions to ask about your own loop

If you are designing a new product, try answering these honestly:

1. How often does your customer have this problem?
2. What will they notice from your product each week or month?
3. What would make them stop paying — and how would you know before they do?
4. Does your price move with the value you deliver and the cost you incur?
5. If acquisition stopped for three months, what would revenue look like?

The last question is the clearest test. A business with a real recurring loop survives a quiet quarter. A treadmill business does not.

When the loop leaks: reading churn properly

Every recurring business loses some customers. What matters is understanding why, and whether the reasons are fixable.

We separate churn into a few types, because each calls for a different response.

Churn after the first period. Customers leave soon after their first month, term or purchase. This usually means the promise on the website and the experience in the product did not match — the offer attracted people the product does not serve well, or onboarding failed to deliver the first moment of value. The fix is in messaging and activation, not in retention campaigns.

Churn after a period of real use. Customers who used the product properly for a while decide to leave. This is the most informative churn, because these people understood the product. Talking to them — briefly, respectfully, without trying to talk them out of it — often reveals the next most important improvement.

Churn caused by price. Sometimes the product is valued but the price no longer fits: a store's sales drop seasonally, a family's circumstances change. Flexible tiers, pausing options or usage-based pricing can keep these relationships alive without discounting the product for everyone.

Churn that is healthy. Some customers leave because the problem is solved. A family that has completed a move no longer needs relocation reports. A student who has finished a course moves on. That is success, and the right response is to make it easy to come back — or to recommend the product to someone else — later.

For each company we keep a short, regularly updated note on why customers leave, in their own words. It is one of the most useful documents a company can have, and it feeds directly into product priorities and the group's operating cadence.

Subscription or usage: the trade-off in one table

Most loop decisions end up somewhere between a flat subscription and pure usage pricing. Neither is better in general; each gives something up.

The friction row is the one people forget. Usage pricing can quietly discourage the very behaviour the loop depends on — if every reading or analysis feels like spending money, customers use the product less and notice its value less. That is why several of our companies combine the two: a subscription that covers normal use comfortably, with usage or credits for the expensive edges.

Mistakes we see in loop design

Some mistakes come up often enough that we check for them in every new company's plan.

Confusing notifications with value. A daily email is not a recurring moment of value unless the customer would miss it. Sending more messages to "drive engagement" usually drives unsubscribes. MerchNivo's briefing earns its place only if it contains something the merchant would otherwise have had to find themselves.

Building the return reason on anxiety. In consumer products especially, it is tempting to bring people back through worry — about the future, about missing out, about a deadline that is not real. We rule this out. ZodiVela gives people reasons to return that are about reflection and enjoyment, never fear. See Entertainment positioning for consumer AI.

Choosing the pricing unit for convenience. Pricing per seat is easy to bill, but if value grows with orders, students or requests, the unit fights the product. Migrating pricing units after launch is painful for everyone.

Discounting to renew. A large renewal discount can save a customer this month and teach every customer to threaten cancellation. Better to fix the reason they wanted to leave, or offer a smaller plan that fits.

A loop that depends on one channel. If repeat revenue depends entirely on a single marketplace, platform or partner, the loop is rented. Owned relationships — email with proper consent, accounts, a good product — keep it yours.

A one-page loop worksheet

Before any build starts, the loop is written into the company's source-of-truth document as a short worksheet. It has seven fields:

1. The recurring problem, and how often the customer has it.
2. The recurring moment of value, described as the customer would experience it.
3. The pricing unit, and why it tracks value.
4. The cost to serve one unit, including AI, at expected usage.
5. The renewal or repeat moment — when and how the customer decides to pay again.
6. The exit: how a customer cancels, exports data or stops, in a sentence.
7. The measure: the one or two numbers that show the loop is working.

Filling it in takes an hour. Leaving a field blank is informative in itself — it usually means that part of the loop has not been thought through yet. For EduRelia, for example, the renewal moment is not a monthly charge but a school's budget decision near the end of the academic year, and the worksheet makes clear that the evidence for that decision must be collected all year, not in the final month.

The worksheet is revisited at each checkpoint. Loops change as companies learn — a report product may discover that partners matter more than expected, or a subscription product that a credit option brings in customers who would never subscribe. Writing the change down keeps the whole team working to the same model, and makes it easier to see which products in the group share the same shape of problem.

Summary

Recurring revenue is not a pricing trick; it is a consequence of solving a recurring problem and delivering value the customer notices, repeatedly and fairly. At Oryvelon we design the loop before the product — subscriptions where use is regular, usage and credits where it varies, licences on institutional calendars, repeat purchases in commerce, and partner loops where the problem is episodic.

The result is a group of companies whose revenue compounds rather than resets. You can see the full list on the Companies page.

Questions and answers

What is a recurring revenue loop?

The mechanism by which a business earns again from the same customers, or from new customers brought in by existing ones, without starting from zero each time.

Do all Oryvelon companies use subscriptions?

No. Loops vary: MerchNivo uses subscription plus usage, EduRelia uses family subscriptions and annual school licences, ZodiVela combines subscriptions and credits, Noveniq relies on repeat purchases and KeşifAtlası on reports and partners.

When should recurring revenue be designed?

Before the product is built. It shapes the product, the pricing and the data the company needs to collect.

Published by Oryvelon, a digital company builder · About the group · Our companies · More in Company Building

NextCapital allocation inside a company builder →