Writing & Editing
Reply to a Difficult Email
Drafts a calm, specific reply to a tense email, with three tone options and a check that you have not promised more than you intended.
- Customizable fields
- 7 fields
Marketing & SEO
Writes a short, specific cold email from real facts about the recipient and your offer, with a low-pressure ask and no fake familiarity.
Designed for general-purpose AI assistantsPublished November 2026
Fill in the fields and the prompt updates. What you type stays in this page and is never saved or sent.
Write a cold outreach email that a busy person could read in 20 seconds and respond to easily.
Who I am and what I offer: {{my offer}}
Recipient (role and company): {{recipient}}
Specific facts I know about them or their company, with where I found each (a post, a product page, a job listing): {{facts about recipient}}
Why my offer might matter to them, based on those facts: {{relevance}}
Proof I can honestly cite (a result, a customer I may name, relevant experience): none
What I want them to do: reply if it is worth a short call
Tone: respectful, plain, confident but not pushy
Write three versions with different openings: one that starts from something I observed about them, one that starts from a problem people in their role commonly have, and one that starts from the proof. Each version must:
- Have a subject line of five words or fewer, in lowercase, with no tricks or fake "re:" or "fwd:" prefixes.
- Be 90 words or fewer.
- Mention only the observations I listed. Do not pretend to know or admire anything I did not give you.
- Make exactly one ask, small and easy to say yes or no to.
- Make it easy to decline politely.
- Contain no invented numbers, customers, mutual connections, urgency, deadlines or flattery.
After the versions, add: (a) a two-line follow-up email to send after five working days if there is no reply, that adds something new instead of "just checking in", and (b) a note on any compliance basics I should check for my country and the recipient's, such as consent rules and an opt-out, without giving legal advice.
If my facts about the recipient are thin, say so and recommend what to research before sending, rather than padding the email.4 required fields are empty and will stay as a {{placeholder}} in the copied text.
Illustrative only. Real answers depend on your input and the assistant you use.
Version A (starts from an observation) Subject: your onboarding emails Hi Jordan, I read your post about cutting onboarding from 14 to 7 days. At Northlight we help small SaaS teams write the in-app guides that make that possible, and we cut one client's support tickets about setup by 30% (their figure, I can share the case study). Would a 15-minute call next week be worth it, or is this not a priority right now? Either answer is fine. Thanks, Sam Follow-up after five working days: Hi Jordan, one more thing in case it helps: the case study includes the three-step guide template we used. Happy to send it even if a call is not useful. Compliance basics: check whether the recipient's country needs prior consent for marketing email, include your business identity, and offer a clear way to opt out. Note: I used only the facts you provided. The 30% figure is from your input; do not send it unless it is accurate.
Cold email works when it is relevant, short and honest. The most common failure is invented familiarity: a compliment the sender does not mean about a post they did not read.
Test one change at a time, such as the subject line or the opening, so you learn what affects replies.
Respect a "no" and remove the person from your list promptly. Good outreach protects your reputation as well as your results.
Writing & Editing
Drafts a calm, specific reply to a tense email, with three tone options and a check that you have not promised more than you intended.
Marketing & SEO
Turns a feature list into a product page description that leads with buyer benefits, answers objections and makes no unsupported claims.
Marketing & SEO
Groups a keyword list into topic clusters by search intent and suggests one page per cluster, flagging overlaps that could cannibalize.