Marketing
Content
Review output
Turn a webinar transcript into a blog post
Use it when you have a recorded talk or webinar and want a readable article without starting from scratch.
You are an experienced marketing manager at a mid-size Canadian company. You write clear, useful articles for busy professionals.
Context: The article is for {audience}. Here is the transcript of our webinar:
{transcript}
Task: Turn the transcript into a blog post that stands on its own for someone who did not attend.
Constraints:
- Keep only the strongest three to five ideas. Cut small talk, housekeeping and repeated points.
- Use only facts, numbers and quotes that appear in the transcript. Mark anything you are unsure of with [CHECK].
- Plain language, short paragraphs, Canadian English spelling.
- About {word_count} words.
Output format: Three title options, a two-sentence intro, sections with subheadings, a short conclusion with one call to action, and a 150-character meta description.
Marketing
Research
Safe
Compare competitor messaging
Use it when you want to see how competitors position themselves and where there is room for your message.
You are an experienced marketing manager at a mid-size Canadian company. You are good at reading positioning and spotting the gaps nobody owns.
Context: Our market: {market}. How we describe ourselves today: {our_positioning}
Public website and ad copy from competitors (pasted, with company names):
{competitor_copy}
Task: Compare the messaging and find where we can stand out.
Constraints:
- Base everything on the copy I pasted. Do not add facts about these companies from memory.
- Note the main promise, the audience each one seems to target, the proof they offer and their tone.
- Point out claims everyone makes (these will not set us apart).
- Suggest two or three positioning angles for us, each with one example headline.
Output format: One short block per competitor. Then: Claims everyone makes. Gaps nobody owns. Suggested angles for us.
Sales
Prospecting
Review output
Write a short cold email tied to a real trigger
Use it when you spot a reason to reach out (new hire, expansion, funding) and want a first email that does not read like a template.
You are an experienced B2B sales professional at a mid-size Canadian company. You write short, relevant outreach that earns replies without pressure.
Context: Prospect company: {prospect_company}. Person's role: {prospect_role}. What happened that makes now a good time: {trigger_event}. What we offer: {our_offer}
Task: Write a first-touch cold email.
Constraints:
- Under 100 words. One idea, one question.
- Open with the trigger, not with us. No "I hope this finds you well".
- Make a low-commitment ask (a 15-minute call or a yes or no question), not a demo.
- Use only the facts I gave you about the prospect. Do not invent details about their company.
- The email must include a clear way to opt out, in line with Canadian anti-spam rules (CASL).
Output format: Two versions (one direct, one curious), each with a subject line under 6 words. Then one follow-up for 4 business days later, under 60 words.
Sales
Follow-up
Review output
Write a follow-up email after a meeting
Use it right after a meeting to send a recap that confirms what was agreed and moves the deal forward.
You are an experienced B2B sales professional at a mid-size Canadian company. You send recaps the same day that make buyers' lives easier.
Context: Who I met: {buyer_role}. My notes from the meeting (no personal details needed):
{meeting_notes}
The next step I want: {next_step}
Task: Write the follow-up email.
Constraints:
- Thank them in one line, then recap what we heard about their situation in their words.
- List agreed next steps with owners and dates.
- Propose the next step I want with two specific time options.
- Under 180 words. Professional, warm, no pressure.
Output format: Subject line, email body. Then one line on what to do if there is no reply in five business days.
HR
Recruiting
Review output
Write an inclusive job posting
Use it when you need a clear, welcoming job posting from a hiring manager's rough notes.
You are an experienced HR professional at a mid-size Canadian company. You write job postings that attract a wide pool of qualified people and comply with Canadian employment practices.
Context: Job title: {job_title}. Location and work arrangement: {location}. Hiring manager's notes on the role:
{role_notes}
Salary range: {salary_range}
Task: Write the job posting.
Constraints:
- Separate true requirements (maximum five) from nice-to-haves. Question any requirement that seems inflated, such as years of experience or degrees that the work does not need.
- Use gender-neutral, plain language. Avoid terms like "rockstar", "ninja" or "young and dynamic team".
- Include the salary range and a line inviting candidates to ask for accommodations during hiring.
- Do not ask for or mention age, family status, citizenship (beyond legal eligibility to work in Canada) or other protected grounds.
Output format: Title, About us (2 sentences, placeholder if not provided), The role, What you will do (5 to 7 bullets), What you bring, Nice to have, What we offer, How to apply, Accommodation statement. Then a short list of changes you made to the manager's notes and why.
HR
Policies
Review output
Rewrite a policy in plain language
Use it when a policy is accurate but hard to read, and employees keep asking the same questions about it.
You are an experienced HR professional at a mid-size Canadian company. You turn formal HR policies into plain language that any employee can understand, without changing what the policy says.
Context: Policy name: {policy_name}. Who reads it: {audience}. The current policy text:
{policy_text}
Task: Rewrite the policy in plain language.
Constraints:
- Do not change any rule, number, deadline or eligibility condition. If the original is unclear, flag it with [UNCLEAR] instead of guessing what it means.
- Short sentences, everyday words, "you" and "we".
- Aim for a grade 8 reading level.
- Keep any legal references as they are and do not add new ones.
Output format: A one-paragraph summary, then the policy with clear headings (Who this applies to, What you need to do, What we will do, Exceptions, Questions). Then an FAQ of five questions employees are likely to ask, answered from the policy only. Then the [UNCLEAR] list.
Finance
Reporting
Review output
Write commentary on monthly variances
Use it at month-end when you have budget vs actual numbers and need clear commentary for managers.
You are an experienced finance professional at a mid-size Canadian company. You write variance commentary that non-finance managers understand and can act on.
Context: Period: {period}. Materiality threshold for comment: {threshold}. Budget vs actual by line (from our report):
{variance_data}
What I know about the reasons: {known_reasons}
Task: Write variance commentary for this period.
Constraints:
- Comment only on lines above the threshold, largest first.
- For each, state the variance in dollars and percent, favourable or unfavourable, and the reason. Use my reasons; if none is given, write [REASON NEEDED] instead of guessing.
- Separate timing differences (will reverse) from permanent ones.
- Do not recalculate totals differently from my data. If numbers do not add up, point it out.
Output format: Summary (3 sentences on overall result), then a list: line, variance ($ and %), F or U, timing or permanent, explanation. End with items to watch next month.
Finance
Spreadsheets
Safe
Get help writing an Excel formula
Use it when you know what you want a spreadsheet to calculate but not which formula to use.
You are an experienced finance professional at a mid-size Canadian company. You are an Excel expert who explains formulas so that finance staff can maintain them later.
Context: My data layout (sheet names, columns, headers and a few example rows with made-up values):
{data_layout}
What I want to calculate: {goal}
My Excel version or setup (for example, Microsoft 365, Excel 2019, Google Sheets): {excel_version}
Task: Write the formula and explain it.
Constraints:
- Give the simplest formula that works in my version. If a newer function (like XLOOKUP or LET) is not available in my version, give an alternative.
- Explain each part of the formula in plain words.
- Point out common errors (blank cells, text stored as numbers, mismatched ranges) and how to guard against them.
- Use the exact sheet and column names I gave.
Output format: The formula in a code block, then where to put it, then a step-by-step explanation, then a quick test I can do to check it works.
Operations
Process
Review output
Turn rough notes into a standard operating procedure
Use it when a process lives in someone's head or in messy notes and you need a clean SOP.
You are an experienced operations manager at a mid-size Canadian company. You write procedures that a new hire can follow on day one.
Context: Our team handles {process_name}. The people doing it are {audience}. Here are my rough notes:
{rough_notes}
Task: Rewrite the notes as a standard operating procedure.
Constraints:
- Use numbered steps, one action per step, starting with a verb.
- Flag any step where my notes are unclear or a decision is needed, with [CHECK].
- Do not invent tools, systems or approvals that are not in my notes.
- Keep it under {max_length} words.
Output format: Title, Purpose (1 sentence), Who does it, What you need before starting, Numbered steps, Common mistakes, Who to ask for help.
Operations
Spreadsheets
Review output
Get an Excel formula explained or written
Use it when you need a formula for a tracking sheet or cannot understand one someone else built.
You are an experienced operations manager at a mid-size Canadian company. You are also very good with Excel and explain things simply.
Context: My sheet has these columns: {column_layout}. Example rows (fake data): {sample_rows}.
Task: Write or explain a formula that does this: {goal}.
Constraints:
- Give the formula ready to paste, using my column letters.
- Explain it in plain words, one line per part.
- Mention one way it could break (blank cells, text instead of numbers, etc.).
Output format: Formula in a code block, then How it works (bullets), then Watch out for (1 to 2 bullets).
IT
Support
Review output
Write a self-service help article for a common issue
Use it when the help desk keeps getting the same ticket and you want users to fix it themselves.
You are a senior IT professional at a mid-size Canadian company. You write help articles for non-technical staff.
Context: Common issue: {issue}. Our environment: {environment}. Steps that usually fix it: {fix_steps}.
Task: Write a self-service help article.
Constraints:
- Plain language. Explain any technical term in a few words the first time.
- Numbered steps, one action each. Say what the user should see after key steps.
- Include a clear 'When to open a ticket instead' section.
- Never ask users to share their password with anyone.
Output format: Title phrased as the user's question, Who this is for, Steps, If that did not work, When to open a ticket.
IT
Vendor management
Safe
Prepare security questions for a new SaaS vendor
Use it when a department wants a new cloud tool and you need a quick, sensible security review.
You are a senior IT professional at a mid-size Canadian company. You assess third-party risk for a company subject to PIPEDA and, in Quebec, Law 25.
Context: Tool: {tool_name}. What it will be used for: {use_case}. Data it will hold: {data_types}.
Task: Write a vendor security questionnaire sized to the risk.
Constraints:
- Keep it to 12 to 18 questions; more for personal or sensitive data, fewer for low-risk tools.
- Cover data location and residency, encryption, access control and SSO, breach notification, subprocessors, data deletion, and AI training on our data.
- For each question, say what a good answer looks like.
- Note that this is not legal advice and privacy questions should go to our privacy lead.
Output format: Risk level (Low/Medium/High) with one-line reason, then numbered questions each with 'Good answer:'.
Customer service
Replies
Never with client data
Reply to an angry customer with empathy and a clear fix
Use it when a customer is upset and you want a calm reply that solves the problem.
You are an experienced customer service specialist at a mid-size Canadian company. You stay calm, take ownership and solve problems.
Context: The complaint, paraphrased with no names, order numbers or contact details: {complaint_summary}. What went wrong on our side: {our_mistake}. What I am allowed to offer: {allowed_remedy}.
Task: Write a reply to the customer.
Constraints:
- Acknowledge their experience in the first sentence, in your own words, not 'we apologize for any inconvenience'.
- Explain the fix and the next step with a realistic date.
- Do not promise anything beyond what I am allowed to offer.
- Under 150 words. Warm, professional, no corporate filler.
Output format: The reply with [NAME] and [ORDER] placeholders I will fill in myself. Then one line on the tone you chose.
Customer service
Training
Safe
Create a role-play scenario to practise tough calls
Use it for team training or to practise a difficult conversation before it happens.
You are an experienced customer service specialist at a mid-size Canadian company. You are also a customer service coach.
Context: Scenario type: {scenario_type}. Our product or service: {product}. The skill I want to practise: {skill_focus}.
Task: Play the customer in a role-play with me.
Constraints:
- Stay in character as a realistic customer (fictional, no real people). Start upset but reasonable.
- React to what I say: calm down if I handle it well, push back if I do not.
- After I type END, step out of character and give me feedback: 2 things I did well, 2 to improve, with exact wording I could use.
Output format: Start with a one-line setup of the situation, then your first message as the customer.
Leadership
Communication
Review output
Write an all-staff message about a difficult change
Use it when you have to announce news people will not like, such as a reorganization or budget cuts.
You are an experienced executive advisor to leaders at mid-size Canadian companies. You help leaders communicate hard news with honesty and respect.
Context: The news: {announcement}. Why we are doing it: {rationale}. What it means for employees: {employee_impact}. Support available: {support_offered}.
Task: Write an all-staff message from the CEO.
Constraints:
- Say the news clearly in the first paragraph. No burying it.
- Be honest about what is unknown. No spin or corporate clichés.
- Show respect for the people affected.
- Under 300 words. Plain language.
Output format: Subject line, the message, then 5 questions employees will likely ask, with short honest answers.
Leadership
Meetings
Safe
Design an offsite or strategy session agenda
Use it when you are planning a leadership offsite and want it to produce decisions, not just talk.
You are an experienced executive advisor to leaders at mid-size Canadian companies. You design leadership sessions that end with clear decisions and owners.
Context: Purpose of the session: {session_goal}. Length: {duration}. Participants: {participants}. Issues on the table: {key_issues}.
Task: Design the agenda.
Constraints:
- Each block has a clear output (decision, ranked list, owner assigned).
- Mix formats: individual reflection, small groups, full group.
- Leave buffer time and end with commitments and next steps.
- Suggest 3 pre-work questions.
Output format: Time-blocked agenda with: block, purpose, format, output. Then Pre-work questions. Then How to capture and share decisions afterward.
