Building on Funnel OS

Overview

Funnel OS is a visual systems architecture tool. It lets you design how attention, customers, content, and revenue move through your system — on one board you can actually operate, rather than a diagram that rots in a folder.

Most funnels live in someone’s head or scattered across documents. Funnel OS puts the whole customer journey in one place, so you can see where people enter, where they drop, and what genuinely needs fixing next.

Open Funnel OS

Before you start

Funnel OS is a whiteboard-driven workspace — dragging blocks, connecting funnels, right-click menus. It needs real screen space and a precise pointer.

Use a laptop, desktop, or a large tablet in landscape. On a phone the board is not usable.
A mouse or trackpad is strongly preferred over touch.
Everything else in the suite works fine on a phone — this one tool is the exception.

The board

The board is an open canvas. There is no rigid template to fight — you place things where the logic of your funnel wants them.

Pan by dragging empty canvas; zoom to move between the whole map and the detail.
Right-click for contextual actions on the canvas and on individual blocks.
Arrange blocks to mirror how attention actually flows, so the shape of the system reads at a glance.

Building your stages

Stages are the backbone. Start with a column for each stage of your journey and resist the urge to over-model on day one.

Create a column for each stage — for example Awareness, Interest, Consideration, and Purchase. Keep it to the stages that matter; you can refine later.
Name them in your own language. The board is for operating, not for impressing anyone.
Group stages into the four layers — attention, trust, ownership, and monetization — so the underlying architecture stays visible.

Those four layers are the operating model behind every ArboraX build. The Framework explains why they are ordered that way.

Adding channels, offers, and actions

This is the step that turns a diagram into an operating system. Under each stage, add the things that actually move someone forward.

Channels — where the attention comes from.
Offers — what you are asking someone to say yes to at this stage.
Actions — the specific thing that carries them to the next stage.

If a block does not move someone forward, it is decoration. Delete it.

Reading the funnel end to end

Once the board reflects reality, read it as a visitor would — start at the top and follow the path down. The gaps announce themselves.

A stage with no channel feeding it will stay empty no matter how good the offer is.
A connection that goes nowhere is a leak. The map makes those obvious.
Branches show alternative paths — a lead that converts now versus one that needs nurturing.
If you cannot explain why a link exists, it probably should not.

The goal is a map where every block earns its place and every connection is intentional. Funnelology walks through hybrid funnels mapped end to end if you want worked examples.

Operating the board

Funnel OS is not a diagramming tool you visit once. It is meant to be the single view of your system.

Keep the board current as the funnel changes — a stale map misleads worse than no map.
Use it in reviews to decide where attention and budget go next.
Let it be the shared picture everyone works from.

How it fits the rest of the suite

The board is the big picture; the other tools fill it in.

Model the economics of a stage in the Calculator.
Project it forward in the Simulator.
Schedule the campaigns that feed it in the Calendar.
Turn each planned change into work in the Task Manager.

If you would rather have this built with you, that is what Services covers.

Saving & exporting

Funnel OS saves your work automatically to your browser’s local storage as you go — there is no save button to remember. Because that storage is tied to one browser on one device, exporting is how you back up or move your work.

Export writes your current data to a file you can keep or transfer.
Import loads a previously exported file back in — useful on a new device.
Keep periodic exports of anything you would hate to lose; local storage is convenient, but it is not a backup.

The Tutorials walk through a full backup-and-move, step by step. For the underlying rules, see Importing & exporting.

Export is also how you share the plan — step back, read the funnel end to end, and when it looks right, export it to keep a backup or hand it to your team.

Your data stays yours. Everything you create lives in your browser’s local storage on your own device — it is never uploaded to an ArboraX server. See Where your data lives and the Privacy Policy for the full detail.