Prompting for non-developers

Write a professional email to [RECIPIENT] at [COMPANY/POSITION].

Context: [describe the situation in 2-3 sentences]

Email objective: [what you want to achieve]

Desired tone: [formal / friendly / direct / diplomatic]

Points to include:
- [Point 1]
- [Point 2]
- [Point 3]

Points to avoid: [what not to say]

Signature: [First Name Last Name, Title, Company]

Write a professional email to Marie Dupont, Purchasing Director at TechCorp.

Context: We sent her a commercial proposal for our inventory management
software 10 days ago. No response since.

Email objective: Get feedback on the proposal and suggest a 20-minute call.

Desired tone: Professional but warm, not pushy.

Points to include:
- Reference to our meeting on February 15th
- That we adapted the proposal based on her feedback
- Concrete suggestion: call on Wednesday or Thursday morning

Signature: Jean Martin, Sales Manager, InventoSoft

Write a follow-up email for [CLIENT NAME] at [COMPANY].

Relationship history: [number of contacts, last interaction, what was discussed]

What's likely blocking: [probable objection or silence]

New value to offer: [fresh argument or special offer]

Desired call to action: [what you want them to do: call, demo, decision]

Tone: follow up without being pushy, stay professional.
Length: 3-4 paragraphs maximum.

Write an internal announcement to inform [TEAM / ENTIRE COMPANY] about [CHANGE].

