Competition Base - Surgical Strike

Targeted approach to identified customers of competitors. Named on the whiteboard as a precision play, not a broadcast.

Vertical: Program · Status: ⬜ Planned Back to Program · workflows index

Who it targets

Non-IIFL base - customers known or inferred to hold a competitor product.

Trigger

Inferred from external signals. The identification method is undefined on the roadmap and is the crux of the workflow.

Flow

identify competitor-held prospects         <- undefined; see caution
        |
verify contactability + consent basis      <- the gate
        |
differentiated proposition per competitor  [Creative Agent]
        |
compliance review - competitor mentions    [Compliance Agent]
        |
dispatch, tightly capped                   [A5 dispatcher]

Data it needs

Needs	Have
Competitor-holding signal	⬜ source undefined
Lawful consent basis for non-customers	⬜
Competitive rate/terms intelligence	⬜

Agents involved

Compliance Agent - this is the one Program workflow where its competitor_promotion code and the brand avoid list matter most.

Blocked on

Not primarily a technical blocker. The identification source and the lawful basis for contacting non-customers both need answers before anything is built.

Roadmap source

Page 2 - A2 -> Competition Base - Surgical Strike — see roadmap_ref_extracted.md.

Caution before scoping this

Two questions the whiteboard does not answer, and neither is an engineering question:

Where does the competitor-holding signal come from? Purchased lists, bureau data and inferred signals carry very different legal and reputational profiles in India.
What is the lawful basis for outbound contact to a non-customer? Consent, the DND registry and regulatory limits on unsolicited financial marketing all apply, and none is mentioned anywhere in the source material.

Treat this as the last Program workflow to build, not the first, regardless of how attractive the targeting sounds.