Most people who are disappointed by AI tools are typing one-line requests like “write an email to a client about the delay.” They get back something generic, conclude AI isn’t that useful, and move on. The difference between a forgettable answer and a genuinely useful one is usually not the tool. It’s the prompt.
You don’t need to become a “prompt engineer.” You need a simple structure and a handful of tested templates your team can reuse. Both are below, ready to copy.
Key takeaways
- Good prompts have five parts: role, task, context, format and constraints.
- Context is the biggest lever. Give the AI what a new employee would need to know.
- Ask for a draft, then refine it in conversation. The first answer is a starting point.
- Save prompts that work as shared team templates. That’s where the real time savings come from.
- Never paste confidential or personal data into tools your company hasn’t approved.
The anatomy of a good business prompt
1 · Role
Who should it be?
“You are an experienced customer service lead at a regional accounting firm.”
2 · Task
What exactly to do
“Draft a reply to the client email below explaining the delay.”
3 · Context
What it needs to know
“They’re a long-time client. The delay is because we’re waiting on their bank statements.”
4 · Format
What it should look like
“Under 120 words, friendly but professional, end with a clear next step.”
5 · Constraints
What to avoid
“Don’t blame the client. Don’t promise a date. If anything is unclear, ask me.”
Before and after
Before
Write an email to a client about the delay.
Result: a vague, generic apology that could be from any company, and that you’ll rewrite from scratch.
After
You are a client service lead at a small accounting firm. Draft a reply to the client email below about the delay on their quarterly return. Context: they've been a client for 6 years. We're waiting on their September bank statements, which we requested on the 3rd. Format: under 120 words, warm and professional, plain English. End with one clear next step for them. Constraints: don't sound like we're blaming them. Don't promise a completion date. Client email: [paste, with account numbers removed]
Result: a specific, on-brand draft that needs a light edit, not a rewrite.
Prompt template library
Pick a department, copy a template, and fill in the [brackets]. Each one follows the five-part structure.
Copy & paste
Templates by department
You are an operations coordinator. Turn the meeting notes below into: 1) a 3-sentence summary, 2) a table of action items with owner and due date, 3) open questions. If an owner or date isn't stated, write "TBD" rather than guessing. Notes: [paste]
You are a process documentation specialist. Write a step-by-step SOP for [process] for a new employee with no prior knowledge. Include: purpose, when to use it, numbered steps, common mistakes, and who to ask for help. Keep each step to one action. Here's how we do it today, in rough notes: [paste]
Summarize the document below for a busy business owner. Format: 5 bullet points maximum, then "What this means for us" in 2 sentences, then any deadlines or dollar amounts mentioned. Quote exact figures; don't round or estimate. Document: [paste, with confidential details removed]
You are a consultative salesperson for [company], which provides [service] to [type of customer]. Write a follow-up email after a first call with a prospect. Context: [what they said their main problem was, in their words]. Format: under 120 words, one clear call to action ([book a 20-min demo]). No hype words like "revolutionary" or "game-changing".
You are a B2B content marketer. Turn the idea below into 5 LinkedIn posts for [company], each with a different angle: a tip, a common mistake, a quick story, a question to the audience, and a myth vs fact. Audience: [who]. Tone: practical and plain-spoken. Each post under 150 words with one line of hashtags. Idea: [paste]
Act as a conversion copywriter. Review the web page copy below for a [type of business] targeting [audience]. Give me: 1) the 3 biggest weaknesses, 2) a rewritten headline and subheadline (3 options each), 3) a clearer call to action. Don't invent claims, statistics or testimonials. Copy: [paste]
You are a senior customer service rep for [company]. Draft a reply to the frustrated customer message below. Acknowledge the specific problem, take responsibility where we're at fault, explain what happens next, and give a timeframe only if I provide one: [timeframe or "none"]. Tone: calm, human, not defensive. Under 150 words. Message: [paste, with personal details removed]
Using ONLY the policy text below, write answers to the 10 questions customers are most likely to ask about it. If the policy doesn't answer something clearly, say "Not covered - check with [team]" rather than guessing. Plain English, under 60 words per answer. Policy: [paste]
You are an HR generalist at a [size] [industry] company. Write a job description for a [role]. Include: a 2-sentence role summary, 5-7 responsibilities, must-have vs nice-to-have qualifications, and what makes this a good place to work: [2-3 true facts about your company]. Use inclusive, plain language and avoid jargon and unnecessary requirements (like degrees that aren't truly needed).
I'm a manager preparing for a conversation with an employee about [situation, described without names]. Help me plan it: 1) key points to make, 2) how to open the conversation, 3) likely reactions and how to respond, 4) a clear, fair next step. Keep it respectful and focused on behavior, not personality.
You are an IT support lead. Explain the issue below to non-technical staff in plain English: what happened, how it affects them, and exactly what they need to do (numbered steps). Under 150 words. No jargon; if a technical term is unavoidable, explain it in one short phrase. Issue: [paste]
Write an internal announcement about [change, e.g. new password policy / new software] taking effect [date]. Include: what's changing, why (in one sentence), what employees must do and by when, and who to contact for help. Tone: friendly and direct. Under 200 words. Add a short subject line.
Five habits of people who get great results
- Treat it like a conversation. If the first draft is off, say what’s wrong: “shorter,” “less formal,” “you missed the part about pricing.” Iterating beats rewriting the prompt from scratch.
- Give examples. Paste one of your best past emails or reports and say “match this style.” It’s the fastest way to get your voice.
- Tell it to ask questions. Ending with “ask me anything you need before you start” often produces a much better result.
- Ask it to show uncertainty. “If you’re not sure about something, say so” reduces confident-sounding mistakes. You still need to fact-check.
- Save what works. Keep a shared document or folder of your team’s best prompts. Many business AI plans also let you save reusable instructions or custom assistants.
Frequently asked questions
Do these prompts work in ChatGPT, Claude, Gemini and Copilot?
Yes. The five-part structure works with any modern AI assistant. Results vary a little between tools, so test your most-used templates in whichever tool your company has approved.
How long should a prompt be?
As long as it needs to be to give the context a capable new employee would need. That’s often 5–15 lines. Longer isn’t better for its own sake, but one-liners almost always produce generic output.
Can I trust what the AI writes?
Treat it as a capable first draft from someone who sometimes makes things up confidently. Check every fact, figure, name and claim before it goes to a client or the public.
Next step
Turn good prompts into measurable results
Pick one workflow, give your team these templates, and measure the difference. Our six-week pilot guide includes a free ROI scorecard.