The change: [precise description of what's changing]

Effective date: [when]

Reasons for the change: [why we're doing this]

Impact on teams: [what concretely changes for them]

What stays the same: [to reassure]

Actions required from them: [if applicable]

Contact for questions: [name and email]

Tone: transparent, positive, reassuring. No corporate jargon.

Write a message to decline [REQUEST / PROPOSAL] from [PERSON].

The received request: [describe what was asked of you]

Main reason for declining: [why you can't/won't]

What you want to preserve: [the relationship, the partnership, goodwill]

Alternative to offer if applicable: [what you can do instead]

Tone: firm but respectful, without leaving the door open for negotiation.

Write a thank-you email to [PERSON] following [TYPE OF MEETING].

What was discussed: [2-3 key points]

What you particularly appreciated: [specific, not generic]

Agreed next steps: [if applicable]

Your commitment: [what you will do following the meeting]

Tone: warm, sincere, concise. 150 words maximum.

Summarize this document for an audience of [TARGET: non-technical manager, client, operational team].

Desired summary length: [1 page / 5 bullets / 3 paragraphs]

Points to absolutely keep: [what's critical]

What can be simplified: [jargon, technical details, legal references]

Output format:
- An executive summary in 3 sentences
- The 5 key points with one sentence each
- Required actions (if applicable)

[Paste document here]

Read this [CONTRACT / REPORT / LONG EMAIL / ARTICLE] and extract:

1. Important dates and deadlines
2. Commitments from each party
3. Important conditions or exceptions
4. Ambiguous points that need clarification
5. Risks or alerts to note

Present each point as a bullet with the exact quote in quotation marks.

[Paste document here]

Compare these [NUMBER] proposals / offers and help me choose.

Criteria important to me (in priority order):
1. [Criterion 1: most important]
2. [Criterion 2]
3. [Criterion 3]
4. [Criterion 4]

Maximum budget: [if applicable]

Non-negotiable constraint: [if applicable]

Generate:
1. A comparison table on my criteria
2. A summary of pros and cons for each
3. Your recommendation with justification

[Paste proposals here]

Analyze these [NUMBER] customer verbatims / reviews / NPS responses.

Identify:
1. Recurring themes (positive and negative)
2. Urgent issues (repeated mention, strong sentiment)
3. Possible quick wins (easy-to-implement suggestions)
4. Surprising or unexpected insights

Present results with:
- Top 5 positive points
- Top 5 negative points
- 3 priority recommendations
- The most representative quotes for each theme

[Paste verbatims here]

Write a LinkedIn post about [TOPIC / EXPERIENCE / INSIGHT].

My angle: [what I want to say, my unique perspective]

My LinkedIn audience: [managers, entrepreneurs, developers, HR, etc.]

Desired format:
- Punchy hook in the first line
- Development in 3-5 concise points
- Conclusion with call to action or question

Tone: [authentic and direct / inspiring / educational / storytelling]

What I want to avoid: [the buzzword of the week, LinkedIn cliches like "I failed and I learned"]

Length: 150-250 words maximum. Short and impactful.

Write a blog article about [TOPIC].

Target: [who will read it, their knowledge level on the topic]

Angle / main thesis: [what the article will argue or explain]

Desired structure:
1. Introduction with hook (problem or question)
2. [Part 1: title]
3. [Part 2: title]
4. [Part 3: title]
5. Conclusion with synthesis and call to action

Data points or examples to include: [if you have any]

Tone: [informative / persuasive / storytelling / expert]

Length: [600 / 1000 / 1500 words]

SEO: include keywords [list]

Create the content for a presentation on [TOPIC] for [AUDIENCE].

Presentation context:
- Duration: [X minutes]
- Objective: [convince / inform / train / sell]
- Key message: [what the audience should remember]

For each slide, provide:
- Slide title
- Main content (3-5 bullets maximum)
- Speaker notes (what to say, not what's on screen)
- Visual suggestion if applicable

Number of slides: [X]
Structure: introduction -> [theme 1] -> [theme 2] -> conclusion -> Q&A

Write a product sheet / sales pitch for [PRODUCT/SERVICE].

For whom: [target customer, industry, company size]

Problem it solves: [customer's main pain point]

Unique solution: [how your product differs from alternatives]

3 key benefits (not features, benefits):
1. [Benefit 1 with concrete example]
2. [Benefit 2 with concrete example]
3. [Benefit 3 with concrete example]

Common objections and responses: [if you know them]

Call to action: [what the customer should do next]

Tone: [professional / enthusiastic / reassuring / technical]

Write a newsletter for [AUDIENCE] on the theme [THEME].

Newsletter frequency: [weekly / monthly]
Issue number: [if applicable]

Structure:
1. Editorial / personal intro (100 words)
2. Section 1: [title]: [content description]
3. Section 2: [title]: [content description]
4. Section 3: [title]: [content description]
5. Resource of the week: [link or tool to share]
6. Question of the week: [to engage readers]

Tone: [like writing to an expert friend / journalistic / educational]
Total length: [400-600 words]

Write meeting notes from these raw notes.

Meeting type: [standup / committee / brainstorm / kick-off / project review]
Date: [date]
Participants: [list of names and roles]

Raw meeting notes:
[Paste your notes here, even messy, with typos, in shorthand]

Meeting notes format:
1. Context (2 sentences)
2. Decisions made
3. Action items (who does what, by when)
4. Points to explore at the next meeting
5. Next meeting date: [if set]

Tone: factual, clear, no jargon.

Create a plan for [PROJECT].

Context: [project description in 3-4 sentences]

Final deadline: [date]

Available resources: [number of people, hours per week, budget]

Known constraints: [dependencies, holidays, mandatory intermediate milestones]

Identified risks: [what could block progress]

Generate:
1. Task list with time estimates
2. Logical task order (dependencies)
3. Week-by-week schedule
4. Key milestones
5. Recommended safety buffer

I have this list of tasks to do. Help me prioritize them.

Tasks:
[List of all your tasks]

Context:
- Available time this week: [X hours]
- Nearest deadline: [date and affected task]
- My main constraint: [what's preventing me from progressing]

Prioritization criteria:
- High impact on [main objective]
- Urgent (deadline < 48h)
- Dependency for other tasks
- Quick win (< 30 minutes)

Generate a prioritized list with for each task:
- Priority (1-5)
- Time estimate
- Reason for priority
- Whether it's delegable

Help me prepare for the following negotiation.

What I want to achieve: [ideal objective]
My minimum acceptable: [red line]
What I can offer in return: [value I bring]

The other party:
- Who: [name, position, company]
- Their likely interests: [what matters to them]
- Their constraints: [what limits them]
- Their likely position: [what they'll ask for]

Generate:
1. 3 strong arguments to defend my position
2. Likely objections and my responses
3. Concessions I can make (without sacrificing my minimum)
4. Questions to ask to understand their position
5. Agreement and deadlock signals to watch for

Create an onboarding / training program for [POSITION / ROLE] at [COMPANY / TEAM].

Program duration: [X weeks / days]

Objectives: by the end of the training, the person should be able to [list of skills]

Available resources: [documents, tools, reference people]

Week-by-week structure:
[Generate the detailed plan]

For each module:
- Duration
- Learning objectives
- Content / activities
- Practical exercise
- Knowledge validation

Write a progress report for [PROJECT] intended for [AUDIENCE: management, client, team].

Period covered: [from XX to XX]

Overall progress: [X% of the project, in your estimate]

Accomplishments this period:
[Raw list of what was done]

In progress:
[List of what's underway]

Blockers and risks:
[What's not moving and why]

Next steps (2 weeks):
[What's planned]

Budget: [consumed / planned / remaining] if applicable

Tone: [factual and reassuring / transparent about difficulties / solutions-oriented]
Length: [1 page / 2 pages]

# Bad (starting over)
"No, that's not it. Redo it."

# Good (iterating with precision)
"The tone is too formal for the relationship I have with this client.
Make it warmer and more direct. Remove paragraph 2 about technical details,
they don't need it. Shorten to 150 words maximum."