How BHASM works

From first data sync
to the brief.

Every decision — who to contact, what to say, when to stay silent — documented and traceable.

Data flow Silence rules The engine Governance
How a score is reached

Every score, traceable to its inputs.

One customer. Urgency 94. The contributing factors and their relative significance.

How this score was reached 94
Silence durationprimary
Personal cycle driftsignificant
World context (pre-season)moderate
Purchase velocity trendsupporting
Relationship balancestable
Every score shows its contributing factors. No black box.

Exact model weights, aggregation formulas, and proprietary calibration logic are protected intellectual property. This ensures the engine remains effective, continuously improving, and difficult to replicate. All decisions remain fully auditable for your compliance and review needs.

Seed & Growth Factor labels and relative significance visible in dashboard.
Scale & Performance Full audit log export via API. Every decision, every signal, every outcome — exportable for compliance teams and regulators.
Architecture blueprint

Where BHASM sits in your stack.

Three nodes. No middleware to host. The Veto layer reads every event before it leaves your domain. Output channels never receive a message the laws have not cleared.

Data sources Your existing stack
· Shopify / WooCommerce — orders, cart events · Razorpay / Stripe — payments + dispute state · GA4 — engagement + UTM attribution · Your CRM — HubSpot, Salesforce, Pipedrive, Zoho · Snowflake / Databricks — warehouse pull (Scale+)
BHASM · Governance Engine The Veto layer
· Urgency model — 0–100 score per customer · Multi-layer governance — hard-coded checks per send · Sentiment veto · karma debt · world signals · 1 in 6 messages stopped before they fire · Every decision logged with originating check cited
Output channels Cleaned triggers only
· Omnichannel gateway — WhatsApp, SMS, Email · Resend / SendGrid / Twilio — transactional + lifecycle · Your ESP (Mailchimp, Klaviyo) via API key · Webhook out — POST /your-endpoint for downstream automation · CRM write-back — at-risk flags on contact rows
Zero-code integration

Connected in 3 minutes. No SDK to install.

There is no engineering lift. The Veto layer is fully managed. You authenticate via OAuth with your store and your communication gateway; BHASM's background signal scan maps your historical data instantly and the first brief generates within 4 minutes of import.

3 min
to first connection
Shopify OAuth, Razorpay key, GA4 service-account — no SDK, no npm install, no webhook URL to deploy.
4 min
to first brief
Historical orders scored against your industry's natural rhythm. 270 customers typical first scan. Brief lands in your dashboard automatically.
0
infrastructure to host
No middleware. No webhook receiver. No engineering ticket. The Veto layer runs in the BHASM cloud and only emits cleaned triggers downstream.

For Scale and Performance: Snowflake or Databricks pull activates once credentials are connected. Enterprise webhooks accept API-key auth. Setup remains hours, not months — the chip is built in; credentials light it up.

Data flow

Your data enters.
Decisions come out.

BHASM reads your customer data, scores every relationship against 62 industry profiles, applies the governance stack, and surfaces who needs a decision. Every step is logged.

Your data sources
Shopifyorders · cart
Razorpaypayments
GA4behaviour
WhatsApp · Email
CSV import
→
BHASM engine
Relationship scoring
62 industry profiles
Multi-layer governance
Sentiment veto
Message generation
→
The weekly dividend
Ranked account list — highest urgency first
Message written for each account
Suppression log — what wasn't sent and why
Estimated recovery value per account
The physics of silence

BHASM sends less than you expect.
That is the product.

Every message not sent is a relationship preserved. These are the five mechanisms that govern silence.

Sentiment veto
Sentiment veto
If a complaint, support ticket, or negative signal is detected — all outreach blocked. No override. Silence until the relationship is repaired.
Without this
Promo sent 2 hours after complaint. Customer churns by end of day.
Frequency limit
Frequency cap
Attention is finite. BHASM enforces hard limits per customer per week and per month — regardless of how many campaigns are running. Third contact in a week? Blocked.
Without this
3 campaigns run the same week. Customer gets 3 messages. Unsubscribes from all future contact.
Silence baseline
Silence accumulation
After sustained contact without response, BHASM enters silence mode. Sending into silence damages the relationship more than not sending.
Without this
Sustained ignored messages. The relationship is dead before BHASM stops trying.
Hard suppression
Absolute block
Payment failure, active dispute, legal opt-out: these are hard stops that no campaign can override. Not a filter. A wall. Governed by the physics layer in every brief run.
Without this
Discount sent to customer with payment failed 3 days ago. Regulatory exposure. Relationship destroyed.
Approval gate
Human approval
On Seed — every message requires your approval before sending. Autonomy is earned, not assumed. Higher tiers unlock autonomous sending only after confidence thresholds are met.
Without this
First brief runs. 14 messages sent to customers you've never approved. No visibility. No control.
The architecture

