DIVISIO / Blog
Workflow

The segments lived in one tool. The campaigns lived in another. Rules export bridged them.

By Nikita

The setup

Northwind sells a project-management app to small teams. Sofia owns lifecycle: onboarding, activation, expansion, the emails and in-app nudges that move accounts from trial to paid to power user. Her engagement tooling is HubSpot for email and Braze for in-app messaging.

The problem

Sofia had a recurring frustration that every lifecycle marketer knows: the place you discover a segment is never the place you use it. She could analyze her accounts and find meaningful groups, but those groups were stuck inside the analysis. To act on them, she’d have to hand a definition to an engineer and ask them to translate “the activated-but-stalling segment” into a query that HubSpot and Braze could understand.

That handoff was the bottleneck. It was slow, it was a favor, and every time the segment logic changed she had to ask again. “I don’t write SQL, and I shouldn’t have to file a ticket every time I want to message a group I already found,” she said.

The turning point

After clustering her accounts in Divisio, Sofia opened business rules export. Instead of a mathematical model she couldn’t move, Divisio handed her each segment as plain IF/THEN rules: auto-generated, readable, and explaining exactly what defined the group:

IF seats_used ≥ 5 AND projects_created ≥ 3 AND days_since_last_login ≤ 7 THEN “Activated Power Team”

That was it. No query language, no engineer, no black box, just human-readable conditions she could read, trust, and paste anywhere. She rebuilt the “Activated but Stalling” segment as a HubSpot active list in minutes by copying the conditions across, and mirrored it as a Braze segment for in-app nudges.

The rules did double duty: they were both the recipe to recreate the segment and the explanation of why an account was in it, so when a teammate asked “what makes someone stalling?”, the answer was right there in the rule.

How she did it

  1. Ran pattern detection on account usage signals (seats, projects, logins, feature depth).
  2. Opened business rules export to get each segment as IF/THEN conditions.
  3. Pasted the “Activated but Stalling” conditions into a HubSpot active list.
  4. Mirrored the same rule as a Braze segment for in-app messaging.
  5. Kept the exported rules in her runbook as the plain-English definition of each segment.

The payoff

Sofia stood up three lifecycle plays in a week without filing a single data ticket: an expansion nudge for Activated Power Teams, a re-engagement series for the stalling group, and a quiet “you’re underusing seats” prompt for over-provisioned accounts. The stalling series lifted activation-to-paid conversion by a meaningful margin in its first full cycle.

The bigger change was independence. Sofia went from waiting on engineering to shipping segment logic the same afternoon she found it.

“The segment and the campaign always used to live in different tools with a person in between. The rules export is that person, except it’s instant and I can read every line.”

Sofia, lifecycle marketer at Northwind

Feature spotlight: Business rules export (Pro)

Every segment Divisio finds can be exported as auto-generated IF/THEN rules that explain it in plain language. No SQL, no model to host, no engineer in the loop, just readable conditions you can paste into HubSpot, Braze, or any tool that takes a filter. The rules double as the definition of each segment, so the logic stays explainable to anyone who reads it.