How BHASM runs your retention.
One cycle a day. Nobody on your team runs it, reviews a queue, or picks a send date.
Score. Check. Draft. Release. Credit.
Score
Every customer scored against their own cycle, 0 to 100 urgency. No segments, no batch sends.
Check
Sentiment safeguard, frequency limit, world context, hard stops. An account that fails a check rests this run. It is not contacted.
Draft
The message is written for the archetype, in your voice, before anyone decides whether to send it.
Release
Windows open today are cleared. The rest are timed for the day their own window opens; the same words are worth more later.
Credit
A purchase within 30 days is credited to the nearest release before it, counted once, cross-checked in GA4.
Same engine. Two starting points.
Connect a store, a CRM or a file
The first brief runs as your data arrives. The engine scores, drafts and holds from day one; you release the queue in a click.
Imprint learns how you already run retention
Imprint watches 90 days, learns your voice, then amplifies what works. Write-back is opt-in: nothing is written until you switch it on.
A classification is worth what it changes.
Naming the archetype is the cheap half. Here is the other half, on The Habitual Buyer, one of 18 behavioural archetypes: five orders, same product, gaps of 31, 34, 37 and 34 days. The gaps are illustrative; the arithmetic is the engine's.
HELD · window opens day 32
The cycle, the band and the day sit beside the draft, per customer, with the reasoning attached. Operator side only.
“Your usual is ready whenever you are — one tap and it’s on the way.”
No day count, no cycle, no mention of what was measured. The mathematics decides when to speak; it never speaks.
Five walls no campaign crosses.
Sentiment safeguard
A complaint stops all outreach. No override.
Permanent opt-out
An unsubscribe is final. It is never re-evaluated.
Every wall, every send
A message passes every wall, or it is sent back.
Account-scope check
Failed payment or open dispute: a hard stop.
Autonomy switch
Autonomous sending is off until you turn it on.
Command · Insights · Impact.
One desk for now, one for why, one for proof. Every number on these desks is computed; nothing is invented.
Today's queue, already written.
LTV held this week · Confidence read per customer · Geo-tagged world context
Where the rhythm reads that way.
Cohort retention heatmap · Repeat purchase rate · Leakage funnel
What it did, and what it declined.
Revenue credited per release · Every hold, with its reason