Claude Prompts for Freelancers

You are a client-experience expert for freelancers. Write a kickoff email that sets a project up to run smoothly. <context>Client: [name]. Project: [project]. Start date: [date]. Deliverables: [list]. What I need from them: [assets/access/answers]. How we'll communicate: [tool + cadence].</context> <task>Write a warm, organized kickoff email that confirms scope, sets expectations, and requests what I need to start.</task> <constraints>Enthusiastic but structured. Confirm the deliverables and timeline. List exactly what you need from them with a due date. Set the communication cadence and response-time expectations both ways. Under 250 words. Reassure them the project is in good hands, and make the single most important 'need from you' item unmissable with a hard deadline attached.</constraints> <format>Subject line + body. Include a short 'What I need from you' checklist with a deadline, and a 'What to expect next' timeline.</format>

You are a freelancer who keeps clients calm with proactive updates. Write a concise weekly status update. <context>Project: [project]. Done this week: [items]. In progress: [items]. Blocked / need from client: [items]. On track for deadline: [yes/no + note].</context> <task>Write a scannable weekly update email that shows momentum and surfaces any blockers early.</task> <constraints>Short and skimmable. Lead with progress. Flag blockers with a specific ask and deadline. Confirm or adjust the timeline honestly. No filler. Under 180 words. If the timeline has slipped, say so plainly with the new date and the reason, never bury bad news, and reduce the overall status to a single word like On track, At risk, or Delayed.</constraints> <format>Subject line with the week/date. Body in three labeled sections: Completed, In Progress, Needs Your Input (with owner + due date). One-line overall status at the top.</format>

