No deployment fee, no monthly platform fee, no per-seat cost. The platform takes a share of end-user subscription revenue, and only above a minimum subscriber threshold.
Below that threshold you run the entire system for nothing.
That is the arrangement at qualifying scale. Smaller and exploratory deployments carry an onboarding fee and a monthly minimum instead. Where the line sits
The AI-on-your-content category charges a subscription to the business. This one does not charge the business at all.
| Model | What the business pays | Risk carried by |
|---|---|---|
| AI clone platforms | A monthly platform fee from day one, whether or not the audience converts. | THE BUSINESS |
| Course & community platforms | A monthly fee that scales with contacts or members, plus setup work. | THE BUSINESS |
| Membership platforms | Nothing up front, then a percentage of everything the audience pays. | SHARED |
| Conquest | At qualifying scale, nothing up front and nothing at all until subscribers pass the threshold. | THE PLATFORM |
FREE UNTIL
IT EARNS.
Ingesting your archive, indexing it, standing up the branded web app, the Telegram bot and the Mini App, and running the AI at query time.
Revenue sharing starts only once paying subscribers pass an agreed minimum. The exact number is set per deployment, against the size of your audience.
We share end-user subscription revenue. The split is agreed before deployment and does not change without you.
What the waiver depends on. The terms above are what we offer a business whose audience is large enough to carry the model on its own. For those deployments we waive everything: no onboarding fee, no minimum, nothing at all until the threshold is passed. It is a real waiver and it is the deal we would rather be doing.
Where the archive is smaller, or where a business would rather deploy first and decide later, we ask instead for a one-time onboarding fee and a monthly minimum. Both are sized against your scale, and the minimum ends the month shared subscription revenue passes it. It is not a licence and it is not a platform fee that runs forever. It is a floor, and it exists so that a deployment is never built for someone who has not decided yet.
The subscription split is the only thing shared. Every other kind of value the deployment creates belongs to the business.
These are the returns that usually dwarf the subscription line, and none of them touch the split.
Every cited answer links to the original video with a timecode. The engine is a permanent, personalized referral engine pointing at your own catalog.
Courses, programs, retreats, consultations, books. When a guide reaches the edge of the free archive, the next step is something you sell.
Your domain, your branding, your subscribers. They are not visiting a marketplace where a competitor is one click away.
The questions people bring, and the ones your archive answers badly, are a content roadmap you cannot get from view counts.
Things worth knowing before you decide, rather than after.
Standing a deployment up is real work and real money: ingesting the archive, indexing it by meaning, building the branded surfaces, and paying for inference from the very first question anyone asks. We are glad to carry all of it for a business whose audience makes the threshold a realistic target, because that is a bet we expect to win, and because carrying it is the strongest signal we can send that we believe the thing works.
We cannot carry it for everyone who is curious. A deployment built for a business that decides three months later it was not for them is a straight loss, and the businesses who do commit end up paying for it. So where the audience is smaller, or where the intent is still exploratory, we ask for a one-time onboarding fee and a monthly minimum until subscriber revenue covers it. The amounts are modest and they are sized against your scale.
The point was never the money. The point is that both sides put something on the table before anyone spends six months on this. Where you fall is a conversation we have at the start, in plain terms, against your actual numbers.
If your audience never reaches the subscriber floor, the platform earns nothing and we will eventually need to have a conversation about whether the deployment continues. We would rather set an honest threshold against your actual audience size than a decorative one.
The engine needs a substantial body of published material to answer from. A handful of videos will not support cited answers or a personal guide. We will tell you if your archive is too thin, before any work starts.
The whole model rests on end-user subscriptions. An audience that has never paid for anything is a genuine risk, and it is one we would rather size up with you honestly than discover six months in.
Tell us the size of your library and your audience. We will come back with a proposed threshold, a proposed split, and an honest read on whether this is worth doing at your scale.
Activate your archive