LifeRaft OSTM

Operations add-on

RLX Funnels

Ecosystem funnel builder for landing flows, lead capture, waitlist/newsletter/donation handoffs, directory/link CTAs, and Analytics/Stats conversion tracking.

OperationsCategory
1.0.0Version
ProductionRelease stage
$64.85 · AdvancedLicense
Back to catalog
Operations add-on

About this add-on

RLX Funnels for LifeRaft OS

Ecosystem funnel builder for landing flows, lead capture, waitlist/newsletter/donation handoffs, directory/link CTAs,

At a glance
  • Funnel campaigns, ordered steps, lead capture, and handoffs
  • Optional RLX NDA gate before lead capture for beta, private-preview, or client funnels
  • Handoff CTA and lead events can mirror into RLX Analytics and RLX Stats
  • Localized labels and theme-token aligned light/dark layouts
rlx-funnels Version 1.0.0 $64.85 · Advanced Production

Capabilities and outcomes

How RLX Funnels improves the build

The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.

Optional bridges to Waitlist, Newsletter, Donate, Directory, Links, NDA, Analytics, and Stats

Turns admin work into a controlled process instead of a spreadsheet habit

Gives professional teams cleaner visibility, repeatability, and post-launch operating confidence

Optional NDA-required lead capture checks funnel assignments by slug, id, then the rlx-funnels addon assignment

Operations builds that need RLX Funnels without forcing it into every install

Standalone value

What it does by itself

RLX Funnels can run as its own Operations workflow. By itself, it focuses on Funnel campaigns, ordered steps, lead capture, and handoffs, Optional RLX NDA gate before lead capture for beta, private-preview, or client funnels, and Handoff CTA and lead events can mirror into RLX Analytics and RLX Stats, so a customer can use the module without buying every related add-on first.

Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.

Connected value

What improves when related add-ons are active

When the customer also owns and activates related modules such as RLX Waitlist, RLX Newsletter, RLX Donate, RLX Directory, and RLX Links, RLX Funnels can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.

Best fit

Who should care about it

  • Funnel campaigns, ordered steps, lead capture, and handoffs
  • Optional bridges to Waitlist, Newsletter, Donate, Directory, Links, NDA, Analytics, and Stats
  • Optional NDA-required lead capture checks funnel assignments by slug, id, then the rlx-funnels addon assignment
  • Operations builds that need RLX Funnels without forcing it into every install

Workflow

How it fits into a real build

  1. Activate RLX Funnels and review its add-on settings
  2. Configure the module settings and permissions
  3. Add the records, content, media, or rules this module manages
  4. Review public pages and backend empty states before launch
  5. RLX Funnels loads from rlx-funnels/addon.php and should be configured through the add-on registry, permissions, and

Works well with

The strongest builds connect the right modules

RLX Funnels becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Waitlist, RLX Newsletter, RLX Donate, RLX Directory, RLX Links, depending on the customer package and what the site needs to accomplish.

Admin setup

Confirm settings, navigation placement, permissions, and any required starter content before launch.

Public QA

Review the public page, empty states, mobile layout, and activated/deactivated states.

Data QA

Check exports, filtering, retention, audit visibility, and staff-only permissions.

Docs and support

Add customer-facing notes, admin setup instructions, and known limitations for the module.

Customer FAQ

Common questions about RLX Funnels

What does RLX Funnels do?

Ecosystem funnel builder for landing flows, lead capture, waitlist/newsletter/donation handoffs, directory/link CTAs, and Analytics/Stats conversion tracking.

Who is RLX Funnels best for?

Funnel campaigns, ordered steps, lead capture, and handoffs. Optional bridges to Waitlist, Newsletter, Donate, Directory, Links, NDA, Analytics, and Stats. Optional NDA-required lead capture checks funnel assignments by slug, id, then the rlx-funnels addon assignment.

Can RLX Funnels run by itself?

RLX Funnels can run as its own Operations workflow. By itself, it focuses on Funnel campaigns, ordered steps, lead capture, and handoffs, Optional RLX NDA gate before lead capture for beta, private-preview, or client funnels, and Handoff CTA and lead events can mirror into RLX Analytics and RLX Stats, so a customer can use the module without buying every related add-on first.

Do I need the other add-ons mentioned on this page?

No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Funnels should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.

What changes when related add-ons are active?

When the customer also owns and activates related modules such as RLX Waitlist, RLX Newsletter, RLX Donate, RLX Directory, and RLX Links, RLX Funnels can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.

Which add-ons work well with RLX Funnels?

RLX Funnels commonly pairs with RLX Waitlist, RLX Newsletter, RLX Donate, RLX Directory, RLX Links. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Funnels?

RLX Funnels should be launched with its real data model and public routes in mind. Routes: RLX Funnels is exposed through the routes registered by its add-on entry file when the module is active. During, launch, teams should confirm the public page, admin entry point, empty states, permissions, and navigation placement, match the package being sold. Add admin screenshots, reporting examples, export behavior, retention policy, permissions, and examples of decisions the module helps staff make. Operations pages should emphasize control, visibility, and repeatable process Optional integrations: rlx-waitlist, rlx-newsletter, rlx-donate, rlx-directory, rlx-links, rlx-nda, rlx-analytics, rlx-stats, rlx-analytics, rlx-stats.

How much does RLX Funnels cost?

RLX Funnels has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.

What support is included for RLX Funnels?

Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.

How ready is RLX Funnels for deployment?

Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.

How does RLX Funnels fit into a real LifeRaft OS build?

Activate RLX Funnels and review its add-on settings. Configure the module settings and permissions. Add the records, content, media, or rules this module manages. Review public pages and backend empty states before launch.

Does the public page include implementation details?

No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.

Coming soon

Want RLX Funnels in your LifeRaft OS build?

RLX Funnels is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.