You are a freelancer known for polished project handoffs. Write a delivery email that presents the finished work and makes next steps obvious. <context>Client: [name]. Deliverable: [what I'm sending]. Where it lives: [link/attachment]. How to use it: [instructions]. Revision policy: [rounds left]. What I'd love next: [testimonial / referral / retainer].</context> <task>Write a delivery email that hands over the work, explains how to use it, states the revision window, and plants a next-step seed.</task> <constraints>Proud but not boastful. Make usage instructions idiot-proof. State the revision deadline clearly. Include a soft, low-pressure ask for a testimonial or referral. Under 220 words.</constraints> <format>Subject line + body: a warm intro, the deliverable link, a short 'How to use this' list, revision-window note, and a light next-step ask.</format>

You are a freelancer skilled at protecting boundaries without damaging relationships. Draft a diplomatic pushback message. <context>Client: [name]. Their request: [unreasonable ask, e.g. rush deadline, free extra, scope jump]. Why I can't/won't as-is: [reason]. What I CAN offer instead: [alternative].</context> <task>Write a message that declines the request as-is while offering a workable alternative, keeping the relationship warm.</task> <constraints>Never a flat no. Acknowledge their need first, explain the constraint briefly and without over-justifying, then pivot to the alternative (e.g. rush fee, later date, paid add-on). Calm and confident. Under 180 words. Keep the explanation to one sentence so it reads as a boundary rather than a plea, and make the alternative concrete enough that they can say yes to it immediately.</constraints> <format>Subject line + body: empathy line, the honest constraint, the alternative offer with any cost/timeline, and a collaborative close.</format>

You are a conflict-resolution specialist for client relationships. Draft a calm reply to an upset or unhappy client. <context>Client: [name]. What they're upset about: [complaint]. What actually happened (my side): [facts]. What I'm willing to do: [resolution]. What I won't do: [boundary].</context> <task>Write a de-escalating email that acknowledges their frustration, corrects the record without blame, and proposes a concrete resolution.</task> <constraints>Lead with empathy, not defense. State facts calmly and neutrally. Offer one clear resolution path. Hold your boundary respectfully. No sarcasm, no over-apologizing that admits fault you don't owe. Under 220 words. Assume the client wants a solution rather than a fight, and close on a forward-looking, collaborative note instead of relitigating who was right.</constraints> <format>Subject line + body: acknowledgment, brief factual clarification, the proposed resolution, a boundary line if needed, and an invitation to move forward together.</format>

You are a portfolio copywriter for freelancers. Turn a project into a results-driven case study. <context>Client/industry: [context]. Their problem: [problem]. What I did: [approach]. Results (numbers if any): [outcomes]. Client quote (optional): [quote].</context> <task>Write a compelling case study that a future prospect reads and thinks 'I need this person'.</task> <constraints>Story-driven, not a task list. Quantify results wherever possible. Keep the client the hero and me the guide. Under 500 words. End with a takeaway a similar prospect self-identifies with. Open with a result-led angle, keep paragraphs short and skimmable, and if hard numbers are missing use concrete qualitative outcomes like time saved or stress removed rather than vague superlatives.</constraints> <format>Sections: Headline (result-led), The Challenge, The Approach (3 steps), The Results (with metrics), Client Quote, and a short 'Facing something similar?' CTA line.</format>

You are a personal-brand copywriter. Write an 'About' page that positions me as the obvious choice for my niche. <context>My name: [name]. What I do: [service]. Who I help: [ideal client]. What makes me different: [angle]. Proof: [experience/results]. Personality: [tone I want].</context> <task>Write an About page that's client-focused, builds trust, and reflects my personality.</task> <constraints>Open with the client's problem, not my life story. Blend credibility with a human touch. Avoid generic phrases like 'passionate about'. Include one specific proof point. Under 350 words. Match the requested tone. Avoid clichés like 'passionate' and 'results-driven', show personality through one specific detail instead, and make the first two lines strong enough to hook a skimming visitor.</constraints> <format>Three short sections: a hook about who I help and why it matters, a credibility paragraph with proof, and a personality/values paragraph. End with a CTA to work together.</format>

You are a conversion copywriter for service businesses. Write a service page for one of my offerings. <context>Service: [service]. Ideal client: [who]. Their pain: [pain]. My process: [steps]. Deliverables: [list]. Price signal: [from / starting at]. Proof: [results/testimonial].</context> <task>Write a service page that turns a browser into an inquiry.</task> <constraints>Speak to the pain before the solution. Make the process feel simple (3-4 steps). Emphasize outcomes over features. Include objection-handling and social proof. One primary CTA repeated. Under 600 words. Use the reader's own language for their pain, keep each section skimmable with a clear subhead, and make the outcome rather than the deliverable the emotional centre of the page.</constraints> <format>Sections: Headline + subhead, The Problem, How I Help, My Process (numbered), What You Get, Proof/testimonial block, FAQ (3 objections), and a strong closing CTA.</format>

You are a LinkedIn brand strategist for freelancers. Rewrite my headline and About section to attract ideal clients. <context>Current headline: [current]. What I do: [service]. Who I serve: [niche]. Differentiator: [angle]. Results/proof: [proof]. Keywords clients search: [keywords].</context> <task>Write (1) three headline options and (2) a client-magnet About section optimized for search and clarity.</task> <constraints>Headlines must state who I help + the outcome, not just a job title. The About must open with a hook, weave in searchable keywords naturally, and end with a CTA. First person. Under 300 words for the About. Front-load the searchable keywords in the first two lines where LinkedIn truncates the preview, and make every headline pass the 'who + outcome' test rather than sounding like a plain job title.</constraints> <format>Part A: 3 headline options. Part B: full About section with a hook opener, a value paragraph, a proof line, and a CTA with contact steps.</format>

You are a positioning strategist. Help me craft a sharp one-line positioning statement and supporting messaging. <context>What I do: [service]. Who I'm best for: [niche]. The transformation I create: [before to after]. Competitors/alternatives: [alternatives]. Why me: [edge].</context> <task>Produce one primary positioning statement plus supporting messaging I can reuse everywhere.</task> <constraints>The statement must be specific enough that the wrong client self-selects out. Avoid buzzwords. Make the niche and outcome unmistakable. Provide variations for different contexts. Test it against the 'could a competitor say this too?' filter, if yes, sharpen it. Prefer concrete nouns over abstractions, and make the primary line short enough to say out loud in one breath at a networking event.</constraints> <format>Output: (1) one primary positioning line, (2) a 2-sentence expanded version, (3) three short taglines, (4) a 'who this is NOT for' line to reinforce focus.</format>

You are an operations designer for freelance businesses. Create a client onboarding welcome document. <context>My service: [service]. Typical first steps: [steps]. Tools clients use with me: [tools]. What I need from them upfront: [assets/access]. How we communicate: [channel + hours].</context> <task>Write a welcome document that orients a new client and reduces back-and-forth in week one.</task> <constraints>Warm and reassuring. Make it self-serve: they should know what to send, when, and how we'll work. Include response-time expectations both ways and where to reach me. Under 500 words. Anticipate the questions a nervous new client would ask in week one and answer them pre-emptively, so this single document replaces three back-and-forth emails.</constraints> <format>Sections: Welcome note, What Happens Next (timeline), What I Need From You (checklist with deadline), How We'll Work Together (tools + cadence), Response Times, Contact & Emergencies. Skimmable with headings.</format>

You are a systems consultant for solo businesses. Document one of my repeatable processes as an SOP. <context>Process: [process, e.g. 'delivering a monthly report']. Rough steps I follow: [steps]. Tools involved: [tools]. Common mistakes to avoid: [pitfalls].</context> <task>Write a clear SOP I could follow on autopilot or hand to a subcontractor.</task> <constraints>Number every step. Be explicit about tools, inputs and outputs. Flag decision points and quality checks. Note common mistakes inline. Written so someone new could execute it without asking me. Under 500 words. Assume zero prior context, spell out where files live and what 'done' looks like at each step, and keep every instruction to a single action so it's impossible to misread.</constraints> <format>Header: Process name, Purpose, When to run it. Then a numbered step list (each step = action + tool + expected result). A 'Quality checklist' at the end and a 'Common mistakes' box.</format>

You are a referral and social-proof specialist. Write a message that makes it effortless for a happy client to give a testimonial. <context>Client: [name]. Project + result: [what we achieved]. Where I'll use it: [website/LinkedIn]. How much time I want to ask of them: [minimal].</context> <task>Write a short request that gets a specific, usable testimonial by doing most of the work for them.</task> <constraints>Make it low-effort: offer 3-4 guiding questions or a draft they can edit. Keep it warm and specific to our project. Reassure them it takes 5 minutes. Under 160 words. Include permission to lightly edit.</constraints> <format>Subject line + body. Include the 3-4 guiding questions (or an optional pre-written draft in [brackets] they can approve) and where it'll appear.</format>

You are a growth advisor for service businesses. Write a message asking a satisfied client for a referral. <context>Client: [name]. Result I delivered: [result]. Type of client I want more of: [ideal referral]. Any incentive I offer: [referral bonus / none].</context> <task>Write a natural referral request that specifies exactly who I want to be introduced to, so it's easy to think of someone.</task> <constraints>Ask only after a win. Be specific about the ideal referral (role/industry/problem) so their brain can pattern-match. Make the intro effortless (offer a forwardable blurb). Mention any incentive lightly. Under 150 words. Make the specific 'who I want to meet' description the heart of the message, since a vague 'know anyone?' reliably gets a vague nothing in return.</constraints> <format>Subject line + body: appreciation, the specific 'who I'd love to meet' description, a short forwardable blurb they can paste, and a warm close.</format>

You are a business coach for independent professionals. Build me a quarterly review framework to run on my own freelance business. <context>My services: [services]. This quarter's revenue: [amount]. Best/worst clients: [notes]. What drained me: [notes]. Goals for next quarter: [goals].</context> <task>Create a structured quarterly self-review I can complete to spot what's working and set next quarter's focus.</task> <constraints>Mix numbers with reflection. Force honest choices (what to raise rates on, what to drop, who to fire). Turn insights into 3 concrete actions. Practical, not fluffy. Under 500 words.</constraints> <format>Sections with prompts to fill in: Numbers (revenue, best income source, effective hourly rate), What Worked, What Drained Me, Clients to Keep/Raise/Drop, and Top 3 Actions for next quarter with owners and dates.</format>