# Agency Operations AI Pack Version 1.0 By ReadyOps AI Twenty-five practical prompts for freelancers and small agency owners who need stronger client communication, faster proposals, cleaner reporting, and firmer scope control without building an operations department. Built for 1 to 10 person shops. ## Positioning Everything you need to run your client relationships with AI — proposals, onboarding, reporting, and offboarding. ## Who This Is For Use this pack if you regularly need to: - onboard new clients without missing details - turn loose sales calls into scoped proposals and SOWs - explain progress clearly without rewriting every update from scratch - chase invoices professionally without sounding awkward - push back on scope creep without damaging the relationship - end engagements in a way that creates referrals, testimonials, and case studies ## How To Use This Pack Copy a prompt into ChatGPT, Claude, or a similar model and replace the bracketed fields with your real details. For the best result: 1. Paste your real notes, call transcripts, or email threads instead of summaries whenever possible. 2. State the client type, project type, timeline, budget range, and tone you want. 3. Ask the model to flag missing inputs before drafting if the stakes are high. 4. Edit the final output for accuracy, commercial judgment, and relationship context before sending. ## Reusable Prompt Upgrades Add any of these lines to the end of a prompt when useful: - "Ask up to 5 clarifying questions before drafting if important information is missing." - "Keep the tone calm, credible, and agency-owner professional." - "Avoid hype, filler, and vague promises." - "Make the next step explicit." - "Flag anything that creates delivery, pricing, or scope risk." ## Recommended Client Brief Template Use this mini-brief to strengthen any prompt in the pack: ```text Client: Industry: Project type: Primary goal: Decision-maker: Budget range: Timeline: Current status: Known risks or sensitivities: Source material: [paste sales notes, call transcript, thread, or draft] ``` --- ## 1) Client Onboarding AI Prompts ### Prompt 1: First Client Welcome Email **Use when:** The deal is closed and you need a polished first email that feels organized from day one. ```text Act as an experienced client success manager for a boutique agency. Write a first welcome email for a new client. Context: - Client name: - Client company: - Service purchased: - Main objective: - Main contact: - Kickoff date: - Assets or access needed first: - Tone: [warm / polished / direct] Instructions: - Thank them briefly for choosing us. - Reinforce the project goal in one sentence. - Tell them what happens next. - Request the first materials or access clearly. - Confirm the kickoff date if available. - Keep the email friendly, organized, and confident. Output: 1. Subject line 2. Final email 3. Shorter version under 140 words ``` **Example input** ```text Client name: Maya Patel Client company: Northshore Studio Service purchased: monthly email marketing management Main objective: increase qualified demo bookings Main contact: Maya Patel, Founder Kickoff date: May 12 Assets or access needed first: brand guide, Klaviyo access, recent campaign results Tone: warm ``` ### Prompt 2: Kickoff Agenda Builder **Use when:** You want a kickoff meeting agenda that sounds strategic instead of generic. ```text Create a client kickoff meeting agenda for an agency engagement. Context: - Client: - Engagement type: - Contract term: - Core goal: - Known risks: - Internal team attending: - Client team attending: - Desired meeting length: Instructions: - Start with project outcomes, not introductions. - Include sections for goals, scope, process, timelines, communication, dependencies, and risks. - Add suggested time blocks. - Include the key questions we should ask live. - End with decisions and next steps. Output: 1. Final agenda 2. Top 5 questions to ask if time is tight 3. Follow-up action checklist ``` **Example input** ```text Client: BrightPath Health Engagement type: website redesign Contract term: 10 weeks Core goal: improve conversion rate on service pages Known risks: late content approvals Internal team attending: strategist, designer, PM Client team attending: marketing lead, founder Desired meeting length: 60 minutes ``` ### Prompt 3: Onboarding Questionnaire Draft **Use when:** You need a questionnaire that collects the right client inputs without overwhelming them. ```text Design a client onboarding questionnaire for a service business. Context: - Service: - Client sophistication level: [first-time buyer / experienced buyer] - What we need to start: - What usually causes delays: - Preferred format: [email / form / doc] Instructions: - Group questions into logical sections. - Ask only questions that affect delivery quality, speed, or risk. - Keep questions clear and plain-English. - Separate must-have inputs from nice-to-have inputs. - Include one short intro paragraph explaining why the questionnaire matters. Output: 1. Final questionnaire 2. Must-have items only version 3. Suggested completion deadline note ``` **Example input** ```text Service: LinkedIn ghostwriting retainer Client sophistication level: first-time buyer What we need to start: positioning, audience, offer, voice samples, founder calendar What usually causes delays: slow feedback, missing approvals, vague topics Preferred format: form ``` ### Prompt 4: Expectations-Setting Message **Use when:** You want to set boundaries and working norms before confusion starts. ```text Write an expectations-setting message for a new client engagement. Context: - Service: - Delivery cadence: - Feedback process: - Revision limit: - Preferred channels: - Response-time norm: - Client responsibilities: - Tone: Instructions: - Sound helpful, not defensive. - Explain how communication, approvals, and revisions will work. - Clarify what the client needs to provide on time. - Prevent common misunderstandings before they happen. - End with a collaborative note. Output: 1. Final message 2. Bullet summary for an onboarding doc 3. One-sentence version for Slack or email ``` **Example input** ```text Service: paid ads management Delivery cadence: weekly updates, monthly review Feedback process: comments in shared doc within 2 business days Revision limit: 2 rounds on creative strategy docs Preferred channels: email and Slack Response-time norm: 1 business day Client responsibilities: provide approvals, tracking access, landing page edits Tone: direct ``` ### Prompt 5: Welcome Packet Outline **Use when:** You need a simple but professional welcome packet for a new client. ```text Build a welcome packet outline for a small agency client. Context: - Agency type: - Services included: - Client type: - Project duration: - Communication tools: - Reporting cadence: - Key policies: Instructions: - Organize the packet into sections the client can skim quickly. - Include the essentials: team roles, timeline, communication, feedback, approvals, file sharing, and billing norms. - Keep the tone premium and reassuring. - Avoid internal jargon. Output: 1. Welcome packet outline 2. Suggested one-paragraph intro 3. Checklist of attachments or links to include ``` **Example input** ```text Agency type: content strategy studio Services included: messaging, editorial planning, thought leadership drafts Client type: B2B SaaS founder Project duration: 3 months Communication tools: email, Notion, Zoom Reporting cadence: weekly summary every Friday Key policies: 2 review rounds, approvals needed before publishing ``` --- ## 2) Proposal & SOW Generator Prompts ### Prompt 6: Scope Definition Draft **Use when:** A sales call is done and you need to turn rough notes into a clear project scope. ```text Turn the information below into a sharp draft project scope for a client proposal. Context: - Client: - Service: - Desired business outcome: - What the client asked for: - What we believe they actually need: - Constraints: - Timeline expectation: Notes: [paste call notes] Instructions: - Define the problem and desired outcome first. - Translate vague requests into concrete scope. - Separate in-scope work from assumptions. - Flag anything that is still unclear. - Keep the language client-friendly and specific. Output: 1. Scope summary paragraph 2. In-scope items 3. Open questions or assumptions ``` **Example input** ```text Client: Meridian Legal Service: website messaging and copy Desired business outcome: better lead quality from inbound traffic What the client asked for: "rewrite our site" What we believe they actually need: positioning clarity, homepage, services, attorney bios Constraints: founder approvals only on Fridays Timeline expectation: 5 weeks ``` ### Prompt 7: Deliverables List Builder **Use when:** You need proposal deliverables that feel concrete and easy to approve. ```text Create a deliverables section for a proposal or statement of work. Context: - Service: - Project type: - Scope summary: - Client maturity: - Internal team: - Exclusions we want to avoid confusion on: Instructions: - Break deliverables into clear items with a short description each. - Focus on outputs the client can understand and value. - Keep the list concrete, not fluffy. - Add optional dependencies if a deliverable relies on client input. Output: 1. Final deliverables list 2. Optional out-of-scope list 3. One-line summary of project value ``` **Example input** ```text Service: brand messaging engagement Project type: strategic messaging sprint Scope summary: clarify ICP, core value prop, homepage messaging, sales narrative Client maturity: seed-stage SaaS Internal team: strategist, copywriter Exclusions we want to avoid confusion on: design, CRM implementation, paid ads ``` ### Prompt 8: Pricing Justification Narrative **Use when:** You want to explain price in terms of value and effort instead of apologizing for it. ```text Write a concise pricing justification section for a proposal. Context: - Service: - Price: - Why this project matters: - Main value drivers: - Expertise involved: - Risk reduction or speed benefit: - Pricing concerns we expect: Instructions: - Justify price through outcomes, complexity, and decision support. - Do not sound defensive. - Avoid hourly-language unless specifically requested. - Make the value believable and grounded. Output: 1. Final pricing justification paragraph 2. A shorter version for email 3. Three talking points for a sales call ``` **Example input** ```text Service: fractional marketing operations support Price: $6,500 per month Why this project matters: campaigns are shipping late and reporting is inconsistent Main value drivers: faster launches, clearer dashboards, fewer founder bottlenecks Expertise involved: ops strategy, PM discipline, analytics cleanup Risk reduction or speed benefit: fewer missed deadlines and cleaner execution Pricing concerns we expect: client compares us with a freelancer hourly rate ``` ### Prompt 9: Timeline and Milestones Draft **Use when:** You need a believable timeline that protects delivery quality. ```text Create a project timeline and milestone section for a proposal or SOW. Context: - Project: - Total duration: - Start date target: - Major phases: - Client dependencies: - Known review bottlenecks: Instructions: - Break the work into phases with clear milestones. - Note where client review or approvals are required. - Keep the sequence realistic for a small team. - Flag anything that could shift the timeline. Output: 1. Timeline by phase 2. Milestones table 3. Timeline caveat note ``` **Example input** ```text Project: sales enablement content buildout Total duration: 6 weeks Start date target: May 20 Major phases: discovery, messaging, draft creation, revisions, handoff Client dependencies: interviews, legal review, sales feedback Known review bottlenecks: CEO approval can take 5 business days ``` ### Prompt 10: Revision Policy Clause **Use when:** You need revision language that feels fair and professional. ```text Draft a revision policy clause for a proposal or SOW. Context: - Deliverable type: - Standard revision rounds: - What counts as a revision: - What counts as new scope: - Approval process: - Tone: Instructions: - Make the boundary between revisions and new scope explicit. - Keep the tone calm and client-friendly. - Prevent endless feedback loops. - Avoid legal overkill unless needed. Output: 1. Final revision policy clause 2. Simpler plain-English version for email 3. One sentence defining new scope ``` **Example input** ```text Deliverable type: website copy and messaging docs Standard revision rounds: 2 What counts as a revision: changes within agreed messaging direction What counts as new scope: new pages, new audience segment, major strategic reset Approval process: consolidated client feedback in one shared doc Tone: polished ``` --- ## 3) Client Reporting Prompts ### Prompt 11: Weekly Status Update **Use when:** You need a weekly client update that shows momentum without writing a novel. ```text Write a weekly client status update. Context: - Client: - Engagement: - Reporting period: - Goal of the engagement: Notes: - Wins: - Work completed: - Blockers: - Risks: - Decisions needed: - Next week priorities: Instructions: - Keep it concise and skimmable. - Lead with progress and outcomes. - Be direct about blockers or dependencies. - End with next steps and asks. Output: 1. Final status update email 2. Bullet summary version 3. Suggested subject line ``` **Example input** ```text Client: Studio Beacon Engagement: SEO content retainer Reporting period: April 22 to April 28 Goal of the engagement: grow qualified organic demo traffic Wins: published 2 comparison pages Work completed: keyword refresh, content briefs, GA4 check Blockers: slow SME review Risks: case study page still missing Decisions needed: approve May content topics Next week priorities: draft 3 pages, finish internal links ``` ### Prompt 12: Monthly Report Summary **Use when:** You need a monthly report narrative that sounds strategic, not automated. ```text Create a monthly client report summary for an agency engagement. Context: - Client: - Service: - Month: - KPIs tracked: - Strategic goal: Performance notes: [paste metrics and commentary] Instructions: - Summarize performance in plain language. - Explain what changed and why it matters. - Distinguish results, insights, and recommendations. - Do not hide weak performance; explain it clearly. Output: 1. Executive summary 2. KPI commentary by category 3. Top 3 recommendations for next month ``` **Example input** ```text Client: Peak Dental Group Service: paid search management Month: April 2026 KPIs tracked: spend, CPL, booked consults, conversion rate Strategic goal: increase consult volume without raising CPL above target Performance notes: spend flat, consults up 18%, brand terms efficient, landing page B underperformed ``` ### Prompt 13: Results Summary for a Single Deliverable **Use when:** You need to explain the outcome of a campaign, sprint, launch, or deliverable. ```text Write a results summary for a completed client deliverable. Context: - Client: - Deliverable: - Objective: - What changed: - Evidence or metrics: - Remaining limitations: Instructions: - Tie the work back to the original goal. - Separate measurable results from qualitative wins. - Avoid overstating impact. - End with what this means for the next decision. Output: 1. Final results summary 2. Short version for email 3. Three proof points pulled from the data ``` **Example input** ```text Client: Lumen Advisory Deliverable: homepage rewrite Objective: improve consultation request conversion What changed: clearer ICP, stronger CTA hierarchy, simplified service language Evidence or metrics: time on page up 24%, form conversion up from 1.8% to 2.6% Remaining limitations: traffic volume still modest ``` ### Prompt 14: Next Steps Email **Use when:** You want a clean client note that turns a report into action. ```text Draft a next steps email after a report, review call, or milestone update. Context: - Client: - Current status: - Key takeaway: - Recommended next actions: - Approvals or decisions needed: - Timing: Instructions: - Keep the message action-oriented. - Make the recommendations feel prioritized, not overwhelming. - Clarify who needs to do what next. - End with one direct ask. Output: 1. Final email 2. Short version under 120 words 3. Action checklist only ``` **Example input** ```text Client: Harbor Growth Current status: Q2 reporting review completed Key takeaway: lead quality improved, but sales follow-up lag is hurting conversion Recommended next actions: tighten lead routing, revise nurture sequence, retrain SDR handoff Approvals or decisions needed: approve CRM workflow updates Timing: next 7 business days ``` ### Prompt 15: Client Leadership Executive Brief **Use when:** The audience is a founder or executive who only wants the signal, not the full report. ```text Create a concise executive brief for a client stakeholder. Context: - Client: - Stakeholder role: - Reporting period: - Core business goal: - Main metrics: - Biggest win: - Biggest concern: - Recommended decision: Instructions: - Keep it under 200 words. - Focus on outcomes and decisions, not process detail. - Use confident, plain-English language. - Surface the one thing leadership should pay attention to. Output: 1. Executive brief 2. Subject line 3. One-sentence verbal summary ``` **Example input** ```text Client: Atlas Recruiting Stakeholder role: CEO Reporting period: April Core business goal: increase qualified applications for two priority roles Main metrics: applicants, qualified interviews, CPL Biggest win: recruiter landing page doubled qualified applicants Biggest concern: Meta creative fatigue Recommended decision: approve two new creative angles and increased budget on the best ad set ``` --- ## 4) Invoice & Payment Prompts ### Prompt 16: Invoice Reminder Email **Use when:** An invoice is due soon or just due, and you want a clean reminder. ```text Write a polite invoice reminder email. Context: - Client: - Invoice number: - Amount: - Due date: - Work covered: - Payment method: - Tone: Instructions: - Keep it short and professional. - Mention the invoice and due date clearly. - Assume good intent. - Include an easy payment prompt. Output: 1. Final reminder email 2. Shorter version 3. Subject line options ``` **Example input** ```text Client: Studio Finch Invoice number: INV-2048 Amount: $2,500 Due date: May 5 Work covered: April content retainer Payment method: ACH via Stripe Tone: warm ``` ### Prompt 17: Overdue Follow-Up **Use when:** Payment is late and you need firmer language without escalating too fast. ```text Write an overdue payment follow-up email for a client. Context: - Client: - Invoice number: - Amount: - Original due date: - Days overdue: - Relationship context: - Next action if unpaid: - Tone: Instructions: - Be clear that payment is overdue. - Keep the tone respectful and firm. - Ask whether there is any issue with the invoice. - State the next step or requested payment date. - Avoid sounding passive-aggressive. Output: 1. Final email 2. Firmer version 3. One-line internal note on the account status ``` **Example input** ```text Client: Growth Harbor Invoice number: INV-2057 Amount: $4,000 Original due date: April 20 Days overdue: 11 Relationship context: second late payment this quarter Next action if unpaid: pause new work after May 3 Tone: firm ``` ### Prompt 18: Payment Received Thank-You **Use when:** You want to acknowledge payment and reinforce professionalism. ```text Write a payment received thank-you email. Context: - Client: - Invoice number: - Amount: - Work stage: - Next upcoming milestone: - Tone: Instructions: - Confirm receipt clearly. - Thank them without overdoing it. - Reconfirm the next project step. - Keep the note concise and polished. Output: 1. Final email 2. Short version for a billing contact ``` **Example input** ```text Client: Fieldnote Creative Invoice number: INV-2061 Amount: $3,200 Work stage: phase 2 kickoff Next upcoming milestone: strategy workshop on May 14 Tone: polished ``` --- ## 5) Scope Creep Management Prompts ### Prompt 19: Polite Pushback Message **Use when:** A client asks for something outside scope and you want to protect the relationship while holding the line. ```text Write a polite pushback message for an out-of-scope client request. Context: - Client: - Original scope: - New request: - Why it is outside scope: - Relationship sensitivity: - Tone: Instructions: - Acknowledge the request positively. - Explain clearly why it falls outside the current scope. - Avoid sounding defensive or rigid. - Offer a path forward if appropriate. Output: 1. Final message 2. Softer version 3. One-sentence explanation of why it is out of scope ``` **Example input** ```text Client: Northlane Studio Original scope: 4 landing pages and messaging guide New request: add email nurture sequence copy Why it is outside scope: not included in approved deliverables or timeline Relationship sensitivity: good client, wants help quickly Tone: diplomatic ``` ### Prompt 20: Change Order Request **Use when:** The new request is valid work and should become paid scope. ```text Create a change order request message for a client. Context: - Client: - Current engagement: - Requested addition: - Impact on timeline: - Impact on fee: - Recommended next step: - Tone: Instructions: - Confirm you can support the request. - Explain the scope, fee, and timeline impact clearly. - Make approval easy. - Keep the tone commercial and collaborative. Output: 1. Final client email 2. Short version for Slack 3. Bullet summary of scope, timeline, and cost change ``` **Example input** ```text Client: Elevate Tax Current engagement: website messaging sprint Requested addition: 5-email nurture sequence Impact on timeline: adds 1 week Impact on fee: additional $1,800 Recommended next step: approve change order by Thursday to keep momentum Tone: direct ``` ### Prompt 21: Project Pause Notice **Use when:** Delivery needs to pause because approvals, assets, or payment are blocked. ```text Write a professional project pause notice for a client. Context: - Client: - Engagement: - Reason for pause: - What is missing: - Since when: - Impact on delivery: - What resumes the project: - Tone: Instructions: - State the pause clearly and professionally. - Reference the dependency causing the pause. - Explain the impact on timing. - Tell the client exactly what is needed to resume. - Keep the message calm and non-accusatory. Output: 1. Final pause notice 2. Shorter version 3. Internal account summary ``` **Example input** ```text Client: Beacon Medical Engagement: ad creative production Reason for pause: overdue approvals and unpaid invoice What is missing: ad approvals and April retainer payment Since when: 9 days Impact on delivery: campaign launch must move to the following week What resumes the project: payment receipt and final creative approval Tone: firm but professional ``` --- ## 6) Client Offboarding Templates ### Prompt 22: Project Wrap-Up Email **Use when:** The engagement is ending and you want a strong final handoff. ```text Write a project wrap-up email for the end of a client engagement. Context: - Client: - Work completed: - Main outcomes: - Assets being handed off: - Open items remaining: - Tone: Instructions: - End on a strong, appreciative note. - Summarize what was completed and what the client now has. - Mention any outstanding items or recommendations. - Keep it clear enough that it can be archived later. Output: 1. Final wrap-up email 2. Handoff checklist 3. Suggested subject line ``` **Example input** ```text Client: Storywell Labs Work completed: messaging strategy, homepage copy, founder bio, sales deck narrative Main outcomes: clearer positioning and tighter conversion path Assets being handed off: messaging doc, final copy file, Loom walkthrough Open items remaining: internal design implementation Tone: warm ``` ### Prompt 23: Testimonial Request **Use when:** You want to ask for a testimonial while results are still fresh. ```text Write a testimonial request email for a recently completed client project. Context: - Client: - Work delivered: - Result or win: - Relationship quality: - Where the testimonial may be used: - Tone: Instructions: - Make the ask easy and specific. - Remind them of the result without sounding self-congratulatory. - Offer a simple prompt they can reply to. - Keep it short. Output: 1. Final email 2. Three optional testimonial prompts 3. Short version for a direct message ``` **Example input** ```text Client: North Ridge HR Work delivered: recruitment funnel audit and landing page rewrite Result or win: qualified applications increased in the first three weeks Relationship quality: strong Where the testimonial may be used: website and proposal deck Tone: warm ``` ### Prompt 24: Referral Ask **Use when:** The client had a good experience and you want to ask for introductions professionally. ```text Write a referral request message for a happy client. Context: - Client: - Service delivered: - Result achieved: - Ideal referral profile: - Best timing: - Tone: Instructions: - Keep the request low-pressure. - Clarify who you are best positioned to help. - Make it easy for them to think of someone specific. - Avoid sounding needy. Output: 1. Final email 2. Short version 3. One-sentence ideal referral description ``` **Example input** ```text Client: Clearframe Studio Service delivered: monthly email and launch support Result achieved: smoother launch and stronger list engagement Ideal referral profile: founder-led B2B brand with no in-house lifecycle marketer Best timing: one week after project completion Tone: polished ``` ### Prompt 25: Case Study Consent Request **Use when:** You want permission to feature the project publicly. ```text Write a case study consent request for a completed client engagement. Context: - Client: - Project: - Notable outcomes: - What details we want to share: - Whether approval is needed before publishing: - Tone: Instructions: - Be respectful of confidentiality. - Tell them what you want permission to use. - Offer review rights before publishing if appropriate. - Keep the request clear and professional. Output: 1. Final email 2. Simpler version 3. Bullet list of approvals requested ``` **Example input** ```text Client: Summit Advisory Partners Project: sales narrative and website copy overhaul Notable outcomes: clearer positioning and stronger lead quality What details we want to share: project scope, before/after messaging examples, high-level outcomes Whether approval is needed before publishing: yes Tone: polished ``` --- ## Final Notes This pack is meant to reduce blank-page time, improve client confidence, and protect delivery quality. The prompts work best when you feed them real context and then apply human judgment before sending anything client-facing. If you reuse this pack across multiple clients, duplicate the prompts into your own templates library and tailor the wording to your agency voice, service model, and boundaries.