Best AI prompts for freelancers

This is the prompt library organized the way you actually work: by workflow stage, not by AI capability. Find the category that matches what you need right now, copy the prompt, fill in the brackets, and move on.

How to use this library

Every prompt in this guide uses [BRACKETS] to mark what you customize. Replace them with your actual details before you send. The more specific your replacements, the more useful the output. Treat everything AI generates as a strong first draft: your judgment, your voice, and your professional context always come last.

The library follows every stage of the freelance workflow, from the first outreach message to the referral request after a project ends.

If you work in English as a second language, the communication prompts help most with formal or firm emails. When the output reads naturally, send it with light edits: the goal is a professional email, not a writing test.

How to write a prompt that works

The prompts below already have a structure. When you write your own, or a prompt here gives you something generic, check it against five parts. You won’t need all five every time.

Context. Who you are, who the client is and what has happened so far. Give it what you would tell a new colleague before handing over the task. AI won’t ask follow-up questions; it will guess.
A specific task. Length, purpose and recipient. “Write an email” gets a generic email. “Write a 150-word follow-up to a prospect who showed interest two weeks ago but hasn’t replied to my proposal. Warm, not desperate. End with one clear question” gets one you can send.
Format and audience. Bullets or prose, how long, which tone, and who will read it. A client who isn’t technical and is worried about cost needs a different answer from an engineer.
A role, when it changes the answer. “Review this cash flow projection as a senior financial advisor looking for errors” helps. If the output would be the same without the role, leave it out.
An example. Showing beats describing. Paste an email whose tone you want to match, or a past deliverable whose structure you want to follow.

Iterate on the first draft

The first output shows you what the AI understood. Name exactly what is off, then fix that one thing:

“The tone is too corporate. Rewrite the opening so it sounds like one peer talking to another.”
“This doesn’t address the client’s budget concern. Add a paragraph after the deliverables on pricing flexibility.”
“Cut this by 30%. Drop the second section and tighten the rest.”

Stay in the same conversation while you refine, since it already holds the context, and start a new one when you switch tasks. For big jobs, go one step at a time: research, then analysis, then the draft, then formatting. A single prompt that asks for all four gets a mediocre version of each.

Outreach prompts

Prompts for researching a prospect, writing the first message, and following up until you get an answer.

Most outreach fails because it is about the freelancer, not the client. Prospects now get more messages than ever, many of them written by AI, and they spot a template at once. So AI has raised the bar for personalization, not lowered it: the messages that get answers could only have been written for that one reader. AI makes them faster to write. It doesn’t replace the research behind them.

Prospect research

“I’m preparing outreach to [PROSPECT: COMPANY, ROLE, INDUSTRY, WHAT THEY DO]. Here’s what I’ve found about them: [PASTE OBSERVATIONS: LINKEDIN POSTS, COMPANY NEWS, WEBSITE CONTENT, JOB POSTINGS, RECENT WINS, APPARENT CHALLENGES]. Identify: (1) the business challenge they most likely face that my services address, (2) a specific observation I could reference to show I’ve researched them, (3) the strongest reason for them to reply to me, and (4) any recent event that makes now a good time to reach out.”

When to use: Before any outreach that matters. Its answers are what make the messages below specific; skip it and you are writing from assumptions.

Cold outreach message

“Write a concise outreach message to a [TARGET CLIENT TYPE] who might need [YOUR SERVICE]. I’ve noticed: [SPECIFIC OBSERVATION ABOUT THEIR BUSINESS]. The message should: open with that observation rather than a generic compliment, connect it to a specific challenge they likely face, offer a specific relevant result I’ve achieved for similar clients, and end with a low-friction call to action. Under 100 words.”

When to use: Before reaching out to a new prospective client who has not asked for your services yet. The observation should be specific enough that the message couldn’t go to anyone else: a recent post, a job listing, a product launch.

Subject lines

“Generate 8 subject lines for this cold email: [PASTE EMAIL]. Vary them across question-based, observation-based, mutual connection, specific outcome, and curiosity. Keep each under 8 words. Avoid overused openers like ‘Quick question’, ‘I can help’ and ‘Checking in’.”

When to use: After the body is written, not before.

LinkedIn connection note

“Write a LinkedIn connection note to [PROSPECT DESCRIPTION]. What I noticed about them: [OBSERVATION]. Keep it under 200 characters and don’t pitch; the goal is a conversation. Then write a message for after they accept: the observation, one relevant result I’ve achieved, and a specific low-friction ask, under 100 words.”

When to use: When your prospects are active on LinkedIn. Save the pitch for after they accept.

Trigger event

“[PROSPECT DESCRIPTION] has recently [TRIGGER: RAISED FUNDING / LAUNCHED A PRODUCT / POSTED A JOB FOR X / PUBLISHED AN ARTICLE / COMMENTED ON MY POST ABOUT Y]. This matters for my services because [CONNECTION]. Write a brief message that references the event specifically, connects it to one way I could help, and proposes a conversation. Under 100 words. Don’t open with ‘Congratulations on your recent…’.”

