Skip to main content
Flow Builder

A no-code flow builder for the full subscriber journey.

Most onboarding flows ship once and never change. Engineering can't get to them, marketing can't touch them, and "we'll fix it next quarter" turns into next year. Flow Builder is a visual canvas for designing, branching, and shipping subscriber journeys — onboarding sequences, conversion funnels, upgrade paths, win-back flows — across CTV, web, and mobile, without filing a ticket.

  • CTV
  • Web
  • Mobile
Onboarding · Q2 Draft · v14
Preview Publish
Trigger
Entry
First open
Branch
Platform
Route by surface
Page
Welcome
iOS · 3 steps
iOS
Page
Hero paywall
Apple TV · Roku
CTV
Page
Plan selector
Web · annual
Web
Page
Trial offer
7-day
Goal
Convert
Subscribed
Page
Win-back
Discount path
Lindsay
The challenge

Onboarding doesn't have a creative problem. It has a release-cycle problem.

For most subscription teams, the onboarding flow is the sequence engineering shipped two years ago and nobody has touched since. Marketing has ideas. Product has data. Growth has variants ready. None of them ship.

What's stuck

Each change is a release

For most subscription teams, the onboarding flow is the sequence engineering shipped two years ago and nobody has touched since. Marketing has ideas. Product has data. Growth has variants ready. None of them ship, because each change is a code release, an App Store review, and three teams' calendars synced up around it. The flow stays frozen while the rest of the business moves.

Why it stays stuck

Generic funnel tools weren't built for this

Most "flow builders" weren't built for subscriptions. Generic funnel tools handle a lead-capture form and a thank-you page. They don't model trial offers, hard paywalls, regional pricing, or the difference between an iOS first-time install and a CTV reactivation. Subscription teams either accept a tool shaped for a different business, or they keep onboarding in code and live with the release cycle.

What it takes

A subscription-native canvas

The fix is a flow builder that's subscription-native — one that knows what a paywall is, what a plan selector is, what a CTV remote does — and that lets product and marketing branch a journey by platform, segment, or region without writing a line of code.

How it works

Map the full path. Branch where it matters. Ship without a release.

Step palette Drag any step onto the canvas. Connect with a click.
Landing
Paywall
Plan picker
Offer
Upgrade
Confirm
Entry
Platform
iOS · Welcome
CTV · Hero
Trial
Convert
Cross-platform

One flow. Every device subscribers actually use.

A flow built once in Nami runs across iOS, Android, Apple TV, Roku, Fire TV, LG, Samsung, Vizio, Xbox, and Google TV — plus Chrome, Safari, and Edge on the web. Layouts adapt to the device. Focus behavior, remote navigation, and platform-native components are handled in the canvas.

The same upgrade flow that runs on mobile runs on Roku without a separate build, a separate team, or a separate roadmap.

iOS
Android
Apple TV
Roku
Fire TV
LG
Samsung
Vizio
Xbox
Google TV
Chrome
Safari
Edge

Surface support, not customer logos. Flow Builder ships the same canvas to every one of these devices from a single dashboard.

What it changes

Onboarding stops being a one-shot deal.

When a flow is something a small team can update in an afternoon, it stops being a fixed asset. It becomes a working surface that gets sharper every quarter — segment by segment, platform by platform, offer by offer. The lift comes from frequency, and the frequency comes from getting onboarding out of the release cycle.

Inside the platform

Flow Builder is one piece. The platform is the system.

Flow Builder is the visual canvas inside Nami's subscription orchestration platform — the system product and marketing teams use to design, test, and optimize the complete subscriber journey across CTV, web, and mobile. The full experience layer, in one place.

Flow Builder FAQ

Questions teams ask before they buy.

How is Flow Builder different from a generic funnel builder?
Generic funnel builders were designed for lead capture and landing pages, not for subscriptions. They don't model paywalls, trial offers, plan selectors, regional pricing, or platform-specific behavior. Flow Builder is built around subscription primitives and ships flows to CTV, web, and mobile from one canvas. The unit of work is a subscriber journey, not a generic funnel.
Do we still need engineering to update flows?
For day-to-day flow work, no. Once your engineering team completes the initial SDK integration — a one-time setup — product, marketing, and growth teams add steps, change branches, and update offers independently. Flow updates ship without filing a ticket or cutting a release.
Can a single flow run different paths on different platforms?
Yes. Conditional logic routes subscribers based on platform (iOS, Android, web, and every major CTV surface), segment (first-time visitor, active subscriber, lapsed), country, language, GeoIP, or CDP audience. One flow definition can produce dozens of platform- and segment-specific variants without duplicating the canvas.
Does Flow Builder replace our onboarding code?
For the screens subscribers see — landing pages, paywalls, plan selectors, upgrade prompts, and win-back sequences — yes. Flow Builder owns those surfaces and the routing between them. Backend logic (auth, entitlements, billing) continues to live in your stack and connects through the SDK.
Can we test a new flow against our current one?
Yes. Variants of a flow run head-to-head in Experiments — a new onboarding sequence against the existing one, an alternate upgrade path against today's, a regional offer against the global default. Configure traffic allocation across variants and read subscription-aware results so the team can declare a winner with confidence.

Move onboarding out of the backlog.

Book a demo and we'll walk through how product and marketing teams design, branch, and ship full subscriber journeys on Nami — across CTV, web, and mobile, without an engineering ticket.