Sales Play Executor · AI Sovereignty

One prospect. Two prompts. One persona-tuned outreach.

A two-stage AI-assisted workflow that turns any Sovereignty conversation from generic outreach into persona-grounded, evidence-anchored, house-of-brand-safe engagement. Stage 1 researches the specific human against public signals and produces a persona essay. Stage 2 uses that essay to write outreach with a custom hook, the Kill Switch narrative, and a concrete next step.

⚡ Wave 1 · Get in the room

How it works

Two stages. One outreach.

BYOI — bring your own AI. Paste the prompts into Claude, ChatGPT, or Gemini. Your API keys and prospect data never leave your browser.

🎯Pick a persona

Three sovereignty archetypes: CIO, CISO, or Data Protection Officer. Each has its own hooks, its own regulator, its own kill-switch place of interest.

→

📝Generate persona essay

Stage 1 prompt — researches the specific prospect against public signals and produces a grounded intelligence brief.

→

✉️Generate outreach

Stage 2 prompt — feeds the essay + the Kill Switch narrative into a persona-tuned message with cold, follow-up, and warm-intro variants.

Step 1 · Pick the persona

Three sovereignty archetypes.

Every place in the Kill Switch stack answers to a different persona. Choose the one closest to your prospect's role and regulator.

STEP 2 Prospect signals

Provide as much or as little as you have. The Stage-1 prompt will explicitly demand grounding and flag any gap it cannot fill from public sources.

Prospect name *

Job title optional

Company *

Industry / regulator optional

LinkedIn URL optional

Paste the URL. The prompt tells the AI to note if it cannot access it directly.

Additional context you already know optional

Outreach variant

The concrete ask

STAGE 1 Persona Essay Generator

Paste this into Claude, ChatGPT, or Gemini. The AI will research the prospect against public signals and produce a persona essay you use as grounding context for Stage 2.

Prompt 1Persona Essay Generator

STAGE 2 Outreach Message Generator

After Stage 1 produces the persona essay, paste it into Stage 2 (replaces the essay placeholder). The result is a persona-tuned outreach with hook, narrative bridge, and concrete next step — pre-loaded with the Kill Switch play context.

Prompt 2Outreach Message Generator

Guardrails — do not skip these

Every prompt above enforces these rules. The seller reviews the AI output against them before sending. Any output that fails a rule goes back into Stage 2 with a correction.

🛡️ House-of-brand

✓Structural framing — sovereignty is a structural question, not a political one.
✓Matter-of-fact tone — evidence does the work, seller does not editorialize.
✕Never name political actors, administrations, or specific executive orders. Say "US export controls", not "President X's order."
✕Never speculate about a specific vendor's compliance failure. Reference publicly-reported patterns only.

📐 Naming (Guide D044422)

✓First reference always full: Teradata Autonomous Knowledge Platform
✓Use Teradata Cloud, Teradata Factory, Teradata Fabric, Teradata AI Studio, Tera, Context Engine.
✕Never AK Cloud, AI Factory, Artemis, AI Workbench, ClearScape Analytics (as product name).
✓In-Database features described as "features included in Teradata Database."

🔎 Grounding discipline

✓Every claim about the prospect must trace to a public source (LinkedIn, company website, industry press).
✓Stage 1 prompt explicitly instructs: "If a fact cannot be verified, say so — do not fabricate."
✕Never invent a specific project, mutual contact, or internal initiative you haven't been told about.

✍️ Seller self-check

?Does the hook reference something specific to this person?
?Is the naming compliant with Guide D044422?
?Is the next step concrete (specific date, format, duration)?
?Does the tone read as matter-of-fact, not alarmist?

Worked example

CISO · Financial Services · DORA

Illustrative output showing what "good" looks like — an anonymized persona essay and the resulting outreach message. Names, companies, and public references are fictional composites.

STAGE 1 OUTPUT Persona essay

Anna Schmidt joined the CISO seat at a top-5 German universal bank eighteen months ago, having spent the prior decade at a European regulator and then at a systemically-important payment infrastructure. Her public speaking — three conference appearances in the last six months — consistently returns to a single theme: that operational resilience and jurisdictional reach are the two questions the industry is under-prepared for, and that DORA is going to expose exactly how under-prepared. She writes on LinkedIn about a third-party risk register her team is building, and about the difficulty of getting board-level attention on the difference between "our data is in-region" and "our data is legally unreachable from foreign jurisdictions." She has publicly criticized vendor claims of "sovereign cloud" that lack transparency about the operator's home-country legal envelope. She is not known to have expressed a technology preference or vendor loyalty in public. Her boss, the Chief Risk Officer, has spoken publicly about the bank's move to reduce concentration risk in its cloud dependencies. Public gap: no known conversation on P2 Weights sovereignty; her focus appears to be P3 Context and P4 Inference.

STAGE 2 OUTPUT Cold outreach (Day 1)

Subject: The two-question framing — from your ISACA panel Anna, Your framing at ISACA in September — that operational resilience and jurisdictional reach are the two under-prepared questions — has been sitting with me. Especially the point about the gap between "our data is in-region" and "our data is legally unreachable from foreign jurisdictions." That distinction is doing more work than most vendor slides acknowledge, and I suspect DORA is about to make it a board-level conversation whether the board is ready or not. We recently published a short piece called The Kill Switch — a documented case: one order, issued elsewhere, and the things an ordinary life rests on switching off one by one; then what she did about it — a register of every yes, and three moves that gave nothing up. Its companion model maps the same six places for an enterprise estate, and marks which switches sit with parties you never chose. Inference, Model, and Identity — and where each is legally reachable from which envelope. It reads as a companion to the third-party risk register work you have referenced publicly. No product pitch; just the structural map. Worth a 30-minute conversation? Two dates that could work: [date A] or [date B]. Happy to send the Kill Switch link ahead of time so we can skip the introduction and go straight to the two places I suspect are on your radar (Context and Inference). Best, [Seller name] — Guardrails self-check: ✓ hook tied to public statement · ✓ Kill Switch play referenced · ✓ concrete next step with dates · ✓ no political actor named · ✓ naming compliant

Wave 5 backlog

EXTENSIONExtend Executor to 9 personas total. Wave 1 ships CIO · CISO · DPO (three primary sovereignty archetypes). Wave 5 adds General Counsel · Board Risk Committee · Chief Compliance Officer for the second ring — plus the same pattern applied to the AI Strategy and AI ROI Executors. Total across the three plays: 27 persona variants.