When to use: Within a few days of the event, not weeks. News, a new hire or a comment on your content opens a door that closes again quickly.

Follow-up

“I sent this outreach message to [PROSPECT DESCRIPTION] [NUMBER] days ago and haven’t heard back: [PASTE ORIGINAL]. Write a [FIRST / FINAL] follow-up that doesn’t repeat the original, adds a new angle or something useful, and is shorter than the first message. If it’s the final one, leave the door open without guilt-tripping. Under 75 words.”

When to use: Send the first follow-up after 5 to 7 days and a final one two to three weeks after the first message. In Woodpecker’s roundup of cold email statistics, 42% of replies come from follow-ups, yet 48% of sales reps never send one.

Proposal prompts

Prompts for qualifying an inquiry, writing each part of a proposal, and following up after you send it.

Three things sink most proposals before price comes up: generic lines like “I’m passionate about quality”, a structure that leads with your process instead of the client’s problem, and an unclear investment section. AI can fix all three, but only from the context you give it. That is why the context prompt comes before any section prompt.

Responding to an inquiry

“A potential client has reached out about [THEIR NEED]. My profession: [DESCRIBE]. Write a brief reply that thanks them, asks the 2 to 3 qualifying questions I need to judge fit (budget, timeline and scope), and shows genuine interest without committing to anything. Warm but professional. Under 100 words.”

When to use: For every new inquiry. The qualifying questions are the point of the email, so don’t let the draft soften them.

Declining a project

“I need to decline a project from [CLIENT DESCRIPTION] because [REASON: WRONG FIT / NO CAPACITY / BUDGET TOO LOW / OUTSIDE MY EXPERTISE]. Write a brief decline that thanks them, gives the reason without over-explaining, keeps the door open for future work, and, if it helps, suggests [A REFERRAL / A LATER START / A SMALLER SCOPE]. Warm and final. Under 100 words.”

When to use: When the answers to your qualifying questions say no. “I’m not the right fit for this one” is a complete reason.

Project scope clarification

“I’ve received this client brief: [PASTE BRIEF]. Identify any ambiguities or missing information that I need to clarify before writing a proposal. List them as specific questions I should ask the client.”

When to use: Any time a brief feels vague or underspecified before you commit to a scope.

Proposal context

“I’m preparing a proposal. Use this context for every prompt that follows. Client: [COMPANY, SIZE, INDUSTRY, WHAT THEY DO]. Their stated need: [WHAT THEY ASKED FOR]. Their underlying problem: [WHAT YOU BELIEVE THEY ACTUALLY NEED TO SOLVE]. What matters most to them: [SPEED / QUALITY / COST / SPECIFIC EXPERTISE]. My relevant experience: [YOUR CLOSEST WORK AND ITS RESULTS]. My approach: [HOW YOU’D TACKLE IT]. Scope: [DELIVERABLES, TIMELINE, APPROXIMATE PRICE]. Competition: [WHO ELSE THEY’RE LIKELY TALKING TO]. Before drafting anything, list the concerns they may not have said out loud and the objections I’m most likely to face.”

When to use: Once per proposal, before any section prompt below. The underlying problem is the field most people skip: a client who asks for a new website may need a higher conversion rate, and one who asks for copy may need a positioning fix.

Proposal opening

“I’m a [YOUR PROFESSION] specializing in [YOUR NICHE]. My client is [CLIENT DESCRIPTION]. They need [PROJECT DESCRIPTION]. Their main concern seems to be [CLIENT PAIN POINT]. Write a compelling opening paragraph for a project proposal that directly addresses their concern and positions my approach as the solution.”

When to use: Before writing a full proposal when you know the client’s primary concern but are unsure how to lead with it. On Upwork and similar platforms, mention something specific from the job post: most proposals there open with a name and years of experience.

Deliverables and timeline

“Using the proposal context, write the deliverables and timeline section. List each deliverable specifically enough that the client knows exactly what they’ll receive, and note briefly what is not included. Then lay out the timeline phase by phase: [PHASES AND DATES], what I need from the client at each stage, and anything that could move the dates.”

When to use: In every proposal. Vague deliverables leave room for scope disputes later; specific ones close it.

Proposal pricing rationale

“I’m proposing [AMOUNT] for [PROJECT SCOPE]. Write 2 to 3 sentences that justify this investment in terms of client value and outcomes, without being defensive about the price.”

When to use: When you need to explain your fee in a proposal without it reading as an apology. If the draft hedges, ask for a version with every qualifier removed, and put your payment terms right after the price.

Closing and next step

“Using the proposal context, write the closing section. Sum up in one sentence why this approach fits, propose one specific next step ([DISCOVERY CALL / KICKOFF DATE / DECISION BY A DATE]), and give a reason to move now without pressure. Under 75 words.”

When to use: At the end of every proposal. “Let me know if you have any questions” gives the client permission to drift. A specific next step gives them something to do.

Retainer proposal

“Using the proposal context, adapt my proposal for an ongoing monthly retainer instead of a one-off project. Explain the value of working together continuously, describe what a typical month looks like in practice, explain how requests beyond the monthly scope are handled, and set out the benefits to the client: consistency, priority access and a predictable cost.”