Built on laws,
not prompts.

Most AI tools ask a language model what to do. BHASM runs a physics engine first — the language model adds narrative to decisions already made by mathematics.

18
Buyer archetypes
Each archetype has a distinct trigger, response rhythm, silence pattern, and message style. Identified from purchase pattern — not demographics.
∎
Governing constraints
Every brief is governed by a deterministic stack of constraints. Every account, every run, traceable end-to-end. Not opinion — mathematics that can be audited.
62
Industry silence profiles
52 days without an order is normal for a luxury fashion brand. For a D2C supplement, it is churn. BHASM knows the difference for 62 industry profiles — and calibrates every urgency score accordingly.
C7
Scoring dimensions
Churn probability · temporal decay · behavioural enrichment · world signal modifier · archetype classification · sentiment veto · physics constraint. Seven independent scores combined into one urgency number. Not a guess. A physics model.
The engine sharpens with every brief. What it knows at month six is not available at week one. That gap is not purchasable.
Governance

Every decision is traceable.

BHASM maintains a full ledger of every send, every veto, every silence. At any time you can see why a message was sent — or why it was not.

Every send logged
Channel. Time. Urgency score at send. Archetype. Which signals triggered the action. Founder approval status.
Every veto logged
Which rule blocked it. What signal triggered the block. How long the silence window lasts. When BHASM will re-evaluate.
Every outcome tracked
Did the customer respond? Did they purchase? Was the relationship repaired? Fed back into the scoring engine.
Start now

See it run on your customers.

Seed tier is free forever. Connect in 3 minutes. First brief runs automatically.

See your industry →
Urgency score
Every silent customer gets a 0–100 urgency score. Score breakdown traceable to its inputs — not a black box. 1 in 6 messages vetoed at the governance layer before they fire.
Outcome math
D2C: day 28 action → 67% recovery rate. Day 47 action → 34%. BHASM acts early, on purpose.
ROI in pricing
5,000 customers: typically recovers $2,500–$5,000 in month 1. Growth: $299. Scale: $999.
Multi-region governance
DPDP Act 2023 · GDPR · CCPA. Regionally isolated data processing. Omnichannel execution — Email, SMS, WhatsApp. Day 1 intelligence active across 62 industry profiles.
Glossary · hover or tap any term
Urgency score — 0–100 composite. Five inputs. Every score traceable.
1 in 6 vetoed — messages drafted then stopped, not delayed.
18 archetypes — each customer classified on first purchase.
62 industries — pre-calibrated cycles and sensitivities.
Personal cycle — silence measured against their average, not yours.
World signals — news, weather, festivals, economic windows.
Multi-layer governance — structural gates every message passes.
14-day attribution — what counts as a real recovery.

Every feature, one click away.

Hero · live demo
The live engine, on loop.
Watch the engine score an active customer, run the governance check, draft the message, and validate the recovery — in eight seconds. Same engine the dashboard runs.
See the live card →
Try the engine
Simulate your list.
Pick an industry archetype and a silence duration. The output names the urgency score, the BHASM decision, and the governing rule that holds or releases the account — not just a number.
Open the calculator →
Audience switcher
E-commerce, SaaS, B2B.
Toggle the framework and the entire homepage recalibrates — customer name, urgency, value, channel — so you see your exact unit economics, channels, and compliance layer.
Switch the view →
The Retention Paradox
Why blocking 16% of sends raises revenue
Inbox placement falls from 94% to 71% when you force the 4th sequence item. The frequency limit fires the veto to insulate domain health — preserving your absolute right to extract revenue when the timing is mathematically worth money.
Read the math →
Industry timelines
industry-scenario, Day 1 → Day 29
Six industries, six end-to-end recovery timelines — the moment BHASM acted and the value protected.
Open the industry scenarios →
Pricing · autonomy ladder
Confidence-gated send authority
Seed: human approval. Growth: confidence-gated autonomous send. Scale: full autonomy within the governance stack. Performance: SLA-backed governance. Each tier names the autonomy contract, not the feature list. SaaS, Stripe, Snowflake, enterprise integrations included on Scale and above.
See the autonomy ladder →
2,847 ₹2,400 ₹24,95,722