I spent three hours rewriting a Statement of Work last March because a client disputed a single line about revision rounds. Three hours. For one sentence I thought was obvious. That was the last time I let vague contract language cost me a billable afternoon — and it pushed me to build a proper prompt library in Claude specifically for SOWs and client agreements.
If you write contracts, service agreements, or Statements of Work for clients — whether you’re a consultant, freelancer, or solo operator like me — you already know the problem. These documents need to be precise without being cold, protective without being aggressive, and clear enough that a client reads them on a Tuesday morning and immediately understands what they’re getting and what they’re not. That’s a hard balance to strike from scratch every time.
Claude handles this kind of structured, nuanced writing better than most AI tools I’ve tested. It holds context across long documents, it asks useful clarifying questions when you set it up right, and it doesn’t produce the kind of generic legalese that makes clients skim past the parts that actually matter. These 25 prompts are what I actually use — copy-paste ready, tested in real client work, and organized by the stage of the contract process where they’re most useful.
Why Claude Works Better Than ChatGPT for SOW and Contract Writing
Before the prompt library, a quick word on why Claude specifically. I’ve tested both extensively for document work. Claude’s longer context window and stronger instruction-following make it noticeably better for contracts — it doesn’t drift from your specified scope, it maintains consistent terminology throughout a long document, and it handles conditional clauses (“if X, then Y, unless Z”) with more precision than I’ve seen from other models.
It also tends to flag ambiguity rather than paper over it with confident-sounding filler. For legal-adjacent writing, that’s a feature, not a limitation.
One real limitation I’ll name now and return to later: Claude will not give you legal advice, and it is correct not to. These prompts produce strong drafts — not reviewed, attorney-approved contracts. For high-value or legally complex work, you still need a lawyer’s eyes on the final document. I use these prompts to get to 85% of the way there quickly, then a local solicitor in Funchal reviews anything above €10,000 in contract value.
Section 1: Prompts for Drafting a Statement of Work From Scratch
These are the prompts I reach for when starting a new engagement from a blank page. They’re designed to pull structured output from minimal input — you describe the project, Claude builds the framework.
Prompt 1 — Full SOW Draft From Project Brief
When to use it: You’ve had a discovery call, you have notes, and you need to turn them into a proper SOW document. Feed Claude your rough notes as context after the prompt.
You are a professional business consultant helping me draft a Statement of Work (SOW) for a client engagement. Based on the project notes I'll provide below, create a complete SOW that includes: (1) Project Overview, (2) Scope of Work with clearly numbered deliverables, (3) Out of Scope section listing 3-5 explicit exclusions, (4) Timeline with milestones, (5) Client Responsibilities, (6) Payment Schedule, (7) Revision Policy, and (8) Acceptance Criteria. Use plain, professional language — avoid legal jargon where a simpler word works equally well. Flag any section where my notes are too vague to draft accurately by writing [NEEDS INPUT] in brackets.
Project notes: [paste your notes here]Prompt 2 — SOW for a Retainer Engagement
When to use it: Monthly retainer clients need different SOW language than project-based work. This prompt structures the ongoing nature of the engagement correctly.
Draft a Statement of Work for a monthly retainer consulting arrangement. The client is [CLIENT TYPE], the service is [SERVICE DESCRIPTION], and the monthly fee is [AMOUNT]. The SOW should clearly define: what's included in each monthly cycle, how unused hours or tasks are handled (do not roll over unless specified), the process for requesting work outside the retainer scope, a 30-day written termination clause for either party, and a quarterly review checkpoint. Keep the tone professional but readable — this is meant to be signed by a business owner, not parsed by a lawyer.Prompt 3 — Scope Section Only (When You Already Have a Template)
When to use it: You have a master SOW template but need to write a fresh, specific scope section for each new client. Use this to generate just that section.
Write only the Scope of Work section for a client agreement. The project involves [DESCRIBE PROJECT IN 2-3 SENTENCES]. Format this as a numbered list of concrete deliverables. Each item should describe what will be delivered, in what format, and by what milestone. After the deliverables list, add a separate "Not Included in This Scope" subsection with 4-5 specific exclusions that a client in this type of project commonly assumes are included but typically are not. Be specific — avoid phrases like "any additional work" as exclusions.Prompt 4 — SOW for a One-Day Consulting Engagement
When to use it: Short engagements still need documentation. This produces a concise, one-page-style SOW appropriate for workshops, audits, or strategy days.
Write a concise Statement of Work for a single-day consulting engagement. Keep the total document under 500 words. Include: a two-sentence project overview, a bulleted list of what will be covered during the day, what the client will walk away with (tangible outputs), what the client needs to prepare in advance, the fee and payment terms, and a cancellation policy. Avoid headers that make this feel like a corporate contract — this is for a small business client. Maintain a professional but direct tone.Section 2: Prompts for Contract Clauses and Protective Language
This is where Claude earns its place in my workflow. Generating individual clauses — payment terms, IP ownership, revision limits — and slotting them into existing documents saves significant time. These prompts target the clauses solopreneurs consistently get wrong or skip entirely.
Prompt 5 — Revision Limit Clause
When to use it: After any project involving creative or consulting deliverables. Revision creep is the quiet killer of solopreneur profitability.
Write a revision policy clause for a service agreement. The policy should state: the client receives [NUMBER] rounds of revisions included in the project fee; a "revision round" is defined as a single consolidated set of feedback submitted in one communication (not multiple emails); additional revision rounds are billed at [HOURLY RATE] per hour; revisions requested after final approval has been given in writing are treated as new scope. Write this in plain English, not legal Latin. It should be firm but not aggressive — I want clients to feel protected, not threatened.Prompt 6 — Late Payment Clause with Escalation
When to use it: Every contract. Always. This one has saved me real money.
Draft a late payment clause for a freelance or consulting service agreement. Include: net payment terms of [NUMBER] days from invoice date; a late fee of [PERCENTAGE]% per month on overdue balances; the right to pause all work on outstanding projects until payment is received; and a statement that the client is responsible for any reasonable collection costs if the account goes to collections. Write this as a single paragraph that can be inserted into an existing contract. Tone should be matter-of-fact, not threatening.Prompt 7 — Intellectual Property Ownership Clause
When to use it: Any project where you’re creating original content, designs, code, reports, or documentation for a client.
Write an intellectual property clause for a consulting or creative services agreement. The clause should state that: all work product created during the engagement remains the property of [YOUR BUSINESS NAME] until full payment is received; upon receipt of full payment, ownership transfers to the client; the consultant retains the right to reference the project in portfolio and case study materials unless the client requests confidentiality in writing; any pre-existing tools, templates, or frameworks used by the consultant remain the consultant's property. Keep this under 150 words and in plain language.Prompt 8 — Limitation of Liability Clause
When to use it: Especially for consulting or advisory work where your recommendations could theoretically affect client outcomes.
Write a limitation of liability clause for a consulting services agreement. It should cap the consultant's total liability at the total fees paid by the client for the specific project in question. It should exclude liability for indirect, incidental, or consequential damages. It should acknowledge that the consultant provides advice and recommendations, and that the client retains full decision-making authority. Write in plain English, keep it under 120 words, and avoid unnecessarily scary legal phrasing that would make a small business client hesitant to sign.Prompt 9 — Project Pause and Restart Clause
When to use it: For longer projects where client delays are common. This clause protects your schedule when clients go quiet for weeks.
Write a project pause clause for a consulting or service agreement. If the client fails to provide required feedback, approvals, or materials within [NUMBER] business days of a request, the project timeline will be extended by the same number of days the delay occurred. If the project is paused for more than [NUMBER] days due to client inaction, the consultant reserves the right to reschedule the project to the next available slot in their schedule, which may extend the original completion date. A restart fee of [AMOUNT or PERCENTAGE] may apply. Write this as a clear, fair, professional paragraph.My Real-World Experience Using Claude for SOWs in Madeira
In January 2026, I had four property consulting engagements close within the same two-week window — two international buyers looking at villas in the west of the island, one investor from Germany wanting a portfolio review, and a developer who needed a market analysis report scoped and priced. Normally, writing four separate SOWs would have eaten a full day. I have a master template, but every engagement is different enough that I always end up rewriting 60% of it anyway.
I ran all four through Claude using versions of the prompts in Section 1, feeding my call notes as context. The first draft for the German investor’s portfolio review came back in under four minutes — structured scope, a clear exclusions list (no legal or tax advice, no bank liaison, no on-site property inspections outside the agreed portfolio), payment in two tranches, and a revision clause. I spent maybe 25 minutes editing that draft: swapping in specific numbers, adjusting the milestone dates, and softening one sentence that read more like a warning than a professional note.
Total time across all four SOWs: 2 hours and 10 minutes, including my review time. My previous average for four SOWs was around 5 to 6 hours — not because writing them is hard, but because starting from a blank section is mentally expensive. You second-guess yourself on scope boundaries, you rewrite the exclusions list three times, you wonder if the revision clause sounds too defensive.
Claude removes most of that friction. It gives me something concrete to react to, which is always faster than generating from nothing.
The limitation I ran into: for the developer engagement, which involved a more complex fee structure with a success component tied to eventual sale prices, Claude produced a clause that was technically correct but would have created ambiguity if the sale timeline shifted. It didn’t know enough about Portuguese commercial property norms to flag that the milestone definition I’d given it was too loosely tied to an event neither of us could fully control. I caught it in review — but only because I knew to look for it. That’s the honest trade-off: Claude drafts faster than I can, but it doesn’t have domain knowledge about your specific market or local legal context. You still need to read the output with your professional brain engaged.
I now use Claude for every SOW first draft and probably two-thirds of my contract clause additions. I’d estimate it’s saving me 3 to 4 hours per month on document work alone — time that goes into actual client work or, occasionally, a coffee in Funchal.
Section 3: Prompts for Contract Review and Gap Analysis
Sometimes the problem isn’t writing a contract — it’s reviewing one someone else wrote, or checking your own draft for holes. These prompts turn Claude into a useful second set of eyes.
Prompt 10 — Find Missing Clauses in an Existing SOW
When to use it: Before sending any contract out. Run your draft through this to catch what you forgot.
Review the following Statement of Work and identify any important clauses or provisions that are missing or underspecified for a [TYPE OF SERVICE] engagement. Specifically check for: revision policy, client responsibilities, payment terms and late payment consequences, project pause conditions, IP ownership, confidentiality obligations, cancellation or termination rights for both parties, and dispute resolution process. For each missing or weak area, explain in one sentence why it matters and suggest brief replacement language. Do not rewrite the entire document — list gaps only.
[PASTE YOUR SOW HERE]Prompt 11 — Simplify Overly Legal Contract Language
When to use it: When a client sends you their standard agreement and you want to understand what it actually says, or when you’ve drafted something that reads like a law school exam.
Rewrite the following contract section in plain English. Keep all the legal meaning intact — do not remove protections or change the substance — but replace any Latin phrases, nominalisations, or unnecessarily complex sentence structures with clear, direct language. The goal is that a non-lawyer small business owner can read this once and understand exactly what they're agreeing to. Where a legal term has no plain-English equivalent, keep the term but add a brief parenthetical explanation.
[PASTE CONTRACT SECTION HERE]Prompt 12 — Identify Clauses That Favor the Other Party Too Heavily
When to use it: When reviewing a contract sent by a client or a larger company that wants you to sign their standard terms.
I am a freelance consultant reviewing a contract sent to me by a client before signing. Review the following agreement and flag any clauses that: place unlimited liability on me, allow the client to cancel without penalty, include broad IP assignment beyond the specific project deliverables, restrict me from working with competitors without compensation, or require me to indemnify the client in ways that seem disproportionate. For each flagged clause, explain the risk in plain terms and suggest one negotiation point I could raise. Do not give legal advice — frame these as commercial considerations.
[PASTE CONTRACT HERE]Prompt 13 — Scope Creep Detection in an Existing SOW
When to use it: Midproject, when a client starts asking for things that feel outside scope. Run their requests against the original SOW.
I have an active project with a client. Below I'll paste the original Scope of Work and then a description of what the client is now requesting. Analyze whether the new request falls within the original scope, partially overlaps, or is clearly outside scope. If it's outside scope, suggest one sentence I could use in a professional reply to acknowledge the request and explain that it would require a separate agreement or change order. Keep the suggested language warm but clear — I want to maintain the relationship while protecting my time.
Original SOW: [PASTE]
Client's new request: [PASTE]Section 4: Prompts for Change Orders and Project Amendments
Scope changes happen on almost every project over a certain length. Having a fast way to document them protects both parties and keeps the relationship professional when money conversations get uncomfortable.
Prompt 14 — Change Order Document
When to use it: Any time work expands beyond the original SOW. Document it immediately, before you do the extra work.
Write a Change Order document to amend an existing Statement of Work. This change order should: reference the original SOW by name and date, describe the additional work being added in specific, deliverable terms, state the additional fee for this work, update the project timeline if applicable, and include a signature line for both parties. Keep the document to one page. Tone should be businesslike and collaborative — frame this as a mutual agreement, not a unilateral charge.
Original SOW title and date: [FILL IN]
Additional work requested: [DESCRIBE]
Additional fee: [AMOUNT]
Timeline impact: [FILL IN]Prompt 15 — Project Cancellation and Kill Fee Letter
When to use it: When a client cancels a project midstream and you need to document the kill fee clearly and professionally.
Write a professional project cancellation letter and summary document. The client has cancelled the project described in [SOW NAME]. Work completed to date represents approximately [PERCENTAGE]% of the total project scope. Per the cancellation terms in the original agreement, a kill fee of [AMOUNT OR PERCENTAGE] applies. The letter should: acknowledge the cancellation without assigning blame, summarize work completed and deliverables provided so far, state the kill fee amount and payment due date, and confirm that all work product completed to date will be transferred to the client upon receipt of the kill fee. Tone should be calm, professional, and final.Prompt 16 — Project Extension Amendment
When to use it: When timelines shift — whether due to client delays or your own schedule — and you want both parties to acknowledge the new dates in writing.
Write a brief project timeline amendment to attach to an existing SOW. The original completion date was [DATE]. The new completion date is [DATE]. The reason for the extension is [BRIEF REASON — e.g., client feedback delays, scope addition, consultant availability]. This amendment should note that all other terms of the original SOW remain unchanged. Include a place for both parties to sign and date. Keep this to a single short paragraph plus signature block.Section 5: Prompts for Client-Facing Summaries and Email Covering Notes
A well-drafted SOW still needs a good covering email — one that sets the right tone when you send it for review. These prompts handle the human layer around the document itself.
Prompt 17 — SOW Covering Email (First Send)
When to use it: Every time you send a new SOW to a client for the first time. This email sets up the document before they open it.
Write a short covering email to send with a Statement of Work attached. The email should: open with a sentence that references our recent conversation (leave a [CONVERSATION REFERENCE] placeholder), confirm what's attached and what you'd like the client to do (review and sign, or suggest changes), highlight 2-3 of the most important sections they should read carefully (scope, revision policy, payment terms), and close with a specific response deadline of [DATE]. Keep the email under 150 words. Tone should be warm, professional, and confident — not apologetic about the document's terms.Prompt 18 — Non-Technical Summary of the SOW for a Non-Business Client
When to use it: When your client is an individual, not a company — someone who may not be used to reading formal service agreements.
Write a plain-language summary of the attached Statement of Work that I can send alongside the formal document. This summary is for an individual client who isn't used to reading service agreements. In 4-5 short bullet points, explain: what I will do for them, what they'll receive, when, what it costs and when payment is due, and what happens if they want to make changes. Start each bullet with a bolded label. Keep this completely jargon-free. End with one sentence encouraging them to ask any questions before signing.
SOW summary input: [PASTE KEY DETAILS FROM YOUR SOW]Prompt 19 — Follow-Up Email When a Client Hasn’t Signed
When to use it: When a SOW has been sitting in a client’s inbox for more than a week with no action.
Write a polite but direct follow-up email for a client who received my Statement of Work [NUMBER] days ago and hasn't signed or responded. The email should: remind them the SOW is waiting without sounding passive-aggressive, note that I've reserved [START DATE] for this project and need confirmation by [DEADLINE] to hold that slot, offer to jump on a quick call if they have any questions, and clearly state that the start date may need to shift if I don't receive a signed agreement by the deadline. Keep it under 100 words. Do not grovel or over-apologize.Prompt 20 — Scope Clarification Email (Professional Pushback)
When to use it: When a client asks for something outside scope and you need to push back without damaging the relationship.
Write a professional email responding to a client who has requested [DESCRIBE THE ADDITIONAL REQUEST], which falls outside the scope of our current agreement. The email should: acknowledge their request positively, clarify that this work isn't included in the current SOW by referencing the scope section, offer two options — adding it as a change order at [RATE OR FEE] or deferring it to a future engagement — and invite them to confirm which they prefer. Tone should be collaborative and helpful, not defensive. Under 150 words.Section 6: Advanced Prompts for Complex Engagements
These prompts handle edge cases and more sophisticated document structures. I use these less frequently — maybe once or twice a quarter — but when I need them, nothing else comes close.
Prompt 21 — Multi-Phase Project SOW
Draft a Statement of Work for a multi-phase consulting project. The project has [NUMBER] phases. For each phase, include: phase name and objective, specific deliverables, duration, payment due at start or completion of that phase, and a go/no-go decision point where the client can choose to proceed to the next phase or stop. Include a clause that states: completion of each phase requires written client approval before the next phase begins, and that fees for a completed phase are non-refundable regardless of whether the client proceeds.
Phase details: [DESCRIBE EACH PHASE]Prompt 22 — Confidentiality and NDA Clause for a Consulting Agreement
Write a mutual confidentiality clause suitable for inclusion in a consulting services agreement (not a standalone NDA). It should: define confidential information broadly but exclude information that is already publicly available, require both parties to protect the other's confidential information with reasonable care, state that confidentiality obligations survive the end of the engagement for [NUMBER] years, and permit disclosure if required by law with reasonable prior notice to the other party. Keep this under 200 words and in plain English. Label this section "Confidentiality" not "Non-Disclosure Agreement."Prompt 23 — Performance-Based Fee Structure Clause
Draft a fee clause for a consulting agreement that includes both a fixed base fee and a performance-based component. The base fee is [AMOUNT], payable [SCHEDULE]. The performance fee is [PERCENTAGE OR AMOUNT] triggered when [DEFINE THE SPECIFIC MEASURABLE OUTCOME — e.g., sale price exceeds a threshold, a KPI is achieved]. Include: how the outcome will be measured and verified, within how many days after the triggering event payment is due, and what happens if the triggering event occurs after the engagement formally ends. Flag any part of this structure that could create measurement disputes and suggest how to address it.Prompt 24 — SOW for a Subcontractor You’re Hiring
Write a Statement of Work to give to a subcontractor I'm bringing in to help with part of a client project. This SOW should: clearly describe only the portion of work this subcontractor will handle, state that they are an independent contractor (
Robson Penassi
Real estate consultant in Madeira, Portugal. Solopreneur since 2012. Testing AI tools since 2023 to automate his one-person business. Writes about what actually works — and what does not.
More articles by Robson →