When to use: When the work is ongoing. A retainer pitched as a project with a monthly price undersells the relationship the client is actually buying.

Proposal review

“Review this proposal for [CLIENT DESCRIPTION]: [PASTE PROPOSAL]. Evaluate: (1) how specific it is to this client versus generic, (2) whether it leads with their problem or with my process, (3) how clear and confident the investment section is, (4) how strong the call to action is, and (5) what a competing proposal might do better. Then rewrite the most generic section using this extra context: [DETAILS ONLY THIS CLIENT WOULD RECOGNIZE].”

When to use: Before you send. If a section could have been written for any client, the fix is more specific context, not better phrasing. For the client’s own reaction, use the client perspective prompt further down.

Following up on a proposal

“I sent a proposal to [CLIENT DESCRIPTION] for [PROJECT] [NUMBER] days ago and haven’t heard back. Write a brief follow-up that references the proposal specifically, invites questions or concerns, and ends with a gentle call to action. Confident, not anxious. Under 75 words.”

When to use: When a client goes quiet after your proposal. Silence is normal, not a rejection, so follow up once and clearly.

Win/loss review

“I recently [WON / LOST] a proposal for [PROJECT DESCRIPTION]. What I know about the outcome: [PRICE WAS TOO HIGH / THEY CHOSE A COMPETITOR / THEY SAID X / THEY MENTIONED Y WHEN THEY SAID YES]. Help me identify what likely drove the result, what to change in my next similar proposal, and which patterns to track across proposals.”

When to use: After every decision, win or lose. Every few months, also paste in your proposal template and ask which sections read the same for every client.

Pricing prompts

Prompts for researching your rate, building a quote, and holding your price when a client pushes back.

AI is good at structuring pricing research and drafting the conversation. It is not a reliable source of current market rates. In a 2026 analysis by Payscale, ChatGPT’s rate range for one role came out nearly $30,000 higher than validated HR-reported data, a 10% inflation. Treat any figure AI gives you as a starting hypothesis, and check it against current platform data such as Upwork’s cost-to-hire pages, industry salary surveys, and conversations with peers before you act on it.

Rate research

“I’m a freelance [YOUR PROFESSION] with [NUMBER] years of experience, specializing in [YOUR NICHE]. I’m based in [YOUR COUNTRY/CITY] and mostly work with clients in [CLIENT GEOGRAPHY: local / US / EU / global]. My current rate is [CURRENT RATE]. Help me think through how to research the right market rate: which factors to consider, how being a [GENERALIST / SPECIALIST IN X] affects what I can charge, and which sources to check. Tell me where your data for this niche and location may be limited.”

When to use: Before you set or raise a rate. Use the answer to plan your research, not as the number itself.

Project quote estimate

“I need to quote a [PROJECT TYPE] for a client. Here is what they need: [DESCRIBE THE SCOPE]. My hourly rate is [RATE]. Help me: (1) estimate how many hours this will realistically take, (2) spot scope elements I might be underestimating, (3) suggest whether to quote hourly or a fixed price for this kind of project, and (4) list any ambiguities I should clarify before quoting.”

When to use: Before any quote goes out. The fourth answer is often the most valuable, because unclear scope is where fixed-price projects go wrong.

Tiered pricing options

“I want to offer a client three pricing tiers for [SERVICE TYPE]. My target engagement value is about [MIDDLE TIER AMOUNT]. My profession: [DESCRIBE]. Typical deliverables: [DESCRIBE]. Create three packages that anchor the client on a premium tier, make the middle tier feel like the best value, and make sure even the entry tier delivers genuine value. Name each tier, describe what’s included, and suggest a price for each.”

When to use: When you’d rather give a client a choice than a yes-or-no price. The tier they pick also tells you their budget ceiling without you having to ask.

Responding to “that’s too expensive”

“A client has replied to my quote of [AMOUNT] for [PROJECT DESCRIPTION] with ‘that’s more than we budgeted.’ Draft three possible responses: (1) one that holds the rate and reframes the value, (2) one that offers a reduced scope at a lower price, and (3) one that acknowledges the gap and gracefully declines if they can’t meet the rate. All three should keep the relationship professional.”

When to use: Once a client has pushed back, and not before: volunteering a lower number before they say anything is one of the most expensive habits in freelancing. Read their tone before you pick a reply.

Underpricing check

“Here is a description of my freelance services and positioning: [YOUR WORK, NICHE, RESULTS, AND CURRENT RATES]. Identify signals that suggest I may be underpricing. Consider how specific my niche is, the results I can claim, the types of clients I serve, and how I describe my work. Flag any assumptions you’re making about market rates.”

When to use: Once a quarter, or when your income feels out of line with your workload. Common signs: you win every bid, clients accept without negotiating, you resent the work at the rate you quoted, or your rate hasn’t moved in more than 12 months.

Negotiation prompts

Prompts for preparing a negotiation, trading on rate and scope, and pushing back on contract terms.

