You are a senior freelance [DISCIPLINE — e.g. copywriter, designer, developer] who has sent hundreds of cold pitch emails and tracked which ones convert. Write a single cold pitch email that sounds like a real person, not a template.
About me:
- What I do: [ONE-LINE SERVICE DESCRIPTION]
- Strongest proof point: [A RESULT, CLIENT NAME, OR PORTFOLIO PIECE]
- My rate or starting price: [RATE OR "STARTING AT $X"]
About the prospect:
- Company: [COMPANY NAME]
- The person I'm emailing: [NAME, ROLE]
- Specific thing I noticed about their business: [PAGE, LAUNCH, JOB POST, NEWS]
- Why I think I can help: [ONE SENTENCE]
Write an email under 120 words with: a subject line that doesn't sound like marketing, a one-line opener referencing the specific thing I noticed, one sentence on what I do, one sentence of proof, and a single low-friction ask (a 15-minute call OR a yes/no question). No "I hope this finds you well." No "circling back." No emojis.
Why this works
The 120-word ceiling and the banned phrases ("hope this finds you well," "circling back") strip out the filler that gets cold emails deleted. Forcing one specific observation about the prospect makes the message feel researched instead of mass-produced.
Act as a senior freelance consultant who has won six-figure projects with clear, one-page proposals. Draft a project proposal for the prospect below.
Client context:
- Client: [COMPANY OR PERSON]
- Their goal: [WHAT THEY ACTUALLY WANT — IN THEIR WORDS IF POSSIBLE]
- Their pain today: [WHAT'S NOT WORKING]
- Timeline expectation: [IDEAL START AND END DATE]
- Budget signal: [STATED BUDGET, RANGE, OR "UNKNOWN"]
What I'd deliver:
- Service: [WHAT YOU DO]
- Deliverables: [LIST CONCRETE ARTIFACTS — E.G. 3 LANDING PAGES, 8 BLOG POSTS, BRAND GUIDE]
- My proposed price: [TOTAL OR PHASED]
Structure the proposal as a one-page document with: a one-sentence summary of what they'll have at the end, the outcome (in their language, not mine), a numbered list of deliverables, the timeline broken into phases, the investment, what's included and what's explicitly out of scope, and a short closing line on next steps. No fluff. No "synergy." Read like a senior practitioner, not a sales deck.
Why this works
Forcing an explicit "out of scope" section is the single biggest predictor of a project that ends well. The "in their language, not mine" line makes the model echo the client's words back, which is the oldest sales trick in the book and the reason proposals get signed.
You are a freelance pricing coach who has helped independents move from hourly to project-based and value-based pricing. Help me build a short internal pricing memo so I can quote this project with confidence.
Project context:
- Service: [WHAT I'M PROVIDING]
- Estimated hours of real work: [HOURS]
- My target hourly equivalent: [WHAT I WANT TO MAKE PER HOUR]
- Client size: [SOLO / SMALL BUSINESS / MIDMARKET / ENTERPRISE]
- Outcome value to the client: [WHAT IT IS WORTH IF IT WORKS]
- My current floor: [LOWEST PRICE I'D ACCEPT]
Produce:
1. A recommended quote (single number) with one line of reasoning
2. Three pricing options I could offer the client: low, standard, premium — each with what's included
3. The exact words I should use to present the price out loud, with no apologies and no over-explaining
4. The two most likely objections the client will raise, and a one-sentence response to each
5. The price I should walk away from
Be direct. Don't tell me to "charge what I'm worth." Give me numbers and language.
Why this works
Pricing is where most freelancers get vague advice. Demanding a single recommended number, an explicit walk-away point, and the literal sentence to say out loud forces the model to commit. The objection-handling pairs make sure you're not freelancing on tilt the second the client pushes back.
Act as a freelance project lead who has written scope of work documents tight enough to survive a difficult client. Draft a clear scope of work for the engagement below.
Engagement context:
- Client: [COMPANY OR PERSON]
- Project name: [WHAT WE'RE CALLING IT]
- Start date: [DATE]
- End date or duration: [DATE OR # OF WEEKS]
- Total fee: [PRICE AND PAYMENT TERMS]
What I'm doing:
- Service summary: [ONE PARAGRAPH]
- Concrete deliverables: [LIST EVERY ARTIFACT WITH QUANTITY]
- What I need from the client to deliver: [ASSETS, ACCESS, APPROVALS]
Structure the scope of work as: a one-paragraph project summary, a numbered deliverables table (item, quantity, format, due date), an explicit list of what is NOT included, the revision policy (how many rounds, what counts as a round), the change order process and rate for additional work, payment milestones tied to deliverables, and a section on assumptions that, if wrong, change the price or timeline. End with a signature block. Use plain English a non-lawyer client can sign.
Why this works
A scope of work that names what's NOT included, defines a "round" of revisions, and lists assumptions is a scope that survives contact with a stressed client. Most templates skip those three sections, which is why most freelancers eat the extra work.
You are a freelance project lead who runs calm, organized kickoffs that make clients feel like they hired a senior pro. Draft a kickoff document we'll review together on the first call.
Project context:
- Client: [COMPANY OR PERSON]
- Project: [PROJECT NAME]
- Goal of the engagement: [ONE-SENTENCE OUTCOME]
- Final deliverable: [WHAT THEY GET AT THE END]
- Total duration: [WEEKS OR DATES]
Produce a kickoff doc with:
1. A one-paragraph "what success looks like" section, written so the client recognizes their own goal
2. The decision-makers on their side and the single point of contact
3. A weekly working rhythm: meeting cadence, day, length, and what each meeting is for
4. The shared tools we'll use (file sharing, comms, project tracking) and where each lives
5. Working hours and response-time expectations on both sides
6. Three risks that could blow the timeline, and how we'll handle each early
7. The first three things I need from the client this week, with a deadline next to each
Tone: warm, structured, and confident. Like a senior practitioner setting a project up to actually finish.
Why this works
Naming a single point of contact and explicit response-time expectations on the first call kills 80% of the chaos that derails freelance projects. The "three things I need this week" list trains the client from day one to send things on time.
Act as a freelance project manager who writes weekly status updates that clients actually read. Draft a short, scannable update I can send to my client today.
Project context:
- Client: [COMPANY OR PERSON]
- Project: [PROJECT NAME]
- Week number: [E.G. WEEK 3 OF 8]
This week's raw notes (paste anything — bullet points, journal entries, half-sentences):
[PASTE YOUR WEEK]
What I need:
1. A one-line "headline" of the week (good news, bad news, or steady — be honest)
2. A "Done this week" section: 3-5 bullets, each with the concrete artifact or decision
3. An "In progress" section: what's actively moving and when it lands
4. A "Blocked / waiting on you" section with named asks and deadlines
5. A "Next week" preview: 2-3 lines on what I'll be working on
6. One "heads up" line if anything changed about scope, timeline, or risk
Keep it under 250 words. No corporate softening. If something is late, say it's late and say what we're doing about it.
Why this works
Clients fire freelancers for silence more often than for slipped deadlines. A weekly headline plus a named "Blocked / waiting on you" section makes the client feel managed and quietly trains them to unblock you. The 250-word cap forces the model to write something a busy person will actually finish reading.
You are a freelance negotiation coach who has helped hundreds of independents push back on scope creep without losing the client. Draft me a response script for the situation below.
The original scope: [WHAT WAS AGREED]
The new request: [WHAT THEY JUST ASKED FOR]
The relationship: [HOW LONG WE'VE WORKED TOGETHER, HOW PROFITABLE]
My capacity: [HAVE TIME / FULLY BOOKED / OVERLOADED]
Produce: a Slack/email reply that names the new request as out of scope without sounding cold, three options for how we could handle it (do it as a change order, swap something else out, defer to phase two), the price and timeline for the change order option, and a closing line that protects the relationship...
Act as a freelance coach who has trained hundreds of independents to collect testimonials that actually convert future leads. Draft a short email I can send to a happy client right now.
Client: [NAME, COMPANY, ROLE]
What we worked on: [PROJECT IN ONE SENTENCE]
The result: [SPECIFIC OUTCOME WITH A NUMBER IF POSSIBLE]
Our relationship: [WARMTH AND RECENCY]
Write an email under 120 words that thanks them, names a specific moment from the project, and asks for a testimonial in three optional formats (a written quote, a 2-minute Loom, or a LinkedIn recommendation). Include three short prompts they can answer instead of staring at a blank page...
You are a freelance business coach who has helped one-person operators turn one-off projects into stable monthly retainers. Build me a retainer proposal I can send to a client we just finished a project with.
Client: [COMPANY OR PERSON]
Project we just finished: [SUMMARY]
The result we delivered: [OUTCOME]
What ongoing work would look like: [HOURS, DELIVERABLES, CADENCE]
Proposed monthly fee: [PRICE OR RANGE]
Produce: a one-page retainer proposal with the ongoing outcome in their language, a monthly deliverables list, what's included and what's not, the cancellation terms, and the exact words to use in the email that sends it...
Act as a senior freelance practitioner who closes projects so cleanly that clients refer you within the week. Draft an end-of-project handoff document I can deliver alongside the final invoice.
Project: [NAME]
Client: [COMPANY OR PERSON]
Final deliverables: [LIST]
Where everything lives: [LINKS, REPOS, FOLDERS]
Required sections: a one-paragraph project recap, a deliverables index with links, a "how to maintain this" section for the client's team, recommended next steps if they want to keep growing, the support window after handoff, and a closing line that opens the door to a future engagement...