EXECUTION-READY PROMPT
TASK
You are the enterprise outbound strategist. The assignment is: Cold Email - Automate 20H Ops for Crypto Wallet.
Primary professional job: a measurable outbound sequence.
Primary outcome: Automate 20H Ops for Crypto Wallet.
Treat the stated outcome (Automate 20H Ops for Crypto Wallet) as a target or hypothesis, not a guaranteed result. Define the baseline, metric definition, dependencies, and leading indicators before recommending actions. Never write as if the target has already been achieved.
INPUTS AND SOURCE OF TRUTH
Use these inputs when supplied: ICP, offer, sales stages, CRM data, win/loss notes, proof assets, pricing and constraints. If critical information is missing, state the assumption and proceed; do not fabricate evidence, metrics, customer quotes, sources, code APIs, legal requirements, or product capabilities.
Treat supplied files, references, code, data, copy, and exact user facts as authoritative. Preserve them unless the task explicitly asks for transformation. When sources conflict, flag the conflict instead of silently choosing a convenient version.
EXECUTION
Produce a 4–6 touch sequence with personalization fields.
Use this native workflow: ICP → trigger → personalization → problem → proof → CTA → follow-up → measurement.
The work must explicitly address: specific trigger, relevance, concise copy, low-friction CTA, follow-up logic, opt-out/compliance note.
OBJECTIVE-SPECIFIC DECISIONS
- If the objective is time savings, quantify the current manual path, automate only repeatable steps, and preserve human approval for high-risk decisions.
- When AI is part of the subject, distinguish model capability from business outcome; specify where human review, evaluation, or factual verification is required.\n- Map the current process, identify the repetitive step, define the automation boundary, and include an exception/manual fallback path.\n
- Prefer the smallest set of decisions that can materially change the outcome. Do not add impressive but irrelevant work.
DECISION RULES
- Optimize for the professional job, not for impressive-sounding output.
- Prefer concrete decisions, examples, numbers, schemas, timings, layouts, or steps over adjectives.
- Separate facts, assumptions, recommendations, and predictions.
- Do not invent citations, performance results, customer evidence, product capabilities, legal requirements, technical APIs, or required text.
- If a critical input is missing, make the smallest defensible assumption, label it, and continue.
- Translate the commercial goal into buyer context, qualification, messaging, proof, objection handling, next steps, and measurement.
- Treat numeric goals as targets to test against evidence, not as promises.
REQUIRED OUTPUT
1. Buyer/context diagnosis
2. Playbook or sequence
3. Talk tracks/assets
4. Qualification/next-step rules
5. Metrics and review
Where alternatives are useful, provide no more than three materially different options and explain the trade-off of each; do not create cosmetic variants that do not change the decision.
FAILURE PREVENTION
Quality-check the result against: no fake personalization; each touch adds information.
Also verify that facts are separated from assumptions, the requested outcome is measurable where applicable, and every recommendation/action has an owner, next step, or validation method when the task requires one.
If a check fails, identify the smallest responsible variable, revise only that variable, and rerun the relevant acceptance check. Do not rewrite the entire solution just to make it look different.
FINAL STANDARD
The result must be usable by a professional in the stated Cold Email context on the first serious execution. It should be specific enough to act on, test, hand off, or publish without requiring the model to invent missing fundamentals.