AI gets you to the table prepared: it finds the words, anticipates objections, and stress-tests your position before the client says a word. It doesn’t give you leverage you don’t have, and the call on when to push and when to concede stays yours. The fear of asking is usually bigger than the risk. A survey published by The Open Notebook found that only 12% of editors had ever revoked an assignment because a freelancer asked for a higher rate.

Negotiation preparation

“I’m about to negotiate [A RATE INCREASE / SCOPE REDUCTION / CONTRACT TERMS] with [CLIENT DESCRIPTION]. My goal: [IDEAL OUTCOME]. My minimum acceptable outcome: [DESCRIBE]. What I believe the client’s priorities are: [DESCRIBE]. My leverage: [DESCRIBE]. Help me: (1) identify the strongest arguments for my position, (2) anticipate their likely objections and how to respond, (3) suggest creative solutions that could work for both of us, and (4) show where I might have more flexibility than I think.”

When to use: Before any negotiation with real stakes. The prompts below work better once you know your goal and your minimum.

Trading rate for better terms

“My client wants to lower my quoted rate of [AMOUNT] for [PROJECT DESCRIPTION]. Instead of simply accepting less, I want any reduction to come with better terms. Draft a professional response that acknowledges their budget concern, offers [LOWER RATE] in exchange for [BETTER TERM: shorter payment terms / fewer revision rounds / smaller scope / larger deposit], frames this as a fair exchange rather than a compromise, and keeps a collaborative tone.”

When to use: When a client pushes back on your rate. A straight discount hands them something for nothing; a trade gives both sides something.

Budget cut without a scope cut

“My client wants to cut our project budget from [ORIGINAL AMOUNT] to [REDUCED AMOUNT] but hasn’t mentioned reducing the scope. Draft a response that acknowledges the budget constraint without judgment, explains that I can work within the new budget by adjusting the scope, proposes [REDUCED SCOPE] as what’s achievable at that budget, and makes clear that the full original scope needs the full original budget. Tone: professional and solution-focused.”

When to use: When a client lowers the budget but still expects the same work. That’s a scope conversation, not a budget one.

Pushing back on contract terms

“My client’s contract includes [UNFAVORABLE TERM: net 60 payment / payment on completion only / full IP transfer with no portfolio rights / a broad non-compete]. I want to negotiate [WHAT YOU WANT: net 14 / milestone payments / a 30% deposit / portfolio rights / a restriction limited to direct competitors for a shorter period]. Draft a professional response that acknowledges their standard terms and the concern behind them, explains my position briefly, proposes specific alternative language, and offers [COMPROMISE] if needed. Frame it as standard professional practice.”

When to use: Before you sign a contract the client wrote. Payment windows, IP rights, and non-competes are starting positions, not fixed facts.

Preparing for a no

“I’m about to make a request my client might refuse: [DESCRIBE]. If they say no, my options are: [ACCEPT THEIR TERMS / REDUCE SCOPE / WALK AWAY / PROPOSE AN ALTERNATIVE]. For each option, draft a brief professional response I could use, so I’m prepared for any outcome.”

When to use: Before any request that matters. A fallback only counts if it’s real: the Program on Negotiation at Harvard Law School describes a true BATNA (your best alternative to a negotiated agreement) as a plan you are willing and able to execute, not a bluff.

Whatever you agree, confirm it in writing before work starts, because terms agreed on a call tend to get contested later. The contract summary prompt further down turns a verbal agreement into a short confirmation for the client.

Contract drafting and review prompts

Prompts for drafting a freelance agreement, writing the clauses that protect you most, and reviewing a contract a client sends you.

These prompts produce a starting draft, not a final legal document, and this page is not legal advice. Legal requirements and enforceability vary by country and state, and AI can write confident-sounding clauses that won’t hold up where you or your client are based. For high-value work, complex IP, international clients, or anything with real dispute potential, professional legal review is strongly recommended. According to ContractsCounsel’s marketplace data, a lawyer’s review of a freelance contract averages $354, a meaningful investment on a $10,000 project and an obvious one on a $50,000 engagement.

Freelance services agreement

“I’m a [YOUR PROFESSION] based in [YOUR COUNTRY/STATE], entering a contract with a [CLIENT TYPE: individual / small business / enterprise] based in [CLIENT COUNTRY/STATE] for [PROJECT DESCRIPTION] worth about [PROJECT VALUE]. The project involves [IP TRANSFER / NDA / ONGOING RETAINER / OTHER]. Draft a freelance services agreement covering: scope and deliverables, timeline and milestones, payment terms and schedule, a revision policy that separates revisions from scope changes, intellectual property ownership, confidentiality, my status as a self-employed freelancer rather than an employee, termination and kill fee, and limitation of liability. Use clear section headings, and after each section flag any language where jurisdiction-specific legal review is particularly important.”

When to use: For a new client when you don’t have a template yet. Your profession, the project value, and where both of you are based all change what a contract should say, so fill in every bracket.

Payment terms and late payment clause

