For PLG SaaS · event-triggered lifecycle

Onboard, activate, retain.

Lifecycle email built around product events. Welcome at 50–80% opens. Trigger flows on ‘activation’ the second your code fires it. No data warehouse, no Customer.io contract.

50–80% welcome open rate·40–60% PLG activation median·<1s event → trigger
Trial cohort · last 7 daysShipBay · web app · onboarding flow live
15.0%trial → paid
StageSigned up
1,247Users
Welcome series — 5 touchesopen ~64%
StageVerified email
1,184Users
StageHit activation event
723Users
Activation milestone emailfires on event
StageActive in week 2
521Users
Power-user upsell pitchusage > threshold
StageConverted to paid
187Users

Ranges from current PLG industry benchmarks.

Who switches to Bluey

Three SaaS shapes. Three reasons they moved.

$0–500K ARR

Seed PLG founder

The situation

Welcome → activation → upgrade sequences need to fire on real product events. No time to wire Segment + a CDP + an ESP.

With Bluey

REST API + webhooks. Fire 'project_created' or 'invited_teammate' from your code. Branch a flow on it the same day.

30K signups/mo

Growth lead · 20-person SaaS

The situation

Free signups land. A single welcome blast goes out. Nothing happens after that. Activation sits well below the 40–60% PLG benchmark.

With Bluey

Pre-built onboarding-by-milestone flow. Different copy for stuck vs activated users. Exits the second they convert.

API-first product

DevTools company

The situation

Transactional + lifecycle email need to live in the same place. A Customer.io contract costs more than the whole API budget.

With Bluey

Same plan handles transactional sends + lifecycle. One DKIM setup. One suppression list. One bill.

PLG activation benchmark

The PLG activation rate that separates winners from also-rans. 40–60%.

Median PLG activation sits between 40 and 60% in current industry data. Top-quartile teams hit 70%+. The single highest-leverage move: a welcome + activation-milestone sequence triggered on the event your product fires when a user gets value.

Day 0The trial starts. The flow fires.

Six lifecycle flows. Six event-triggered moments.

Each branches on what the user actually did in the product — not when they signed up. Configurable in minutes.

01

Onboarding by milestone

Branch the welcome series on whether the user hit their activation event. Different copy for stuck vs activated.

Welcome opens 50–83% · industry benchmark

02

Trial expiry · three touches

Day -7, -3, -1 sequence. Each scoped by how much the user actually used the product.

Industry trial-to-paid conversion median: ~15%

03

Power-user upsell

Watch for usage thresholds and frequent-login signals. Auto-pitch upgrade with the user's own usage data.

Highest-converting upsell trigger in PLG

04

Churn-risk save

Fires when usage drops >50% week-over-week. A short, honest re-engagement note from the founder.

Catches roughly 1 in 4 at-risk accounts early

05

Feature announcements, targeted

Announce a new feature only to the segment that would care — customers using the competing feature today.

Lifts feature adoption vs broadcast announcements

06

NPS + replies threaded

NPS request flow. Replies thread back to the contact's timeline. Detractors auto-routed to support.

Industry NPS response rate 5–15%

Things teams check first.

How do I send events into Bluey?

REST API ('track' endpoint), Segment integration, or webhooks. Events show up on the contact's timeline within a second and become available as triggers and segment conditions.

Can I score leads based on engagement?

Yes — Bluey computes a lead score per contact based on rules you configure (event weights, recency, custom). Score updates live; segments and flows branch on it.

Do you support enterprise auth (SSO, SCIM)?

SSO via Google and Microsoft is on Grow and above. SCIM is on Agency. SOC 2 Type II reports available under NDA.

Wire your first event. Watch the flow fire.

Drop our 'track' endpoint into your code. Branch a welcome series on whether they hit activation. Ship before lunch.