Prompt library — 21 prompts
SOPs, workflows, handoffs and the small automations that remove copy-paste work.
Use this before automating anything — you can't automate a process you haven't actually mapped.
Walk me through mapping this process step by step: [DESCRIBE THE PROCESS IN YOUR OWN WORDS, ROUGHLY]. Ask me clarifying questions one at a time about who does each step, what tool is used, and how long it takes, until we have a complete numbered map with no gaps.
Use this once a process is mapped and needs to be documented for someone else to run.
Turn this into a written SOP: [PASTE PROCESS DESCRIPTION OR MAPPED STEPS]. Format: purpose (one sentence), numbered steps with the tool used at each step, who's responsible, and a 'what could go wrong' note for any step with a real failure risk. Write for someone doing this for the first time.
Use this right after a meeting instead of manually re-reading notes to find what actually got decided.
Here are my raw meeting notes or a transcript: [PASTE]. Extract: decisions made (stated as facts, not discussion), action items with an owner and due date if mentioned, and open questions that weren't resolved. Don't include general discussion points that didn't lead anywhere.
Use this to separate 'automate this' from 'this needs a human' before building anything.
Here's a process: [PASTE MAPPED PROCESS OR DESCRIPTION]. For each step, tell me: is this a good automation candidate (rule-based, repetitive, low judgment required) or does it need human judgment and should stay manual. Be honest — don't recommend automating steps that involve real discretion or client-specific nuance.
Use this to compare tools on criteria that matter for the actual task, not feature-list marketing.
I'm evaluating tools for [SPECIFIC TASK/NEED]. Options I'm considering: [LIST TOOLS]. Build a comparison framework with criteria that actually matter for this task (not generic ones): [LIST 4-5 CRITERIA RELEVANT TO YOUR NEED, e.g. integrates with X, handles Y volume, team can learn it in a day]. Score each option against the criteria based on what I tell you about them.
Use this when delegating something you've been doing yourself and don't want to become the bottleneck for.
I'm handing off [TASK/RESPONSIBILITY] to [PERSON/ROLE]. Help me write a handoff doc: what the task involves, where to find everything needed [FILES/TOOLS/LOGINS TO REFERENCE], the recurring schedule if any, and who to ask if something's unclear. Written so nothing depends on asking me directly.
Use this to build the template once, then reuse it every week instead of freeform reviewing.
Build a weekly ops review template for [BUSINESS TYPE/TEAM]. Sections: what shipped this week, what's blocked and why, any process that broke or felt slow, and one thing to fix next week. Keep it short enough to fill in 10 minutes.
Use this once to build a template, then fill it in per project instead of starting from a blank doc.
Build a reusable project brief template for [TYPE OF PROJECT YOU RUN REPEATEDLY]. Sections: objective, scope (in/out), timeline with milestones, stakeholders and their role, and success criteria. Keep every section short — this is a brief, not a full plan.
Use this to plan an automation in plain language before building it in a tool like Make.
Here's my current client intake process: [DESCRIBE STEPS]. Help me describe how this could work as an automated flow: trigger, each step in sequence, what data moves where, and where a human needs to review before it continues. I'll hand this description to whoever builds the actual automation.
Use this for the first or second reminder — direct but not adversarial.
Write a payment reminder email for an invoice that's [NUMBER] days overdue, to a client I have a good relationship with. Reference the invoice number and amount, assume it's an oversight rather than a refusal, and state the next step plainly (pay by X or let me know if there's an issue).
Use this to build a reusable checklist rather than remembering onboarding steps from memory each time.
Build an onboarding checklist for a new [ROLE] joining [TEAM/BUSINESS TYPE]. Group into: before day one (accounts, access), first week (tools to learn, people to meet, first task), and first month (what success looks like by day 30). Keep each item action-based, not vague ('get familiar with').
Use this quarterly to keep your task list from quietly growing with things that no longer earn their time.
Here's a list of tasks I do regularly: [LIST TASKS AND ROUGH FREQUENCY]. For each, tell me whether it's a candidate to automate, delegate to someone else, or drop entirely because it doesn't actually move anything forward. Ask me follow-up questions if you need more context on any task.
Use this when the same problem keeps recurring despite quick fixes.
This keeps causing delays: [DESCRIBE THE RECURRING PROBLEM]. Help me diagnose the actual root cause rather than the symptom — ask me clarifying questions about where in the process this shows up, who's involved, and what's been tried already. Don't propose a fix until we've confirmed the real cause.
Use this to organize a decision you already have information for, not as a live research tool.
I'm choosing between [TOOL/VENDOR A] and [TOOL/VENDOR B] for [SPECIFIC USE CASE]. Based on what I know about each [LIST WHAT YOU KNOW], build a comparison on: cost at my scale, learning curve for my team, and how well it fits this specific use case (not general reputation). Tell me what you don't have enough information to judge.
Use this before importing messy data into a CRM or automation tool.
I have a spreadsheet with [DESCRIBE THE MESS — duplicate entries, inconsistent formatting, missing fields]. Write me step-by-step instructions to clean this up manually, or a script/formula approach if it's repetitive enough to automate. Flag anything where cleaning risks losing information rather than just standardizing it.
Use this to build a reusable report structure instead of reformatting from scratch each period.
Build a template for my [FREQUENCY] report on [WHAT IT COVERS — e.g. content performance, client pipeline]. Sections: the 3-4 metrics that actually matter for this, a one-line 'what changed since last time', and a 'what I'm doing about it' line. Keep it skimmable in under a minute.
Use this when scheduling is eating more back-and-forth than the actual meeting is worth.
Here's how scheduling currently works for [CALLS/WORKSHOPS/CLIENT SESSIONS]: [DESCRIBE CURRENT PROCESS]. Identify where back-and-forth is happening that a scheduling tool or template could remove, and draft the email/message template that replaces the manual coordination step.
Use this to find documentation gaps before they become a problem, not after.
Here's a list of my current documented processes: [LIST WHAT'S DOCUMENTED]. Based on the tasks I do regularly [LIST YOUR REGULAR TASKS], tell me what's undocumented that would cause a problem if I were unavailable for two weeks. Prioritize the gaps by risk, not by ease of documenting.
Use this for processes where context matters as much as the steps themselves.
Write process documentation for [SPECIFIC TASK] aimed at someone who has never done it before and doesn't have context on why it's done this way. Include the 'why' briefly for each major step, not just the 'what' — that's what prevents them from doing it wrong when something unexpected happens.
Use this to build a business case for automation that will hold up to scrutiny, not just sound good.
I want to propose automating [PROCESS] to [DECISION-MAKER/CLIENT]. Current time cost: [HOURS/FREQUENCY]. Help me frame the case: time saved, error/risk reduced, and what stays human either way (so it's clear this isn't about replacing judgment). Keep the numbers conservative and defensible, not inflated.
Use this to introduce a new AI tool to a team without it landing as either a mandate or a gimmick.
We're rolling out [TOOL/WORKFLOW] to the team for [PURPOSE]. Write the announcement message: what's changing, why (tie to a real problem it solves), what stays exactly the same (reduce anxiety about scope creep), and where to get help or flag issues. No hype language about the tool itself.