“Write a payment terms clause for a freelance contract. Payment structure: [MILESTONE / HOURLY / FIXED FEE]. Schedule: [MILESTONES OR INVOICING SCHEDULE]. Due date: net [NUMBER] days from the invoice date. Include a late payment provision charging [PERCENTAGE]% monthly interest on overdue balances, and a clause that lets me pause all work if payment is [NUMBER] days overdue, with no obligation to deliver further work until the balance is cleared. Jurisdiction: [COUNTRY/STATE].”

When to use: In every contract. The work-pause clause matters most: without it, you may have to keep delivering while you wait to be paid, so give it a specific number of days.

Kill fee and termination clause

“Write a termination clause for a freelance services contract. Include: (1) either party may terminate with [NUMBER] days’ written notice, (2) the client pays for all work completed up to the termination date, (3) a kill fee of [PERCENTAGE]% of the remaining contract value if the client terminates after [MILESTONE / DATE / PERCENTAGE OF WORK COMPLETED], and (4) clear language defining what counts as completed work for payment. Jurisdiction: [COUNTRY/STATE].”

When to use: For any project that could be cancelled midway. Kill fees of 25 to 50% of the remaining contract value are standard across creative industries; decide the trigger point before you generate, because AI can’t make that call for you.

Intellectual property clause

“Write an intellectual property ownership clause for a freelance [PROJECT TYPE] contract. The client wants [FULL OWNERSHIP TRANSFER / LICENSE ONLY / SPECIFIC USE RIGHTS]. I want to keep [NOTHING / PORTFOLIO RIGHTS / UNDERLYING TOOLS OR CODE / TEMPLATES]. Jurisdiction: [COUNTRY/STATE]. Make the ownership transfer explicit and conditional on receipt of full payment, and flag anything that may need jurisdiction-specific review.”

When to use: For creative and technical work, where vague ownership language invites disputes. Countries treat work-for-hire and IP assignment very differently, so take the flags seriously.

Client contract review

“Review the following contract a client has sent me. I am a freelance [YOUR PROFESSION]. Identify: (1) clauses that significantly favor the client over me, (2) missing clauses that would normally protect the service provider in this kind of agreement, (3) vague language that could disadvantage me in a dispute, and (4) whether the intellectual property terms are reasonable for this type of project and project value. Flag each issue by section number and severity, and note where professional legal review is particularly important. Here is the contract: [PASTE CONTRACT]”

When to use: Whenever a client sends you their own agreement. Name your profession, because what’s standard depends on the work: a full IP transfer is normal for a logo project and unusual for ongoing consulting.

Before an AI-drafted contract goes to a client, check that every bracket is filled, the payment, IP, and kill fee terms match what you actually agreed, and every section AI flagged for legal review has been dealt with. AI wrote the structure and the language; you own the accuracy.

Project execution prompts

Prompts for briefing, research, quality review, and deliverable production.

Project kickoff brief

“I’m starting a [PROJECT TYPE] for a client who is [CLIENT DESCRIPTION]. The goal is [PROJECT GOAL]. Key constraints are [CONSTRAINTS]. Write a project kickoff brief I can share with the client covering: objectives, scope, deliverables, timeline, payment terms and invoicing schedule, communication expectations (response times, channels, urgent requests), and what I need from them.”

When to use: At the start of any new project to align expectations before work begins. With the invoicing schedule in writing, the first invoice is no surprise, and agreed response times give you something to point to when a client expects an instant reply late at night.

Quality review

“Review the following [DELIVERABLE TYPE] I’ve prepared for [CLIENT DESCRIPTION AND GOAL]: [PASTE DELIVERABLE]. Identify: (1) any logic gaps or unsupported claims, (2) sections that could be clearer for a [TARGET AUDIENCE] reader, (3) anything that doesn’t serve the stated goal, (4) any tone inconsistencies.”

When to use: Before sending any deliverable to a client, as a final editorial check.

Domain knowledge primer

“I’m a [YOUR PROFESSION] working on a project for a client in [INDUSTRY]. I need to understand [SPECIFIC CONCEPT] well enough to [SPECIFIC TASK]. Give me a 300-word primer covering key concepts, standard terminology, and common pitfalls I should know. Flag anything I should verify independently.”

When to use: When starting work in an unfamiliar industry or technical area.

Scope change documentation

“My client has requested a change to our agreed project scope. Original scope: [DESCRIBE]. Requested change: [DESCRIBE]. Write a professional email documenting the change, its impact on timeline and cost, and requesting written approval before I proceed.”

When to use: The moment a client asks for something that was not in the original agreement.

Deliverable variants

“Generate [NUMBER] alternative versions of the following [HEADLINE / TAGLINE / OPENING SENTENCE / CONCEPT]: [PASTE ORIGINAL]. Vary them across [SPECIFY DIMENSIONS: tone, approach, format, angle].”

When to use: When you need options to present to a client or want to test different creative directions.

Client communication prompts

Prompts for project updates, deliveries, revisions, and the difficult conversations in between.

Project status update

“Write a brief client-facing project update email. Project: [PROJECT NAME]. Client: [CLIENT DESCRIPTION]. Current status: [WHAT’S DONE, WHAT’S IN PROGRESS]. Any blockers or decisions needed: [DESCRIBE]. Next milestone: [WHAT’S NEXT AND WHEN]. Tone: professional and confident. Under 150 words.”

