Write an initial outreach email from public information
Author: AILesson7 min setupTested with:ChatGPTReviewed: 2026-08-28
Quick answer
Write relevant, permission-aware outreach from verified public facts without pretending familiarity or intent. Provide: Public prospect information, Offer and evidence, Contact and messaging rules. Expected result: A concise outreach email with claim citations, relevance logic, a low-friction ask, and compliance checks.
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Draft an initial outreach email using only the supplied public information and offer evidence. Do not browse or infer missing facts.
Source IDs, URLs, publication/access dates, facts, role, organization, and uncertainty:
[prospect]
Verified capability, use cases, exclusions, proof, permissions, CTA, and qualification needs:
[offer]
Sender identity, lawful contact basis, region, opt-out, cadence, tone, length, prohibited claims, and review date:
[rules]
First audit source recency, directness, and whether the fact belongs to the recipient/organization. Separate public fact, reasonable relevance hypothesis, and unknown. Do not infer pain, budget, authority, priority, current system, intent, personality, or personal relationship. Do not use personal/sensitive data merely because it is public. If contact permission or legal basis is missing, stop at a draft and flag compliance review; never claim the email has been sent.
Write a specific factual subject, transparent introduction, one concise public context reference, a clearly hypothetical relevance bridge, verifiable offer evidence with limits, and one easy next step or permission question. Avoid false praise, surveillance-like detail, urgency, fear, guaranteed outcomes, manipulative personalization, hidden tracking, or pretending a case study applies directly. Include an appropriate opt-out only if rules require. Provide full and shorter versions, a source-to-claim ledger, personalization risk check, stale-source check, and pre-send confirmations.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Public prospect information
P1: Northstar Library Network annual plan, published 2 Jul 2026, accessed 26 Aug 2026, official site. It states a 2026 goal to standardize performance definitions across 14 branches; owner is listed as Operations Directorate, not an individual. P2: organization staff page, updated 1 Aug 2026, accessed 26 Aug: Priya Shah is Head of Operations. No public statement says she owns the standardization project, has budget, or seeks vendors. Use organization email supplied by an approved business directory; its provenance still needs compliance confirmation.
Offer and evidence
Sender works at ClearLedger. Verified product capability: configurable data dictionaries, validation rules, and approval history for CSV reporting workflows. It does not automatically clean data or guarantee time savings. Approved anonymized case: a public-service team used a shared schema/checklist; self-recorded reconciliation moved from about two staff-days to four staff-hours, with workload changes and no causal test. Permission allows aggregate wording. CTA: ask whether a 15-minute comparison of their definition workflow would be useful; qualification needs are current workflow and ownership.
Contact and messaging rules
Draft only for UK business outreach, under 120 words, direct and respectful. Sender name/title must be inserted. Legal basis and directory provenance are not yet approved, so flag compliance review. One initial email and one follow-up maximum if approved; include a simple no-more-email option. No tracking-pixel recommendation, urgency, or claim that Priya leads the initiative. Review date 26 Aug 2026.
Example output
Subject: Northstar's shared reporting definitions
Hello Priya,
I'm [sender name], [title] at ClearLedger. Northstar's 2026 annual plan describes a goal to standardize performance definitions across 14 branches. I do not know whether this sits within your current remit, but your public role in Operations made you a reasonable person to ask.
ClearLedger supports configurable data dictionaries, validation rules, and approval history for CSV reporting. In one approved anonymized public-service example, self-recorded reconciliation moved from about two staff-days to four staff-hours after a shared schema and checklist; workload also changed, so this is not a guaranteed or causal result.
Would a 15-minute comparison of definition workflows be useful, or is there a better owner? If this is not relevant, reply and I will not contact you again.
Best,
[sender name]
Short version: “Northstar's annual plan notes a 14-branch definition-standardization goal [P1]. ClearLedger supports data dictionaries, validation, and approval history. I do not know whether you own this work. Would a brief workflow comparison be useful, or is there a better contact?” Ledger: annual-plan fact P1; role P2; ownership explicitly unknown; product/case from offer. Do not send until lawful basis, directory provenance, sender fields, current pages, and approved opt-out wording are confirmed.
Why this works
1
Labeling relevance as a hypothesis prevents a public fact from becoming an invented customer problem
2
Source and contact-basis checks make personalization reviewable before it reaches a real person
Check the result
Can every prospect and offer claim be traced to a current supplied source or labeled hypothesis
Does the draft avoid inferred pain, authority, intent, relationship, and sensitive personalization
Are lawful contact basis, opt-out, source freshness, and pre-send approval explicit
Use it with confidence
Frequently asked questions
Practical answers about when to use this recipe, what to provide, and where human review still matters
What should I prepare before using “Write an initial outreach email from public information”?
For “Write an initial outreach email from public information,” prepare Public prospect information, Offer and evidence, and Contact and messaging rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Write an initial outreach email from public information” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A concise outreach email with claim citations, relevance logic, a low-friction ask, and compliance checks—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Write an initial outreach email from public information”?
The published test record for “Write an initial outreach email from public information” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT