v2 LIVEBranching journeys + account scoring just shipped

The customer journey
platform for B2B SaaS.

Branching journeys, broadcasts, and transactional messaging on one canvas, powered by workspace-scoped user and account data, dynamic segments, and event-first execution.

MR
AK
JT
IP
Built for product, lifecycle marketing, customer success, and engineering teams.
app.bunloop.com / journeys / onboarding-v3
Journeys/Onboarding sequenceRunning
Trigger
signup_completed
Email
Welcome
Wait
2 days
Branch
Plan = Pro?
Email
Upgrade
Exit
Completed
1,284 in flight
Email step
Welcome
Welcome to {{co.name}}
Performance
Sent12,480
Open rate64.2%
Click rate22.1%
Trusted by teams shipping atPlinthStrandPylonCadenceLinearVercelStripe
event
schedule
webhook
{ }api
Onboarding live
triggerwaitemailbranch
Welcome sent
Lead created
The Loop

A customer journey
that actually loops.

The marketing-automation stack hasn\u2019t been redesigned in a decade. You pay three vendors, maintain two reverse-ETL syncs, and write glue code in n8n — to send what is functionally one stream of messages.

Bunloop is one canvas, one data model, one bill.

Journeys

Drag, drop, branch.

A visual canvas for multi-step automation. Version, fork, and roll back like git for journeys.

Branch on anything

Conditional logic that reads your real data.

Route users by plan, behavior, last-seen, custom object state — anything in your model. Test the branch against historical data before publishing.

  • Nested conditions with AND / OR / NOT
  • Time-window predicates ("in the last 7 days")
  • A/B paths with weighted traffic
Explore branch on anything
app.bunloop.com / journeys / onboarding-v3
Trigger
signup_completed
Email
Welcome
Wait
2 days
Branch
Plan = Pro?
Email
Upgrade nudge
1,284 in flight
The whole stack

Unified customer operations.
Durable by design.

CRM data modeling, segmentation, workflow automation, broadcasts, and transactional messaging operate on one workspace-aware platform with queue-first execution and run visibility.

Automations

Trigger and action flows with branching and waits.

Broadcasts

Draft, schedule, and send to dynamic or static audiences.

Transactional

Event-driven operational messaging in the same platform.

Orchestration

Durable state, retries, and recovery-aware execution.

Broadcasts

One-off campaigns with the discipline of automation.

Send launches, webinar invites, and recaps to a precisely-defined audience. Time-zone aware. Live segment count as you compose.

  • A/B test with auto-winner selection
  • Send in each recipient’s local time
  • Per-link, per-cohort analytics
Channels· broadcast · launch-week-d1
em
Email
12,480
sm
SMS
4,820
ps
Push
8,140
ia
In-app
2,610
Explore broadcasts
app.bunloop.com / broadcasts / launch-week-day-1
Subject
Launch week, day 1: branching journeys
Body
Hi {{first_name}},

We just shipped branching journeys — conditionally route users based on plan, activity, or any property...
Audience
Active customers · Pro plan
2,847 recipients
Send
Tue, Mar 12 · 9:00 AM PT
Data model

Built for how B2B actually works.

A
Plinth Co
account · $2,400 mrr
S
sara@
logininvite
M
mike@
viewedit
A
amy@
login
EVENTS1,284 / 30d

Users belong to accounts.
Accounts have events too.

Bunloop treats accounts as a first-class object — with their own events, properties, and journeys. Stop bolting account-aware logic onto a tool that only understands users.

// Account-level event
await client.track({
  event:     'invoice_paid',
  accountId: 'acc_R7Q',
  properties: { amount: 4900 }
})
The Bunloop difference

One canvas. The whole stack.

Stop paying for three tools that don\u2019t share a data model.

Bunloop
Point tool A
Point tool B
Visual journey builder
User-level events
Account-level events
Custom objects
Transactional emails
API-first
Per-step analytics
Account scoring
Workspace-scoped architecture
Durable orchestration runtime

Bunloop gave us one operating surface for customer data, segmentation, and execution. Our team now ships lifecycle changes in hours instead of stitching tools for weeks.

SY
Sasha Yu
Head of Growth · Plinth.dev
7
core product pillars
3
execution surfaces
1
workspace-scoped platform
Durable
queue-first runtime model

Build the loop.
Let it run forever.

Start in sandbox mode, then scale with workspace-aware controls, ingestion-ready APIs, and run observability.