Draft a professional marketing email I can send from Gmail to [RECIPIENT OR RECIPIENT GROUP]. I represent [SENDER AND COMPANY], and the purpose is [PURPOSE AND CLEAR ASK]. Use these facts about the recipient, relationship, offer, and permissions: [CONTEXT AND APPROVED FACTS]. Match this tone: [TONE]. Write for a busy recipient who should understand why this is relevant in the first two sentences. Open with a specific, accurate connection to their role, work, or stated priority from my notes; do not pretend we have a relationship, read private activity into public information, or manufacture flattery. Explain one concrete reason the offer may matter, then make one low-friction ask. If the ask involves a meeting, state the proposed duration and give a simple reply path. Produce: 1. Three subject lines, each under 55 characters and without misleading “Re:” or “Fwd:” prefixes.
2. One preview-text option under 90 characters.
3. A 100–160 word email in plain paragraphs, with no more than one link placeholder: [LINK OR ASSET].
4. A one-sentence follow-up to send 4–6 business days later if there is no reply.
5. A short note naming any claim, personalization, permission, or compliance issue I should verify before sending.
Do not invent results, customers, mutual contacts, approvals, or recipient pain points. Do not add a calendar link unless I provide it. Avoid multiple CTAs and avoid “just checking in” in the follow-up.
Before answering, check that the subject accurately reflects the email and that the email contains exactly one primary request. Flag unsupported statements rather than smoothing them over. Ask up to 3 clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT OR RECIPIENT GROUP] | Enter the individual recipient or a narrowly defined group and their role. | Priya Nair, director of operations at a 40-person regional architecture firm. |
| [SENDER AND COMPANY] | Enter the sender’s name, title, company, and any relationship that is true. | Daniel Ortiz, partnerships manager at FieldBoard, a project-status dashboard for design teams; Priya downloaded our coordination checklist last month. |
| [PURPOSE AND CLEAR ASK] | Enter why you are emailing and the one action you want the recipient to take. | Invite Priya to a 15-minute conversation about whether FieldBoard can reduce weekly status-meeting preparation. |
| [CONTEXT AND APPROVED FACTS] | Enter accurate personalization details, offer facts, permissions, proof, and claims that are allowed. | FieldBoard imports tasks from Asana and shows project risks in one view; use only the checklist download as personalization; no quantified time-savings claim; Priya opted in to receive product updates. |
| [TONE] | Enter the tone to use, such as concise and collegial or formal and direct. | Concise, helpful, and professional. |
| [LINK OR ASSET] | Enter the approved link, document, or state “no link.” | https://fieldboard.example.com/architecture |
How to use
- Give the model only personalization you can stand behind, including how the recipient opted in if this is marketing outreach.
- Choose one subject line and make sure the first sentence still makes sense if preview text is not shown.
- Confirm the sender identity, permissions, unsubscribe process where required, and every factual claim before sending from Gmail.
- Follow up with: “Make the email 85 words, preserve the same ask, and remove any sentence that does not help the recipient decide.”
Variations
Customer renewal
Use when writing to an existing customer before a renewal discussion.
Write a renewal email to [CUSTOMER CONTACT] from [SENDER] about [RENEWAL DATE OR WINDOW]. Use these verified account facts: [ACCOUNT NOTES]. Ask for [NEXT STEP]. Provide two subject lines and a 120-word email. Lead with the customer’s documented use or outcome, state the renewal logistics plainly, and surface an unresolved issue without defensiveness. Do not imply renewal is automatic, promise features or pricing not approved, or invent satisfaction. Check that all dates, plan terms, and requests match the notes. Ask up to 3 questions only if needed.
Event invitation
Use when inviting a relevant contact to a webinar, dinner, or small event.
Draft an invitation email for [EVENT] to [RECIPIENT GROUP] from [SENDER]. The event details are [DATE, TIME, LOCATION OR LINK, AND CAPACITY], and the reason it is relevant is [APPROVED RELEVANCE]. Create three subject lines, preview text, a 90–130 word invitation, and one short reminder. State the event logistics and RSVP action clearly. Do not imply an exclusive invitation unless it is true or create speaker credentials, agenda items, or attendee names. Check that the time zone and capacity language are accurate. Ask up to 3 questions only if inputs are missing.
Post-demo follow-up
Use after a sales or product demonstration.
Write a post-demo follow-up email to [RECIPIENT] about [PRODUCT]. Use these call notes and commitments: [DEMO NOTES]. The desired next step is [NEXT STEP]. Produce a subject line and an email under 150 words with sections for their stated priorities, relevant capabilities, open questions, and the next action. Distinguish what the product does today from requests or roadmap items. Do not claim that a feature was demonstrated if the notes do not support it. Check every commitment and deadline. Ask up to 3 questions only if needed.
Tips
- A relevant email uses a real detail to explain the message, not as an excuse to repeat the recipient’s biography.
- Limit the body to one recipient benefit and one action; a product tour, case study, demo, and referral request do not belong in the same first email.
- For Gmail sends to groups, segment by a shared reason for relevance and adjust the opening line rather than mail-merging a broad claim.
- Write the follow-up as a useful fork in the road, such as offering a resource or asking whether the issue is not a priority, rather than repeating the first pitch.
FAQ
Can I use this for a bulk marketing email?
It is best for individual or tightly segmented messages. Bulk campaigns require consent, unsubscribe handling, deliverability controls, and testing that Gmail alone may not provide.
How long should a professional outreach email be?
For a first outreach email, 100–160 words is usually enough to establish relevance and make one request. Cut product history and secondary benefits first.
Should I include a calendar link?
Use one only when the recipient is ready to book or the purpose is explicitly a meeting. A reply-based ask can feel lower pressure in a first message.