When to use: For any scheduled or spontaneous update to keep a client informed without overcommunicating.

Chasing missing assets

“I need [SPECIFIC INFORMATION OR ASSETS] from my client to move on to [PROJECT STAGE], and they haven’t sent it yet. Write a short request that says exactly what I need, why and by when, what happens to the timeline if it arrives late, and makes it easy to reply. Helpful, not pushy. Under 150 words.”

When to use: When a project stalls on the client’s side. Clients often hold things up because they don’t know exactly what you need or why.

Delivery email

“Write an email delivering [DELIVERABLE] to my client. Include: what’s been delivered and where to find it, the key points to review or decisions they need to make, how revisions work ([NUMBER] rounds included and how to send feedback), and when they’ll hear back from me. If this is the final delivery, also ask for formal sign-off and include any handover information. Organized and professional. Under 200 words.”

When to use: With every delivery. Stating the revision process up front isn’t confrontational: it’s the information the client needs to give useful feedback.

Revision request response

“My client has sent the following feedback: [PASTE FEEDBACK]. Write a professional response that: acknowledges their feedback specifically, confirms what I’ll change, pushes back politely on [SPECIFIC POINT IF APPLICABLE], and sets a timeline for the revised version.”

When to use: After receiving client feedback, especially when some of it requires gentle pushback.

Revision overload

“My client is asking for revisions beyond the [NUMBER] rounds we agreed. This is round [NUMBER]. Write a message that acknowledges their input, notes that we’ve used the included rounds, explains how extra revisions work ([RATE OR PROCESS]), and keeps the tone collaborative. Firm but friendly. Under 150 words.”

When to use: As soon as a request goes past the agreed rounds, not three rounds later. The number was in your contract and your delivery email, so this is a reminder, not a confrontation.

Difficult conversation email

“I need to tell my client [DIFFICULT MESSAGE: timeline delay, scope problem, mistake]. Write a professional email that: takes appropriate responsibility without over-apologizing, explains what happened briefly, states clearly what I’m doing to address it, and focuses on moving forward. Tone: honest, calm, solution-focused.”

When to use: When something has gone wrong and you need to communicate it without damaging the relationship.

Sending a difficult message is professional behavior, not weakness. The clients who receive honest, solution-focused communication are more likely to keep working with you.

Recording advice the client didn’t take

“My client wants to go ahead with [THEIR DECISION] although I recommended [MY ADVICE]. The risks are [DESCRIBE]. Write an email that records my recommendation, lists the specific risks without condescension, confirms that the decision is theirs, and asks for written confirmation to proceed. Serious and factual. Under 200 words.”

When to use: When a client overrules you on something you believe is a mistake. If the problem shows up later, the record protects you, so keep it factual, not adversarial.

Ending a client relationship

“I need to end my working relationship with a client because [REASON: PERSISTENT SCOPE CREEP / LATE PAYMENT / REPEATED UNPROFESSIONAL BEHAVIOR / IT ISN’T WORKING]. I want to finish any contractual obligations, give appropriate notice, and close professionally without burning the bridge. Write the message. Professional and final, no hostility.”

When to use: When the same problem keeps coming back despite clear conversations. Keep the reason short: “this engagement is no longer working for either of us” is enough and leaves nothing to argue with.

Business and financial management prompts

Prompts for invoicing, rate discussions, and business documentation.

Invoice line item description

“Write professional invoice line item descriptions for the following work: [BRIEF DESCRIPTION OF WHAT YOU DID]. Client type: [DESCRIBE]. Format: [NUMBER] line items, each 10 to 15 words, describing the deliverable and its value.”

When to use: When creating an invoice and your line items sound generic or unclear.

If you work with clients across different countries, Ruul lets you send professional invoices in 190 countries without needing a registered company. Ruul acts as the legal counterparty, issues the invoice to the client, collects payment, and pays you within one business day after the client pays.

Rate increase communication

“I need to inform an existing client that my rates are increasing from [CURRENT RATE] to [NEW RATE] effective [DATE]. Write a professional email that: gives appropriate notice, briefly frames the increase in terms of value, maintains a positive tone, and makes it easy for them to continue working with me.”

When to use: When communicating a rate change to any existing client.

Give at least 30 days’ notice, and 60 to 90 days for raises of more than 30%. If the client pushes back, offer a transition, such as a phased increase or the new rate on new projects only, rather than dropping the increase.

Late payment follow-up

“Write a [STAGE 1 / STAGE 2 / STAGE 3] payment reminder for invoice [NUMBER] totaling [AMOUNT] that was due [NUMBER] days ago. Client relationship: [DESCRIBE: new client, established, large company]. Tone: [WARM / FIRM / FORMAL].”

When to use: At each stage of chasing an overdue invoice, adjusting tone as the delay grows.

According to Remote’s 2025 contractor management report, 85% of freelancers have experienced late invoice payments. Sending a payment reminder is professional behavior, not rudeness.

