From raw intent to running channels — without you touching the wiring.
Eight stages run as a deterministic pipeline. The AI only ever proposes; the state machine and your approvals drive every transition; and external channels are written only by deterministic executors after an approval exists.
- 01 INTAKE
Intent data lands in a live ledger
Your first-party intent data — pixel identity plus enrichment — flows into an audience ledger. It polls for refreshes and detects deltas: who is new, who changed, who went quiet. Nothing is deleted; the history is kept so the system can learn from it.
- 02 DIAGNOSE
The AI reads the audience — not the PII
The AI sees redacted stats and field-presence counts, never raw sensitive data. From that it diagnoses who is in-market and proposes segments with predicates a deterministic compiler proves before you ever see a count. The AI never invents a filter.
- 03 OFFER
Each segment gets a matched offer
Shaped by your company DNA and industry, every proposed segment carries one offer — the message that fits where that segment is in its journey. That same offer later drives the email copy, the ad, and the landing page, so the whole activation stays message-matched.
- 04 VALIDATE
Every contact is cleaned before it ships
Emails are verified and only deliverable ones proceed. Every phone is checked against do-not-call flags, and only consented, non-DNC mobiles reach SMS or voice. Compliance is a hard gate before any channel is touched — not a setting you can skip.
- 05 APPROVE
You approve one activation policy
Segment, offer, channels, and caps come to you as a single approval — immutable and hashed once you accept. You approve the policy once; future deltas execute under it within your caps. You are not re-approving every contact, but you are never out of the loop on spend.
this is the gate · nothing spends without it
- 06 ACTIVATE
One plan fans out to every channel
A single lifecycle drives every adapter — email, Meta and Google audiences, AI voice, and a landing page per segment. Paid channels are created paused; a separate spend-gate approval turns them on. The landing-page URL is injected into email CTAs and ad destinations with tracking, closing the loop between targeting and destination.
- 07 SYNC
It re-syncs itself as the audience refreshes
When your audience refreshes, delta detection runs and new, changed, and departed members propagate to every active channel under the approved policy — within caps, without re-approval. The activation stays live without you rebuilding it.
- 08 LEARN
Outcomes flow back and sharpen the next run
Ad spend, email engagement, call results, and CRM won/lost attribute back to person × segment × channel × variant. Winners get promoted, losers paused, fresh converters seed lookalikes, non-responders get suppressed — all inside approved caps, all per-account. Anything material comes back to you.
channels it runs
how it works · faq
The pipeline, in plain answers.
Common questions about the eight stages above — segmentation, approval, compliance, and how it improves. For the agency and business angles, see for agencies and for businesses.
How does Intent On Demand work, step by step?
Eight stages run as a deterministic pipeline: (1) Intake — your intent data lands in a live audience ledger; (2) Diagnose — the AI reads redacted stats, not raw PII, and proposes segments; (3) Offer — each segment gets one matched offer; (4) Validate — emails are verified and phones checked against do-not-call before anything ships; (5) Approve — you approve one activation policy; (6) Activate — one plan fans out to email, SMS, AI voice, Meta, Google, and a landing page per segment; (7) Sync — it re-syncs as the audience refreshes; (8) Learn — conversion outcomes flow back and sharpen the next run.
What data does the AI actually see?
The AI sees redacted statistics and field-presence counts — never raw sensitive data. From those signals it diagnoses who is in-market and proposes segment predicates that a deterministic compiler proves before you ever see a count. The AI never invents a filter and never reads raw PII.
Does the AI launch campaigns on its own?
No. The AI only ever proposes. External channels are written exclusively by deterministic executors, and only after you approve. The state machine and your approvals drive every transition — the AI cannot spend or send on its own.
What do I approve, and how often?
You approve one activation policy — segment, offer, channels, and caps — as a single, hashed, immutable approval. Future deltas execute under that policy within your caps, so you are not re-approving every contact. Anything that spends more or targets wider comes back to you.
How does it stay compliant on email, SMS, and voice?
Compliance is a hard gate before any channel is touched. Emails are verified and only deliverable ones proceed. Every phone is checked against do-not-call flags, and only consented, non-DNC mobiles reach SMS or AI voice. It is enforced in the pipeline, not a setting you can switch off.
What happens when my audience changes?
When your audience refreshes, delta detection runs and new, changed, and departed members propagate to every active channel under the approved policy — within caps, without re-approval. The activation stays live without you rebuilding it.
How does Intent On Demand improve over time?
Ad spend, email engagement, call results, and CRM won/lost attribute back to person × segment × channel × variant. Winners get promoted, losers paused, fresh converters seed lookalikes, and non-responders get suppressed — all inside your approved caps, all per-account, with nothing crossing between clients.
keep reading
get started
See it run on your own audience.
Connect your data and your channels. The AI builds the plan, you approve it, and the pipeline above runs end-to-end — then keeps improving.
No campaign runs until you approve it.