Prompt library

You are helping me write a follow-up email after a call with [WHO THE CALL WAS WITH, e.g. a customer's operations lead].

Here are my rough notes from the call:
[PASTE YOUR NOTES]

Write a follow-up email that:
- Opens with one warm line that refers to something specific from the call
- Lists what we agreed, as short bullet points
- Makes clear who owns each next step, us or them, with a date where one was mentioned
- Ends with one clear next step and a proposed date
- Stays under 150 words, in plain language, with no corporate phrases

If something in my notes is unclear, do not guess. List it at the end under "Check before sending".

Read the email you just wrote and my original notes again.
What did we discuss on the call that the email does not confirm?
List anything that could cause confusion later, in one line each.

I am a customer success manager preparing for a renewal conversation with [DESCRIBE THE CUSTOMER, e.g. a 40-person marketing agency].

Here is what I know about the account:
[PASTE YOUR NOTES: their original goals, what they use, results, recent conversations]

Create a one-page renewal brief with these sections:
1. Their original goals, in their words where possible
2. What has improved for them, with any numbers from my notes
3. What has not gone as planned
4. The three concerns they are most likely to raise
5. Five open questions I should ask to understand their plans for next year

Keep it factual. Only use what is in my notes, and mark anything you are inferring with "(inferred)".

Based on the brief, play the role of the customer's decision-maker.
Ask me the three toughest questions they might ask about renewing.
After each of my answers, tell me in one line what would make it stronger.

I am preparing a quarterly business review for [DESCRIBE THE CUSTOMER].
Their main goals for this year are: [LIST 2-3 GOALS].

Here are my notes and results from the last quarter:
[PASTE NOTES AND RESULTS]

Draft a slide-by-slide outline for a 30-minute review. For each slide give:
- A title written as a statement, not a label (e.g. "Onboarding time dropped by a third", not "Onboarding")
- Two or three bullet points of supporting detail
- One question to ask the customer on that slide

Build the story around their goals, not around our product. Keep it to 7 slides or fewer.

Search the web and research [COMPANY NAME] ([COMPANY WEBSITE]) before my first sales call with them.
I sell [WHAT YOU SELL, in one line].

Give me a short brief with:
1. What they do and who their customers are, in two sentences
2. Anything that has changed recently: new products, hiring, funding, leadership changes, expansion
3. Two or three problems they might have that relate to what I sell, marked as guesses
4. Five open questions I could ask to find out if those problems are real

Link the source for every fact. If you cannot find something, say so rather than guessing.

Here are three emails I have written that got good replies:
[PASTE 2-3 OF YOUR EMAILS]

Describe my writing style in five short bullet points: sentence length, tone, how I open, how I ask for things, and phrases I use.
Do not write anything else yet.

Using my writing style, write a first email to [THEIR ROLE] at [COMPANY].
The specific reason I am writing: [ONE CONCRETE REASON, e.g. they just opened a second office, or they posted about a problem I solve]
What I can help with: [ONE LINE]

Rules:
- Under 90 words
- Open with the specific reason, not with who I am
- One question at the end that is easy to answer
- No phrases like "I hope this finds you well" or "I wanted to reach out"

Then write one follow-up for five days later, under 50 words, that adds something new rather than "just checking in".

I sell [WHAT YOU SELL] to [WHO YOU SELL TO].
These are the objections I hear most, in the customer's words:
[LIST 3-5 OBJECTIONS]

For each one, give me:
1. What the person is probably really worried about, in one line
2. A short, honest answer I can say out loud, under 40 words
3. One question I can ask back to understand the concern better

Do not use pushy sales techniques. The goal is to understand the concern, not to win the argument.

Play the role of a busy, slightly sceptical buyer.
Raise this objection: "[ONE OBJECTION]".
After I answer, respond as the buyer would, then step out of the role and tell me in two lines what worked and what to change.

Here is a piece of content I wrote:
[PASTE THE FULL TEXT]

Find eight different angles for a LinkedIn post, each one able to stand on its own. For example: a surprising number, a mistake, a how-to, a strong opinion, a before-and-after.
Give each angle a one-line summary. Do not write the posts yet.

Write LinkedIn posts for angles [NUMBERS YOU CHOSE].
My audience: [WHO READS YOUR POSTS]

Rules for each post:
- The first line must make sense on its own and make someone want to click "see more"
- Short paragraphs of one or two sentences
- One idea per post, under 180 words
- End with a question or a simple takeaway, not "thoughts?"
- No hashtags in the body, and no emojis at the start of lines

Here is a transcript of an interview with a customer about how they use our product:
[PASTE THE TRANSCRIPT]

Write a case study draft with these sections:
1. The situation before, in the customer's terms
2. What they tried and why it did not work
3. What changed after they started using us
4. The result, using only numbers the customer actually said
5. Three short direct quotes, copied exactly from the transcript

Strict rules: never invent a number or a quote. If a section has no support in the transcript, write "Not covered in interview" so I know to ask a follow-up question.

Here are [NUMBER] pieces of customer feedback, one per line:
[PASTE THE FEEDBACK]

Group them into themes. For each theme give:
- A clear name for the theme
- How many pieces of feedback mention it
- Whether it is mostly positive, negative or mixed
- One or two quotes copied exactly from the feedback

Sort themes from most to least common. Put anything that fits no theme in an "Other" group rather than forcing it in.

Here is a rough explanation of how we [NAME OF THE PROCESS]:
[PASTE YOUR NOTES OR TRANSCRIPT]

Turn it into a step-by-step guide:
- Start with one line on what the process achieves and when to use it
- List what you need before starting
- Number every step, with exactly one action per step, starting with a verb
- Where a step has a decision, write it as "If X, do Y. Otherwise, go to step N."
- End with how to know it worked

Use plain language. Do not add steps that are not in my explanation.

Read the guide as someone who has never done this before.
Which steps would you get stuck on, and what information is missing?
List each gap as a question I should answer.

Here is everything I worked on this week, unsorted:
[PASTE YOUR NOTES OR TASK LIST]

The update goes to [WHO READS IT, e.g. my manager].

Write a weekly update with three short sections:
1. What moved forward, as results, not activities ("Supplier contract signed", not "Had calls with supplier")
2. What is stuck, and why
3. What I need, from whom, by when

Maximum 120 words. Leave out anything routine that the reader would not miss.

Here are notes from a meeting about [TOPIC]:
[PASTE NOTES OR TRANSCRIPT]

Give me three lists:
1. Decisions made, one line each
2. Actions, each with an owner and a deadline. If no owner or deadline was stated, write "No owner" or "No date" so I can fix it
3. Questions discussed but left open, with no decision

Only include what is in the notes. Do not invent owners or dates.

I am a [YOUR ROLE, e.g. freelance brand designer]. Here are my notes from a discovery call with a potential client:
[PASTE YOUR NOTES]

My proposed timeline: [TIMELINE]
My price: [PRICE AND WHAT IT INCLUDES]

Write a one-page proposal with:
1. The problem, described in the client's own words from my notes
2. What success looks like for them
3. My approach, in three to five plain steps
4. Timeline and what I need from them at each stage
5. The investment, stated once, clearly, with what is included and what is not

Confident but not salesy. No filler about my passion or experience.

A client has not paid an invoice.
Invoice: [INVOICE NUMBER], [AMOUNT], due on [DUE DATE]
Our relationship: [e.g. good, a first project, a long-term client]

Write three short reminder emails:
1. A friendly nudge, sent 3 days after the due date. Assume it was missed, not ignored.
2. A clear reminder, sent 10 days after the due date, asking for a payment date.
3. A firm final notice, sent 21 days after the due date, stating what happens next, for example pausing work.

Each email under 80 words, polite, with the invoice details stated plainly. No guilt-tripping and no apologising for asking.

I am doing this project for a client: [ONE-LINE PROJECT DESCRIPTION]
What I have agreed to deliver: [LIST THE DELIVERABLES]
Timeline: [TIMELINE]

Write a scope of work with:
1. Deliverables, each described specifically enough that we would both agree on whether it is done
2. Rounds of revisions included for each deliverable
3. What is not included, listing things clients commonly assume are part of a project like this
4. How extra requests are handled: how they are quoted and approved
5. What I need from the client, and by when, for the timeline to hold

Plain, friendly language. It should read as clear, not defensive.