Platforms like Ruul handle payment tracking and automatic reminders, so the follow-up happens without you having to think about it.

Pausing work for non-payment

“My client hasn’t paid invoice [NUMBER] for [AMOUNT], which was due [NUMBER] days ago, and I’ve sent [NUMBER] reminders. Write a message telling them I’m pausing work on [PROJECT] until payment arrives, referencing our agreed payment terms, and setting out what needs to happen for work to resume. Formal and factual. Under 150 words.”

When to use: After the reminders have gone unanswered, and ideally backed by the work-pause clause from the payment terms prompt above. A pause is a business decision, not a punishment, so state it that way.

Contract summary

“I’ve agreed the following terms with a client verbally: [DESCRIBE KEY TERMS]. Write a brief written summary of these terms that I can send to the client for confirmation before starting work. Include: scope, deliverables, timeline, payment terms, revision policy.”

When to use: After any verbal agreement, before a single billable hour is logged.

If you work with international clients and do not have a registered company, Ruul’s Contractor of Record model means you can invoice legally without setting up a business entity. For freelancers on recurring retainers, Ruul’s subscription invoicing automates the recurring invoice cycle entirely.

Marketing and business development prompts

Prompts for portfolio content, LinkedIn presence, and the relationships that bring in your next client.

Case study draft

“Write a 400-word case study for my portfolio. Client background: [DESCRIBE]. Problem they faced: [DESCRIBE]. My approach: [DESCRIBE]. Results achieved: [DESCRIBE]. Format: brief client introduction, the challenge, my approach, the outcome, a short quote I can attribute to the client. Professional but not stiff tone.”

When to use: After completing any project that produced measurable results worth documenting.

LinkedIn post

“Write a LinkedIn post from my perspective as a [YOUR PROFESSION]. Topic: [DESCRIBE: a lesson learned, a client outcome, an industry observation]. Tone: genuine, professional, first person. Include a specific observation or insight, not just general advice. 150 to 200 words. End with a question to encourage engagement.”

When to use: For regular LinkedIn content that builds authority in your niche.

Bio for different contexts

“Write three versions of my professional bio: short (50 words), medium (100 words), and full (200 words). I am a [DESCRIBE YOUR WORK, SPECIALIZATION, AND NOTABLE ACHIEVEMENTS]. Perspective: third person. Tone: confident and specific, not generic.”

When to use: When updating your website, a platform profile, or a speaker introduction.

Service description

“Write a service description for my [SPECIFIC SERVICE] aimed at [TARGET CLIENT TYPE]. The description should: identify the problem they’re experiencing, explain what I do, communicate the outcome they’ll get, and differentiate from generic alternatives. Under 120 words.”

When to use: For your website, a proposal appendix, or any client-facing service overview.

Reconnecting with a past client

“I worked with [CLIENT DESCRIPTION] on [PROJECT TYPE] about [TIMEFRAME] ago. Write a brief message that references our past work specifically, gives a natural reason to get back in touch ([NEW RELEVANT WORK / THEIR RECENT NEWS / AN IDEA FOR THEM]), and ends with a specific question. Warm, not salesy. Under 100 words.”

When to use: For past clients and leads that went quiet. They already know your work, so you only need a reason to reconnect. A specific question turns a check-in into a conversation: “I saw you launched [PRODUCT]. How did it go?” beats “What are you working on these days?”

Referral request

“I’d like to ask [CLIENT DESCRIPTION] for a referral. Our work together: [BRIEF DESCRIPTION]. Write a short message that thanks them, describes the kind of client or project I’m looking for, makes a specific ask, and makes it easy to say yes or no. Warm and direct. Under 100 words.”

When to use: After a project that went well. Be specific about who you want: “other Series A SaaS founders” produces referrals, while “anyone who might need my services” rarely does.

Testimonial request

“I’d like a testimonial from [CLIENT DESCRIPTION] about our work on [PROJECT]. Write a short request that names the format I’d like (written, LinkedIn recommendation or video), suggests 2 to 3 specific questions to answer, and makes it easy for them. Appreciative and specific. Under 150 words.”

When to use: While the results are fresh. Questions like “What changed after the project?” and “What was working together like?” get you a testimonial that says something specific, not generic praise.

Referral partner

“I want to build a referral relationship with [ADJACENT FREELANCER / AGENCY / OTHER PROFESSIONAL]. We serve [OVERLAPPING CLIENT TYPES] with different, complementary services. Write a message that makes the fit clear, proposes [REFERRING WORK TO EACH OTHER / TAKING ON THEIR OVERFLOW OR WHITE-LABEL WORK], and suggests a short call as the next step. Under 125 words.”

When to use: With professionals whose clients regularly need what you do. One well-chosen partner can send a steady stream of warm introductions.

Portfolio writing prompts

Prompts for turning finished projects into portfolio pieces that show what changed because of your work, not just what you did.

Most portfolios list tasks, like “I designed a homepage,” while clients hire on outcomes. AI is good at turning task language into outcome language and getting you past the blank page. The specifics that make a piece true are yours, and so is the check that every claim matches what actually happened.

