BNI · FLOWOnDraft

Traditions + Innovation

Flow Designer

separating processes from code.

Weekly chapter and one seat per profession is the tradition. Flow Designer is the innovation on that seat: the process lives where operators can read it, not only where a developer can compile it.

Show us the bottleneck →Process design

Why this matters after the 1-2-1

A referral that depends on one person’s head is fragile. If the join between Xero and Logistaas only exists as custom code, the next change is a ticket and a wait. Flow Designer puts the process on a canvas: starts, logic, do, tell, finish — then compiles it to the runtime that should actually run it. The publicFlow Designer demois the same idea without a login.

  • Members and operators can see the process without a deploy.
  • Versioning: the current flow is the source of truth, with history.
  • Faster iteration when the bottleneck moves — which it will.
  • Less lock-in to one developer’s head, including ours.
PRODUCT HUB · FLOW STUDIOOnDraft
Flow Studio process canvas: a visual flow of trigger, system joins, and completion nodes
Dark Store Systems Flow Studio hub illustration — the product canvas for authoring a process as a flowchart (starts, joins, finish), not a screenshot from a logged-in tenant session. We could not capture a live designer login in this environment.

How a BNI-shaped flow is authored

In the product, processes are drawn as glass-brick nodes. Palette folders group work by job: Starts (order events, integration webhooks such as Xero), Logic, Do (including Create payment and Ring Bud Bell), Tell, Finish. The document in the middle is a ProcessDocument. Compile targets either an integration runner or warehouse rules — pick the runtime first, do not pretend one engine does both.

01See

Map the bottleneck with the member or their client.

02Draw

Author the process on the canvas, not in a hidden script.

03Compile

Integration graph or warehouse rules — the right executor.

04Run

Every trigger and step writes a business event.

05Change

Version the flow when the operation learns.

Try the public Flow Designer demo The Xero payment flow this is for Ring Bud Bell from the same palette Process design service

Process as source of truth

What does Flow Designer separate?

The process — triggers, decisions, joins, notifications — from the code that executes it. The process is the source of truth. Code compiles and runs it.

Can a BNI member’s operations team change a process?

That is the point. Operators can see the flow and change it without waiting for a developer to redeploy a hidden script. Versioning keeps the history honest.

We build systems that power growth.

AI agents, integrations and operational software—built around your business.