How to Use Claude for Operations:
The Workflows That Run Your Business on Autopilot

Write a standard operating procedure for this process: [process name] Here's how we currently do it (rough notes or brain dump): [Paste your notes — even messy bullet points work] Who performs this process: [role] How often: [daily / weekly / as-needed] What systems or tools are involved: [list them] What can go wrong, and what should they do: [known failure points] What does "done correctly" look like: [the quality check] Format: - Title and purpose statement (2 sentences) - Prerequisites / what to have ready before starting - Numbered steps (be specific enough that someone new could follow this) - Troubleshooting section for common issues - Notes or exceptions at the bottom Plain language. Imperative voice ("Click X," not "The user should click X"). Flag any step where I was vague so I can clarify.

Draft a [weekly / monthly] operations report for [date range]. Here are my notes and key data points: [Paste your raw notes, metrics, highlights, and lowlights] Report audience: [leadership team / board / department heads] What they care most about: [e.g. efficiency, cost, headcount, velocity] Format we use: [executive summary + section breakdowns / bullet-only / narrative] Structure the report with: 1. Executive summary (3–4 sentences — what happened and what it means) 2. Key metrics (format as a simple table or labeled bullets) 3. Highlights — what went well and why it matters 4. Issues / blockers — what's at risk and what we're doing about it 5. Next week's / next month's priorities Write in [formal / conversational] language. Flag any data point I gave you that seems off or needs verification.

Write a vendor email for this situation: [describe the situation] Examples: - Requesting a price reduction or renegotiation - Escalating a service delivery issue - Requesting an updated contract or statement of work - Following up on an unresolved issue after 2+ weeks Vendor details: [who they are, what service they provide, how long we've worked with them] Our position: [what we want / need, and why] Tone: [firm but professional / collaborative / direct] What we're prepared to do if this isn't resolved: [optional — helps Claude calibrate leverage] Write the email with: - A specific subject line - Clear opening that states the purpose - Context (brief — they know the background) - Our specific ask or concern - A proposed next step with a timeline - Professional close Under 200 words. No filler. Don't be apologetic about asking for what we need.

Build a meeting agenda for a [60-minute / 30-minute] [meeting type — e.g. weekly ops sync / quarterly planning / vendor review]. Attendees: [roles, not names] Meeting goal: [what decision or alignment do we need to leave with] Topics to cover: [list them, rough is fine] Any known tension or difficult topic: [optional but helpful] Format: - Meeting title and time allocation - Pre-read or prep (if anything) - Agenda items in order, with time allocation for each - Decision or output for each item - Parking lot section at the bottom Keep it tight. Every item should have a clear purpose.

Here are my raw notes from our [meeting name] meeting today: [Paste notes — even messy stream-of-consciousness] Extract and format: 1. Decisions made (clear, definitive statements — not "we discussed") 2. Action items — each one must have: what, who, by when 3. Open questions that still need resolution 4. A 3-sentence summary I can share with people who weren't in the room Format action items as a table: | Action | Owner | Due Date | Flag any action item where ownership or deadline wasn't clearly stated.

I need to document our [department / function] process for [purpose — e.g. onboarding a new manager / audit prep / team alignment]. Here's what I know about how it currently works: [Describe the process — who does what, in what order, using what tools] Key inputs (what triggers the process or is required to start): [list] Key outputs (what is produced at the end): [list] Systems involved: [tools, software, platforms] Key handoff points between teams or roles: [describe them] Where things commonly break down: [known failure modes] Create a process document with: - Process overview (what it is and why it exists — 2 paragraphs) - Process map narrative (step by step, with responsible role at each step) - Systems and tools reference - Key handoffs and dependencies - Common issues and how to handle them - Metrics or quality checks (if applicable) Clear, structured, skimmable. Someone new to the role should be able to read this and understand how the function operates.

Write a job description for this role: [job title] Role brief: - What this person will own day-to-day: [list main responsibilities] - What success looks like in 90 days: [specific outcomes] - What success looks like in 12 months: [longer-term impact] - Must-have experience or skills: [list] - Nice-to-have: [list] - Who they'll report to: [role] - Who they'll work with: [teams or roles] - Compensation range (optional): [range] Company: [1-2 sentences about what you do and who you are as a company] Culture or working style: [e.g. async-first, fast-moving, high trust] Write a job description that: - Has a compelling opening that describes the role's impact (not just duties) - Lists responsibilities in plain language (not vague corporate phrases) - Is honest about what's hard about the role - Describes the type of person who will thrive here (not just qualifications) No "rockstar," "ninja," or "passionate." Write for people, not ATS systems.

Write an internal company policy for: [policy topic — e.g. expense reimbursement, remote work, PTO] Here's what I want the policy to cover: [Describe your intent in plain language — even rough notes work] Context: - Company size: [headcount range] - Who this policy applies to: [all employees / specific roles / contractors] - Any existing rules or constraints: [e.g. state laws, current informal norms] - Tone I want: [formal and official / clear and conversational / brief and direct] - Anything I want to avoid or that's been a problem: [optional but helpful] Write a policy document with: - Policy title and effective date placeholder - Purpose statement (why this policy exists) - Scope (who it applies to) - Policy details (the actual rules, clearly written) - Process (how to use or apply the policy) - Exceptions and approval process - Questions / contact section Plain language. No legal jargon unless required. Flag any area where I should consult an employment attorney before finalizing.