Laiškai Customer / Difficult
Reply to a customer complaint
Acknowledge the issue, take responsibility, propose a clear next step.
Here is a customer complaint and the context behind it. Draft a reply that:
1. Acknowledges what happened in plain language.
2. Takes responsibility without overpromising.
3. Proposes one clear next step we can deliver this week.
4. Stays warm and respectful, not corporate.
Keep it under 120 words. Use British English.
Customer message:
"{paste the customer message here}"
Context they may not know:
"{any internal context, what went wrong, what we are doing about it}"
Laiškai Comms
Polite decline that does not burn the bridge
Say no clearly while keeping the relationship warm and the door open.
Draft a short reply that politely declines the request below. Make sure to:
1. Thank them for thinking of us.
2. Decline clearly without long apologies or excuses.
3. Suggest one alternative if you can think of a sensible one.
4. Keep the tone warm and the door open for the future.
Under 100 words.
Their request:
"{paste the request here}"
Laiškai Meeting
Meeting follow up email
Recap the meeting, confirm decisions, list action items with owners.
Write a short follow up email after the meeting described below. Use these sections:
Subject: short and specific.
Recap: 2 to 3 sentences in plain language.
Decisions: bullet list.
Actions: bullet list, each with an owner and a due date.
Next step: one sentence.
Friendly but professional tone. Under 200 words.
Meeting notes:
"{paste your meeting notes or transcript here}"
Laiškai Sales
Cold outreach intro
A short, human cold email with a specific reason to reply.
Write a short cold email to the prospect below. The email must:
1. Open with one specific observation about their business, not a generic compliment.
2. Explain in one sentence why we are reaching out.
3. Offer one specific, low commitment next step (a 15 minute call, a short example, a checklist).
4. End with a friendly sign off.
Under 90 words. No emojis. No buzzwords.
About the prospect:
"{their company, role, recent news or a real observation}"
About us:
"{one sentence on what we do and who we help}"
Laiškai Internal
Internal status update
A clean weekly update for your team or manager. Same format every week.
Draft my weekly update using these sections:
This week: what was shipped or progressed (bullets).
Next week: what I plan to do (bullets).
Blockers: anything I need help with (bullets, omit if none).
Notes: anything worth flagging that does not fit above.
Plain language, no corporate filler. Under 200 words.
My raw notes:
"{paste your week notes, bullet points, calendar items}"
Marketingas Social
Social post in 5 variations
One idea, five takes. Pick the one that fits the channel.
Take the idea below and produce five short social post variations. For each variation use a different angle:
1. Plain and informative.
2. A question that invites a reply.
3. A short story or anecdote.
4. A surprising stat or claim.
5. A bold opinion.
Each variation under 60 words. No hashtags unless asked. No emojis.
The idea:
"{your update, news, opinion or product}"
Marketingas Content
Blog post outline
A clear outline before you start writing, so the article stays on track.
Build a tight blog post outline on the topic below. Include:
Working title (3 options).
Reader: who this is for, in one sentence.
Promise: what they will know or be able to do after reading.
Sections: 5 to 7 H2 headings, each with 2 to 4 H3 subpoints.
Examples and stats to find: a short list.
Suggested CTA at the end.
Topic:
"{your topic}"
Audience:
"{who you are writing for}"
Marketingas Email / Content
Newsletter from raw notes
Turn three updates into a warm, short newsletter draft.
Write a short, warm newsletter from the notes below. Format:
Subject line: under 50 characters, specific.
Opening: 1 to 2 sentences, like talking to one reader.
Body: 3 short sections, each tied to one of the updates.
One CTA at the end.
Around 200 words total. Avoid hype words. British English.
My notes:
"{three things to include this issue}"
Marketingas Copy
Product description rewrite
Cleaner, more useful product copy without inventing features.
Rewrite the product description below. Make it:
1. Clear about what the product is in the first sentence.
2. Focused on benefits, not features.
3. Under 70 words.
4. Honest. Do not invent capabilities. If something is missing, ask me.
Original copy:
"{paste current description}"
Audience and tone:
"{who buys it and how the brand sounds}"
Marketingas Copy
Headline brainstorm (10 angles)
Ten distinct headline angles for the same topic.
Generate 10 headline options for the piece described below. Use a different angle for each:
1. Plain and direct.
2. How to.
3. Question.
4. Numbers / list.
5. Contrarian.
6. Story driven.
7. Quote driven.
8. Comparison.
9. Result driven.
10. Curiosity driven.
Keep each under 12 words. No clickbait. Mark the strongest 3 with a star.
The piece:
"{your topic, audience, key insight}"
Pardavimai Follow up
Quote follow up
A friendly, low pressure nudge after sending a quote.
Write a short follow up message for a customer who received a quote 5 days ago and has not replied. The message should:
1. Reference the original quote without quoting numbers.
2. Offer to answer questions or adjust scope.
3. Suggest a 10 minute call as the next step, with a clear ask.
4. Be friendly and low pressure.
Under 100 words.
Context:
"{customer name, what was quoted, anything you discussed}"
Pardavimai Calls
Discovery call agenda
A clean 30 minute agenda you can paste into the calendar invite.
Draft a 30 minute discovery call agenda for a first conversation with a prospective client. Include:
Opening: 3 minutes, who is who, what to expect.
Their context: 12 minutes, the questions you would ask.
What we do: 8 minutes, kept short.
Fit and next step: 7 minutes.
Plain language. Avoid sales jargon. Add 5 specific questions tailored to the prospect described below.
About them:
"{their industry, size, suspected need}"
About us:
"{one sentence on what we do}"
Pardavimai Proposal
Proposal cover letter
A short, warm letter that frames the proposal that follows.
Write a one page cover letter for the proposal described below. Sections:
Opening: 2 to 3 sentences, warm, references something specific from our conversation.
Why this proposal: 1 short paragraph.
What is inside: 3 to 5 bullets.
Next step: 1 sentence with a clear call to action.
Under 250 words.
Conversation notes:
"{what they said they need, in their words if possible}"
Proposal summary:
"{what you are proposing in 1 to 2 sentences}"
Pardavimai Calls
Objection handler
Three thoughtful ways to answer a tough objection.
A prospect raised the objection below. Suggest 3 distinct ways to respond. For each response:
1. State the response in 2 to 3 sentences.
2. Explain in one line when this response is the right one.
3. Note one risk of using it.
Stay honest. Do not pressure. Plain language.
Their objection:
"{paste the objection word for word}"
Context:
"{what they are buying, what stage we are at}"
Operacijos Meetings
Meeting summary recipe
A consistent meeting summary structure that people actually read.
Summarise the meeting below using this exact structure. Keep the whole thing under 250 words.
Context: 1 paragraph in plain language.
Decisions: bullet list, each one a complete sentence.
Open questions: bullet list.
Action items: 1 line each, with owner and due date if mentioned.
Neutral, factual tone. If something is unclear, say so explicitly.
Transcript:
"{paste meeting transcript or notes here}"
Operacijos Docs
Process documentation from notes
Turn rough notes into a usable step by step process.
Turn the notes below into a clean step by step process document. Use this structure:
Title.
Purpose: 1 to 2 sentences.
When to use it.
Roles involved.
Steps: numbered, one action per step, with the tool used in brackets.
What good looks like: 2 to 3 bullets.
Common pitfalls: 2 to 3 bullets.
Plain language. No fluff.
Raw notes:
"{paste your notes here}"
Operacijos Finance
Friendly invoice reminder
Polite, clear, useful. Includes the next step.
Draft a short, polite payment reminder for an invoice that is now {X} days overdue. The message should:
1. Reference the invoice number and original due date.
2. Assume good faith.
3. Offer to resend the invoice or clarify any question.
4. Mention the next step if it stays unpaid (in plain language, no threats).
Under 100 words. Warm but professional.
Details:
"{customer name, invoice number, amount, original due date, any prior reminders}"
Operacijos Procurement
Vendor or supplier brief
A short shortlist with criteria, options and a recommendation.
Build a short shortlist for the supplier or tool we need. Output:
Need: 2 to 3 sentences.
Must have: bullet list of non negotiables.
Nice to have: bullet list.
Options: 5 candidates, each with one line on the offer, a price range and a one line risk.
Recommendation: one option, with two reasons why and one caveat.
What we need:
"{describe the need, budget, region, any constraints}"
Operacijos Internal
Weekly team update
Same shape every week, easy to scan, easy to write.
Write our weekly team update in this exact shape:
Headline: one sentence on the most important thing.
Wins: 3 to 5 bullets.
In progress: 3 to 5 bullets.
Blockers and risks: bullets, or write "None this week".
Numbers: 2 to 4 simple metrics in a small table.
Asks: what we need from anyone reading.
Under 300 words. Friendly but factual.
My raw inputs:
"{everything from the week, in any order}"
Rašymas Editing
Tighten this paragraph
Shorter, sharper, no meaning lost.
Rewrite the paragraph below to be 30 to 50 percent shorter. Rules:
1. Keep every fact and every nuance.
2. Cut filler words, stage directions and throat clearing.
3. Prefer simple words over Latin ones.
4. Do not add anything that is not in the original.
Show the rewrite, then a one line note on what you cut and why.
Paragraph:
"{paste the paragraph here}"
Rašymas Editing
Plain language rewrite
Take dense or jargon heavy text and make it clear for non specialists.
Rewrite the text below for a non specialist reader. Constraints:
1. No jargon. If a technical word is essential, explain it in brackets the first time.
2. Short sentences. One idea per sentence.
3. Active voice where possible.
4. Same meaning. No new claims.
5. Same length or shorter.
Original:
"{paste original text}"
Reader:
"{who they are, what they already know}"
Rašymas Translation
Translate keeping the tone
Translate without flattening the voice.
Translate the text below from {source language} to {target language}. Constraints:
1. Keep the original tone and rhythm. If the original is warm and informal, the translation should feel the same.
2. Do not localise idioms unless the literal translation would not make sense.
3. Note any phrase you were not sure about at the end, with two alternatives.
Text:
"{paste original text}"
Rašymas Editing
Make this less corporate
Strip stiff, generic phrasing and make it sound human.
Rewrite the text below to sound like a real human wrote it. Constraints:
1. Cut all corporate filler ("we are excited to announce", "leverage", "synergies", "best in class").
2. Use specific words and concrete examples.
3. Keep all the facts.
4. Tone: warm, confident, plain.
Original:
"{paste text}"
Rašymas Learning
Explain like I am 14
A clear, simple explanation of any topic without dumbing it down.
Explain the topic below to a curious 14 year old. Constraints:
1. Use everyday language. No specialist words without a quick definition.
2. Use one or two analogies or examples from daily life.
3. Be honest about what is uncertain.
4. End with one question that invites curiosity.
Topic:
"{your topic, as specific as you can}"
Rašymas Meetings
Pre read for a meeting
A 1 page brief so everyone arrives prepared.
Write a 1 page pre read for the meeting described below. Use these sections:
Why we are meeting: 2 sentences.
What you need to know: 4 to 6 bullets, each a complete sentence.
What we will decide: bullet list.
What we will not decide today: bullet list.
Suggested questions to come prepared with: 3 questions.
Under 350 words. Plain language.
Meeting context:
"{topic, who is invited, what has happened so far}"
Pagalba Difficult
Apology with a real action
A clean apology that includes what you will actually do next.
Draft a short apology message for the situation below. It must include:
1. A clear acknowledgement of what happened, in their words.
2. A direct apology, no excuses.
3. One specific action you will take, with a date.
4. An open door for further questions.
Under 120 words. Warm and human.
The situation:
"{what happened from the customer's point of view, plus any internal context}"
Pagalba Comms
Status update to a waiting customer
Calm, honest update when a fix is taking longer than promised.
Write a short status update to a customer who is waiting on a fix. The update should:
1. Acknowledge the wait.
2. Tell them what is true right now (no spin).
3. Give the next concrete milestone with a date.
4. Tell them when they will hear from us again.
Under 100 words.
Context:
"{what they are waiting for, what changed, what you actually know}"
Pagalba Docs
FAQ from real questions
Turn the questions your team gets every week into a clean FAQ section.
Build an FAQ section from the customer questions below. Constraints:
1. Group similar questions together. Use the wording customers actually use as the question.
2. Each answer is 2 to 4 sentences. Plain language.
3. End each answer with a single sentence pointing to the next step (a link, a contact, a doc).
4. Output as a clean numbered list.
Customer questions:
"{paste your raw list of recent questions}"
Asmeninis Career
CV bullet rewriter
Stronger, sharper bullets for your CV without inflating the truth.
Rewrite the CV bullets below. Each bullet should:
1. Start with a specific verb.
2. Include a measurable outcome where possible (number, range or simple comparison).
3. Be one line, under 18 words.
4. Stay accurate. Do not invent results.
If a bullet is too vague to rewrite well, ask one specific question to make it stronger.
My current bullets:
"{paste your bullets here}"
Role context:
"{the role and the kind of job you are applying for}"
Asmeninis Career
Cover letter draft
A short, sincere cover letter you can adapt by hand.
Draft a short cover letter for the job described below. Constraints:
1. Under 250 words.
2. Open with one specific reason this role and this company appeal to you. No generic flattery.
3. Three short paragraphs: why this role, what I bring, what I would like to learn.
4. Tone: warm, confident, no buzzwords.
About me:
"{your background, key wins, current role}"
About the role:
"{job title, company, anything specific from the listing}"
Asmeninis Reflection
Weekly reflection
A short prompt to look back on the week and plan the next.
Walk me through a calm weekly reflection. Ask me one question at a time, wait for my answer, then move on.
Cover these in order:
1. What went better than expected this week?
2. What drained me and why?
3. What did I learn about my work?
4. What is the one thing that matters most next week?
5. What is one small change I will try next week?
End with a 5 line summary in my own words, suitable to keep in a notes file.
Šioje kategorijoje užklausų dar nėra.