Portfolio context

“I’m writing portfolio content about the following project. Use this context for every prompt that follows. Project: [BRIEF DESCRIPTION]. Client: [CLIENT TYPE AND INDUSTRY; NO NEED TO NAME THEM IF CONFIDENTIAL]. The problem I was solving: [THE UNDERLYING BUSINESS PROBLEM]. What I did: [APPROACH AND DELIVERABLES]. Results: [METRICS, FEEDBACK, OR OBSERVABLE OUTCOMES]. What made it distinctive: [ANYTHING UNUSUAL ABOUT THE APPROACH OR OUTCOME]. Who I want to attract: [TARGET CLIENT TYPE].”

When to use: Once per project, before you write anything about it. Reuse it in the prompts below, in the case study and bio prompts above, and in the testimonial request above.

Outcome language without metrics

“I completed the following project but don’t have specific metrics: [DESCRIBE THE PROJECT AND WHAT WAS DELIVERED]. Write 5 outcome statements, from conservative to more specific, that describe the impact directionally without inventing numbers and are still more compelling than a plain task description.”

When to use: When the client never shared results or the project launched after you left. “Reduced friction in the checkout process” says more than “designed the checkout page,” but only use a statement you can stand behind.

Asking a past client for results

“I want to follow up with a client from a [PROJECT TYPE] project that ended [TIMEFRAME] ago and ask for outcome data I can use in my portfolio. Write a brief message that explains what I’m looking for (specific metrics or observations), makes it easy for them to reply, and offers to share the case study with them before I publish it. Under 75 words.”

When to use: Before you write up a project whose results you never saw. The client may have numbers you don’t, and asking for them is professional.

Case study headlines

“Generate 6 case study headline options for this project: [PASTE PROJECT CONTEXT]. Use these formats: (1) outcome-led, ‘[SPECIFIC OUTCOME] for [CLIENT TYPE]’, (2) problem to solution, ‘From [PROBLEM] to [OUTCOME]’, and (3) approach-led, ‘How I [APPROACH] to achieve [OUTCOME]’. Avoid generic titles like ‘Web Development Project’.”

When to use: Once a case study is drafted. A specific headline frames the work; a generic one buries it.

Generic-to-specific rewrite

“The following portfolio description is too generic: [PASTE DESCRIPTION]. Here is more context about the project: [SPECIFIC DETAILS, OUTCOMES, AND APPROACH]. Rewrite it to be significantly more specific and outcome-focused for [TARGET CLIENT], specific enough that a client in [INDUSTRY] would recognize their own situation.”

When to use: On any existing description or bio that leans on words like “passionate” or “results-driven.” It’s the fastest way to improve a portfolio you already have.

Productivity and thinking prompts

Prompts for decision-making, problem-solving, and professional development.

Decision framework

“I’m deciding whether to [DESCRIBE DECISION]. Key factors I’m considering: [LIST FACTORS]. Risks I’m worried about: [LIST RISKS]. What am I likely missing in my analysis? What questions should I be asking that I’m not asking?”

When to use: Before making any significant business decision where you suspect blind spots.

Client perspective simulation

“Read the following [PROPOSAL / EMAIL / DELIVERABLE]: [PASTE CONTENT]. Respond as a [DESCRIBE CLIENT TYPE] who is evaluating this. What concerns or objections would you have? What would you find convincing? What questions would you ask before saying yes?”

When to use: Before sending any high-stakes proposal or deliverable, to identify gaps before your client does.

This is one of the most underused prompts in freelancing. Most AI prompt guides skip it. The feedback it generates is the closest thing to a free client review before you hit send.

Project retrospective

“I’ve just completed a project for [CLIENT TYPE]. What went well: [DESCRIBE]. What went less well: [DESCRIBE]. What I’d do differently: [DESCRIBE]. Help me turn this into 3 specific process improvements I can implement in my next project.”

When to use: At the close of every project, to turn experience into a repeatable system.

Skill gap identification

“I’m a [YOUR PROFESSION] specializing in [YOUR NICHE]. I want to increase my income by [GOAL]. Based on this context, what are the 3 most likely skill gaps limiting my earning potential, and what specific steps would address each one?”

When to use: When growth feels stalled and you need an outside perspective on what to develop next.

Maintaining and expanding your prompt library

Save every prompt that produces strong output. A Notion page, a plain text file, or a dedicated document works fine. The format matters less than the habit. Organize it by task type, the way this guide is, and keep the parts that change in brackets. When you save a prompt, add a note about what context it needs and what it produces well. Your library improves with use, and a prompt that took 10 minutes to refine once can save you that same 10 minutes every time you use it afterward.

The prompts in this guide are starting points. The most effective prompt library you will ever have is the one you build from your own work, your clients, and your specific context.

Save this library and come back to it as your prompting needs grow. For the parts of your freelance workflow that do not need prompting at all, including invoicing, payment collection, automatic reminders, and tax-ready documentation, Ruul handles them automatically. Whether you prefer traditional bank transfers or want to withdraw earnings in crypto, you can get paid in 140+ currencies across 190 countries.