Add-on Strategy

LifeRaft OS add-ons are product workflows, not random extras. Each add-on should either help the project operate, earn revenue, support members, publish content, protect access, report activity, or connect the community to another system.

The best add-on plan starts with the customer journey.

Start With The Job

Ask what the site needs to do first:

• Collect and qualify interest.
• Give members a place to talk.
• Publish updates, docs, or resources.
• Support customers or clients.
• Sell downloads, memberships, or access.
• Track campaigns, funnels, and engagement.
• Gate private areas with agreements.
• Connect a studio/game/virtual-world workflow back to the web platform.

Then choose the add-ons that directly support that job.

Strong Pairings

Some add-ons become more valuable together:

• RLX Funnels + RLX Analytics: see which campaigns, links, and steps actually create leads or conversions.
• RLX NDA + RLX Funnels: require agreement acceptance before private-preview or beta lead capture.
• RLX NDA + RLX Analytics: report agreement views, accept starts, completed accepts, cancellations, and gated contexts.
• RLX Forms + RLX Support: turn intake into structured follow-up.
• RLX Roadmap + RLX Timeline: show what is planned and what has already shipped.
• RLX Gallery + RLX Store or Resources: connect media presentation with paid or protected content.

Standalone Still Matters

An add-on should also make sense alone. A small site might only need Analytics. A private build might only need NDA. A launch campaign might only need Funnels. The modular model lets the install stay lean until a workflow earns its place.

What Customers Should Expect

Public add-on pages explain the business value, workflow fit, related modules, and production expectations. Licensed add-on packages include deeper setup, route, data, hook, and maintenance details.

That keeps the public catalog useful for buyers without exposing private implementation material.