How BHASM runs your retention.
One cycle a day. Nobody on your team runs it, reviews a queue, or picks a send date.
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, at a rhythm of their own.
- CycleTheirs
Their own median gap, not a category average. The archetype decides which clock to trust.
- BandMeasured
The measured spread of their own gaps. It sets where the window opens and where it closes.
- ReleaseAt open
Nothing is written before the window opens. When it opens, the message is written from what is true then, and sent.
- FloorHistory
Without enough history BHASM will not use a personal cycle. It uses the category rhythm and says so.
- What the operator sees in the brief
HELD · window opens [date]
The cycle, the band and the window sit on the account, per customer, with the reasoning attached. Operator side only.
Score. Check. Draft. Release. Credit.
- 01 · 06:00
Score
Every customer scored against their own cycle, 0 to 100 urgency. No segments, no batch sends.
- 02 · 06:04
Check
Sentiment safeguard, frequency limit, world context, hard stops. An account that fails a check rests this run. It is not contacted.
- 03 · 06:07
Draft
Only accounts whose window opens today are written, for the archetype, in your voice, from what is true this morning.
- 04 · 06:09
Release
Windows open today are cleared. Every other account waits for its own window; its message is written that morning.
- 05 · T+30d
Credit
A purchase within 30 days is credited to the nearest release before it, counted once, cross-checked in GA4.
Five laws no campaign crosses.
- 01
Sentiment safeguard
A complaint stops all outreach. No override.
- 02
Permanent opt-out
An unsubscribe is final. It is never re-evaluated.
- 03
Every law, every send
A message passes every law, or it is sent back.
- 04
Account-scope check
Failed payment or open dispute: a hard stop.
- 05
Autonomy switch
Autonomous sending is off until you turn it on.
Same engine. Two starting points.
- Start fresh
Connect a store, a CRM or a file
The first brief runs as your data arrives. Every account is scored and timed from day one; you release the queue in a click.
- Keep your stack
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.
Command · Insights · Impact.
One desk for now, one for why, one for proof. Every number on these desks is computed; nothing is invented.
- Command · now
Today's queue, already written.
LTV held this week · Confidence read per customer · Geo-tagged world context
- Insights · why
Where the rhythm reads that way.
Cohort retention heatmap · Repeat purchase rate · Leakage funnel
- Impact · proof
What it did, and what it declined.
Revenue credited per release · Every hold, with its reason