You spent your Connects on twelve proposals this week and heard back from two.
The problem is rarely your skills. It is usually that each proposal looks like the other forty in the client’s inbox: a friendly greeting, a list of what you can do, and no sign that you read the job post.
The Claude prompts for winning Upwork contracts below fix that at every stage. They help you decide which jobs deserve a bid, write proposals that open with the client’s problem, price your work without undercutting yourself, handle pushback, and follow up without sounding desperate.
You get 10 prompts, each with a role, your context, a step-by-step process, firm rules, and an exact output format. Paste in the job post and your real details, and you should get a usable draft on the first try.
One rule runs through all of them: Claude never invents your experience or results. Clients check, and a single made-up claim can cost you the contract.
How to Use These Claude Prompts for Winning Upwork Contracts
A few habits make every prompt below work better.
Paste the full job post. Include the title, description, budget, and screening questions. Claude can only mirror language it can see.
Keep a “proof file.” Write down three to five real results from past work, with numbers where you have them. You will paste from it into several prompts.
Edit before you send. Claude writes the draft, but you add the one detail only you know. That small touch is what separates a proposal from a template.
The prompts use XML-style tags to separate your material from the instructions. Anthropic’s prompting guidance recommends this structure because it keeps Claude from confusing your pasted text with its task.
Claude Prompts for Finding and Vetting the Right Upwork Jobs
Winning more contracts starts with bidding on better jobs. These two prompts stop you from wasting Connects.
1. Decode a Job Post and Decide Whether to Bid
Job posts often hide the real problem, the real budget, and the warning signs. This prompt pulls all three out.
<role>
You are an experienced freelance consultant who has won hundreds of contracts on Upwork and knows how to read a job post like a client, not just a freelancer. You are honest, even when the honest answer is "skip this one."
</role>
<context>
I am deciding whether to submit a proposal for the job below. Analyze it using only the text provided and the details of my own background. Do not invent facts about the client.
</context>
<inputs>
Full job post (title, description, budget, screening questions): {{PASTE THE FULL JOB POST}}
My skills and relevant experience: {{PASTE YOUR PROFILE SUMMARY}}
My target rate and minimum acceptable rate: {{PASTE RATES}}
Hours per week I have available: {{PASTE AVAILABILITY}}
</inputs>
<instructions>
1. Summarize in three sentences what the client says they want, then in one sentence what problem they most likely need solved underneath it.
2. List the explicit requirements, then the likely hidden requirements (things the client expects but did not state).
3. List red flags found in the post, such as unclear scope, a budget that does not match the work, requests for free samples or unpaid tests, requests to communicate off the platform, or unrealistic deadlines. Quote the exact text for each.
4. List green flags, such as a clear brief, defined deliverables, a realistic budget, or signs of an ongoing relationship.
5. Estimate the effort as a range of hours and calculate the effective hourly rate if the budget is fixed. Show the math.
6. Rate my fit as Strong, Moderate, or Weak, with the reasons tied to my background.
7. Give a recommendation: Bid, Bid With Conditions, or Skip. State the conditions if any.
8. List up to five questions I should ask the client in my proposal or first message.
9. List the ten most important words and phrases from the post that I should mirror naturally.
</instructions>
<rules>
- Use only the post text and my details. Write UNKNOWN for anything not stated.
- If my fit is weak, say so plainly. Do not encourage a bid just to be positive.
- Do not draft the proposal yet.
</rules>
<output_format>
Headings in order: What the Client Wants, Hidden Requirements, Red Flags (table: Quote, Concern), Green Flags, Effort and Effective Rate, My Fit, Recommendation, Questions to Ask, Words to Mirror.
</output_format>
If the recommendation is “Skip,” believe it. Every Connect spent on a poor-fit job is one you cannot spend on a better one.
2. Vet the Client Before You Spend Connects
Upwork’s own guidance suggests looking at the client’s profile before you send a proposal, and it pays off. Check the client’s Upwork profile before you send anything.
<role>
You are a freelance risk analyst who evaluates clients on freelance platforms. You weigh evidence carefully and never treat missing information as proof of a problem.
</role>
<context>
Below is the information Upwork shows about a client. Assess how reliable and worthwhile this client is, and tell me how to adjust my approach.
</context>
<inputs>
Payment method verified: {{YES, NO, OR UNKNOWN}}
Total amount spent on the platform: {{AMOUNT OR UNKNOWN}}
Hire rate and number of jobs posted: {{DETAILS OR UNKNOWN}}
Average hourly rate paid: {{AMOUNT OR UNKNOWN}}
Member since and location: {{DETAILS}}
Reviews from freelancers, with ratings and comments: {{PASTE REVIEWS, OR WRITE "NONE"}}
Other jobs this client has posted recently: {{PASTE TITLES AND BUDGETS, OR WRITE "NONE"}}
This job's budget and type: {{PASTE}}
</inputs>
<instructions>
1. Assess each factor: payment reliability, hiring behavior, budget realism compared with their past spending, and the pattern of freelancer reviews.
2. Identify any patterns in reviews, such as repeated complaints about scope changes, slow payment, or unclear feedback, and quote the relevant text.
3. If the client is new and has no history, say so and explain how to handle a first-time client safely, for example by proposing milestones.
4. Classify the client as Priority, Worth a Bid, Proceed With Caution, or Skip, with a three-sentence justification.
5. Recommend what to emphasize in my proposal for this type of client (for example: reliability, clear milestones, speed, or communication).
</instructions>
<rules>
- Do not treat a missing detail as a negative. Mark it UNKNOWN.
- Base every claim on the data I pasted.
- Do not speculate about the client's personality.
</rules>
<output_format>
Headings in order: Factor Assessment (table: Factor, Evidence, Signal), Review Patterns, Classification and Why, What to Emphasize in My Proposal.
</output_format>
A new client with no history is not automatically risky. It simply means you protect yourself with clear milestones.
Claude Prompts for Writing Upwork Proposals That Get Replies
This is where contracts are won. The proposal and the screening answers are the first thing a client judges you on.
3. Write a Proposal That Opens With the Client’s Problem
Upwork’s guidance on winning proposals says to address the client’s specific needs in the opening lines, include relevant work samples or past results, and keep the cover letter to two or three short paragraphs. This prompt builds every one of those into the draft. Clients also want to see that you actually read the post, so a copy-pasted generic message is the thing to avoid.
<role>
You are a top-rated Upwork freelancer and proposal coach who has written proposals that consistently get replies. You write short, specific, client-focused proposals that sound human.
</role>
<context>
Write a proposal for the job below. The client will see only the first couple of lines in their proposal list, so those lines must make them want to open the rest.
</context>
<inputs>
Full job post: {{PASTE THE FULL JOB POST}}
Client's name, if shown: {{NAME OR "NOT SHOWN"}}
My background and strongest skills for this job: {{PASTE PROFILE SUMMARY}}
My real proof points (results, clients, numbers) relevant to this job: {{PASTE FROM YOUR PROOF FILE}}
A relevant portfolio item I can reference (describe it): {{DESCRIPTION OR "NONE"}}
My availability and earliest start date: {{PASTE}}
My tone: {{FRIENDLY, PROFESSIONAL, DIRECT, OR OTHER}}
Insights from the job decoder (optional): {{PASTE OR WRITE "NONE"}}
</inputs>
<instructions>
1. Identify the client's single biggest problem or goal from the post.
2. Write the first two lines so they show I understand that specific problem and hint at the outcome I will deliver. Do not begin with a self-introduction, my experience, or a generic greeting. Use the client's name if provided.
3. Write a short paragraph with my approach: three concrete steps tied directly to details in the post.
4. Write a short paragraph with one relevant proof point from my list, including a specific number or outcome where I have provided one. Reference the portfolio item if I gave one.
5. Close with one thoughtful question about their project that shows I have thought about it, then a clear next step such as a quick call or sharing a plan.
6. Write two versions: Version A is direct and concise (120 to 160 words), Version B is consultative with slightly more detail (170 to 220 words).
7. Mirror three or four phrases from the post naturally.
</instructions>
<rules>
- Use only the facts and proof I provided. Never invent results, clients, tools, or experience. If a proof point is missing, leave it out.
- Banned phrases: "I hope this finds you well," "I am the perfect fit," "I am writing to apply," "Dear Sir or Madam," "I have X years of experience" as an opener, "I can do this job," "please check my profile."
- No bullet lists inside the proposal. Use short paragraphs.
- No exclamation marks and no emojis.
- Do not mention price unless I included a rate to use.
</rules>
<output_format>
Headings in order: Client's Core Problem, Version A, Version B, What to Attach or Link, Why the Opening Works (two sentences), Verify Before Sending (claims I should double-check).
</output_format>
Read both versions out loud. Keep the one that sounds like you, and add one small, true detail about the client’s project before you send.
4. Answer Screening Questions Without Sounding Generic
Screening questions are a quiet filter. Many freelancers answer them in one line and lose the job there.
<role>
You are an Upwork proposal coach who writes screening answers that are specific, honest, and brief. You know that clients use these answers to shortlist.
</role>
<context>
The client added screening questions to their job post. Write answers that are consistent with my proposal and based only on my real background.
</context>
<inputs>
Job post: {{PASTE THE JOB POST}}
Screening questions: {{PASTE EACH QUESTION}}
My background and proof points: {{PASTE PROFILE AND PROOF FILE}}
My proposal text (so the answers stay consistent): {{PASTE PROPOSAL, OR WRITE "NOT WRITTEN YET"}}
</inputs>
<instructions>
1. Write an answer to each question of 40 to 90 words.
2. Begin every answer with a direct response to the question in its first sentence. Then support it with one specific example from my background.
3. If a question asks for experience I do not have, answer honestly, state the closest related experience I do have, and explain how it applies.
4. If a question asks for a link or sample, tell me exactly which item to attach and write the sentence that introduces it.
5. If a question asks about availability, rate, or timeline, use the details I provided. If I did not provide them, write "YOU MUST ADD:" with what is missing.
6. After the answers, flag any answer where a stronger response needs information I have not given.
</instructions>
<rules>
- Never claim experience, tools, or results that I did not provide.
- Do not repeat the same example in more than one answer unless it is my only relevant one.
- No filler such as "Great question" or "I would be happy to."
</rules>
<output_format>
For each question: the question quoted, then my answer, then a one-line note on any risk or missing detail.
</output_format>
Consistency matters. A client who sees one story in your proposal and another in your screening answers will notice.
Claude Prompts for Building an Upwork Profile and Portfolio That Convert
Your proposal gets the click. Your profile and portfolio decide whether it turns into an interview.
5. Rewrite Your Upwork Profile Title and Overview for Search and Clarity
Clients search by keyword and skim fast, so your title and the first lines of your overview carry the most weight.
<role>
You are an Upwork profile strategist who helps freelancers position themselves for a specific niche so that the right clients find them and understand their value in seconds.
</role>
<context>
Rewrite my Upwork profile title and overview. Use real job-post language from my niche so my profile matches what clients search for and ask for.
</context>
<inputs>
My current title and overview: {{PASTE CURRENT TEXT}}
My niche and the clients I want: {{DESCRIBE NICHE AND IDEAL CLIENT}}
Services I offer: {{LIST SERVICES}}
My real proof (results, clients, numbers, tools, years): {{PASTE PROOF FILE}}
Five job posts in my niche that I would like to win: {{PASTE 3 TO 5 POSTS}}
My process in a few lines: {{DESCRIBE HOW YOU WORK}}
</inputs>
<instructions>
1. Extract the recurring skills, tools, and phrases across the five job posts and rank them by frequency.
2. Write three title options that state what I do and who I do it for, using the highest-ranked terms. Keep each short enough to read fully in search results, and aim for under 70 characters.
3. Write an overview of 180 to 260 words with this structure: a first two lines that state the client problem I solve and the result I deliver, a short section on who I help, a three-step description of my process, two or three real proof points, and a closing line inviting a specific kind of project.
4. Write a ranked list of 12 to 15 skills to include, using the terms from step 1 that my background truly supports.
5. Say whether a specialized profile for a second service would help me, and why.
6. List what is missing from my profile that clients would want to see.
</instructions>
<rules>
- Use only facts I provided. No invented results or credentials.
- No phrases such as "hard-working," "passionate," "results-driven," "detail-oriented," or "team player."
- First person, short paragraphs, plain language.
- Keywords must read naturally, not as a list.
</rules>
<output_format>
Headings in order: Keyword Findings, Title Options (with character counts), Overview, Skills List, Specialized Profile Advice, Gaps to Fill.
</output_format>
Update your profile before you send your next batch of proposals. A strong proposal that lands on a weak profile wastes its own effort.
6. Turn One Past Project Into a Portfolio Item and a Proposal Proof Point
A portfolio item that explains a problem, an action, and a result does more than a screenshot with a title.
<role>
You are a portfolio writer who turns freelance projects into clear, credible case studies that help new clients picture working with the freelancer.
</role>
<context>
Turn the project details below into a portfolio entry for my Upwork profile and a two-sentence proof point I can reuse in proposals.
</context>
<inputs>
Project description: {{PASTE WHAT THE PROJECT WAS}}
Type of client (you may anonymize): {{PASTE, E.G. "A SaaS startup"}}
The problem the client had: {{PASTE}}
What I did, step by step: {{PASTE}}
Results, with numbers where I have them: {{PASTE ACTUAL RESULTS}}
Tools and skills used: {{PASTE}}
Timeline: {{PASTE}}
Anything confidential I must not reveal: {{PASTE, OR WRITE "NONE"}}
</inputs>
<instructions>
1. Write a portfolio title of up to 10 words that states the outcome or the type of work.
2. Write a description of 100 to 150 words in three labeled parts: The Challenge, What I Did, The Result.
3. Write a one-line summary I can use as a caption.
4. Suggest what to show visually (for example: before and after, a dashboard, a sample page) and what to leave out for confidentiality.
5. Write a two-sentence proof point for use in proposals, in first person.
6. If the results are vague or missing, say what additional detail would strengthen the entry and how I might find it.
</instructions>
<rules>
- Use only what I provided. Do not invent numbers, client names, or outcomes.
- Respect the confidentiality notes. Anonymize where needed.
- Plain language, no jargon the client would not use.
</rules>
<output_format>
Headings in order: Portfolio Title, Description, Caption, What to Show and What to Hide, Proposal Proof Point, Missing Details.
</output_format>
Run this on your three strongest projects. Those proof points feed prompts 3 and 4 directly.
Claude Prompts for Pricing, Interviews, and Negotiation
Once a client replies, the work changes. These prompts keep you prepared and keep your rate intact.
7. Price the Job and Structure Milestones Without Undercutting Yourself
Pricing from fear is the fastest way to win a contract you regret. This prompt works from your minimum and shows its math.
<role>
You are a freelance pricing strategist who helps freelancers quote fairly, protect their margins, and structure projects so both sides know what is being delivered and when payment is due.
</role>
<context>
I need to price a job and structure its milestones. Use my minimum rate as a firm floor.
</context>
<inputs>
Job post and any details discussed with the client: {{PASTE}}
My target hourly rate: {{AMOUNT}}
My minimum acceptable hourly rate: {{AMOUNT}}
My honest estimate of hours needed: {{HOURS OR RANGE}}
Client's stated budget: {{AMOUNT OR "NOT STATED"}}
Project type the client wants: {{HOURLY, FIXED-PRICE, OR UNSURE}}
</inputs>
<instructions>
1. Multiply my hours estimate by 1.25 to account for revisions and communication. Show the calculation.
2. Calculate the total price at my target rate and at my minimum rate. Calculate the effective hourly rate of the client's stated budget, if given.
3. Recommend hourly or fixed-price for this job, with reasoning.
4. Write three pricing options with clearly different scopes: Essential, Standard, and Premium. Each must price at or above my minimum rate. List exactly what is and is not included in each.
5. Build a milestone plan of three to five milestones. For each: deliverable, acceptance criteria, estimated duration, and percentage of payment.
6. Define scope boundaries: what counts as a revision, how many revision rounds are included, and what triggers a change in price.
7. Write two sentences presenting the price in a proposal or message without apologizing or over-explaining.
8. If the client's budget is too low to meet my minimum even at the smallest sensible scope, say so plainly and suggest how to respond.
</instructions>
<rules>
- Never recommend a price that falls below my minimum rate.
- Show every calculation.
- Do not invent details about scope. Base everything on what I provided and flag assumptions.
</rules>
<output_format>
Headings in order: Effort and Price Math, Hourly or Fixed, Three Options (table), Milestone Plan (table), Scope Boundaries, How to Present the Price, Budget Verdict.
</output_format>
Milestones protect you as much as the client. They make the payment schedule clear before the work starts.
The JSON Prompt Mastery for Claude collection includes 70+ pre-built structured prompts organized by business workflow, so you run the prompt and get the output without building anything from scratch. If you want ready-made prompts for the rest of your freelance workflow, it is built for exactly that.
8. Prepare for the Client Call or Interview
When a client replies, the next conversation decides the contract. Walk in knowing what they will ask and what you need to learn.
<role>
You are a freelance interview coach who prepares freelancers for client calls. You think like the client and like a seasoned freelancer who protects their time.
</role>
<context>
A client replied to my proposal and wants a call or chat. Prepare me.
</context>
<inputs>
Job post: {{PASTE}}
My proposal: {{PASTE}}
The client's reply: {{PASTE}}
My background and proof file: {{PASTE}}
Call length and format: {{PASTE, OR WRITE "UNKNOWN"}}
</inputs>
<instructions>
1. Predict the eight questions this client is most likely to ask, based on their post and reply.
2. For each, write a 60 to 90 word answer outline using only my real background. Mark with "YOU MUST ADD:" where I need to supply a detail.
3. List the eight most important questions I should ask the client, ranked. Cover goals and success metrics, timeline, budget, decision process, who approves work, what access I will need, past experience with freelancers, and what went wrong before.
4. List the warning signs to listen for during the call, such as vague scope, shifting goals, resistance to milestones, or pressure to work for free.
5. Write a closing script of three sentences that confirms next steps and invites them to start the contract.
6. Write a recap message of no more than 120 words to send after the call, summarizing what we agreed and the next step.
</instructions>
<rules>
- Do not invent experience or numbers.
- Keep answers conversational, not scripted.
- The recap message must contain only points I list as discussed, so include a placeholder line "YOU MUST ADD: what was agreed" where needed.
</rules>
<output_format>
Headings in order: Likely Questions and Answer Outlines, Questions I Should Ask, Warning Signs, Closing Script, Recap Message.
</output_format>
The recap message often gets overlooked. It turns a pleasant conversation into a written record the client can approve.
9. Respond to Rate Objections Without Caving or Sounding Defensive
Every freelancer hears “your price is too high” sooner or later. This prompt gives you three professional ways to answer.
<role>
You are a freelance negotiation coach who helps freelancers hold their rates with confidence and flexibility. You never recommend guilt, threats, or defensiveness.
</role>
<context>
A client has pushed back on my price or scope. Help me reply in a way that protects my minimum rate and keeps the door open.
</context>
<inputs>
The client's message: {{PASTE THE EXACT MESSAGE}}
My quoted price and what it covers: {{PASTE}}
My minimum acceptable price: {{AMOUNT}}
How much I want this contract (Low, Medium, High) and why: {{PASTE}}
What I could reduce or remove from the scope: {{PASTE OPTIONS}}
</inputs>
<instructions>
1. Identify the objection type: price, scope, trust, timeline, or a request for free work.
2. Write three reply options of no more than 100 words each:
- Option 1, Hold the Price: restate the value tied to the client's goal and keep the price.
- Option 2, Adjust the Scope: propose a reduced scope with a clear lower price that stays at or above my minimum, and show what changes.
- Option 3, Step Back Politely: close warmly and leave the door open without discounting.
3. Tell me which option fits best given how much I want the contract, and explain in two sentences.
4. List one thing I should not say in this situation.
</instructions>
<rules>
- Never write a price below my minimum.
- Do not apologize for my price.
- Do not use guilt, pressure, or threats.
- Keep all communication in a form suitable for Upwork messages.
</rules>
<output_format>
Headings in order: Objection Type, Option 1, Option 2, Option 3, Best Fit and Why, What Not to Say.
</output_format>
Option 2 wins more often than people expect. Clients with a budget limit usually want a smaller version of the work, not a lower-quality one.
Claude Prompts for Follow-Ups and Repeat Work
The last prompt covers the messages most freelancers skip, and they often matter most.
10. Write the Follow-Up Message for Every Stage of a Contract
Silence after a proposal, a pleasant call that goes quiet, and a finished project with no review are all follow-up problems.
<role>
You are a freelance communication specialist who writes short, warm, professional follow-up messages that get responses without sounding pushy.
</role>
<context>
I need a follow-up message for a specific stage of an Upwork contract. Write the message for the stage I choose, plus one backup version.
</context>
<inputs>
Stage (choose one and delete the others): (1) No reply to my proposal; (2) After a call or interview, no decision yet; (3) Project delivered, waiting for approval and review; (4) Project finished successfully, seeking more work from the client
Job and client details: {{PASTE JOB POST AND CLIENT NAME}}
What happened so far (dates, messages, anything promised): {{PASTE}}
My relevant results or help I can offer next: {{PASTE}}
</inputs>
<instructions>
Write the message according to the stage:
- Stage 1: Two to three sentences, no more than 60 words. Add one new piece of value, such as a short idea or a relevant insight for their project, instead of just asking if they saw my proposal.
- Stage 2: No more than 90 words. Recap the main point we agreed on, restate the next step, and offer to answer any final questions.
- Stage 3: No more than 110 words. Confirm what was delivered, invite specific feedback, and politely ask for a review once they are satisfied. Do not pressure for a particular rating.
- Stage 4: No more than 120 words. Thank them for a specific part of the project, suggest one logical next piece of work based on what we learned, and make it easy to say yes or no.
Then write one backup version with a different angle.
</instructions>
<rules>
- Use only facts I provided. Do not invent shared history or results.
- No guilt, pressure, or passive-aggressive phrases such as "just checking in again" or "as I mentioned."
- Keep the tone warm, direct, and professional.
- Do not suggest moving communication or payment off Upwork.
</rules>
<output_format>
Headings in order: Message, Backup Version, Best Time to Send (one sentence).
</output_format>
Stage 4 is the most valuable. A client who already trusts you is far easier to win again than a new one.
Mistakes That Cost Freelancers Upwork Contracts
Even strong prompts fail when they are used badly. These are the common slips.
Sending the same proposal to every job. Clients can tell. Use prompt 3 each time with the full post pasted in.
Opening with yourself. A proposal that starts with your years of experience gives the client no reason to read on. Start with their problem.
Claiming results you cannot prove. Clients can ask for details, and an exaggerated claim collapses the moment they do.
Pricing below your floor to win. A low price attracts clients who will keep negotiating. Use prompt 7 and hold your minimum.
Ignoring red flags. Unpaid tests, vague scope, and requests to leave the platform are warning signs. Trust prompts 1 and 2 when they say skip.
How to Combine These Claude Prompts Into a Daily Upwork Routine
You do not need all ten for every job. A simple rhythm covers most of the work.
Once, build your foundation: run prompt 6 on your best projects and prompt 5 on your profile. Then, for each job you consider, run prompt 1, and run prompt 2 if it passes.
For jobs worth a bid, use prompts 3 and 4 together. When a client replies, use prompt 8 before the call, prompt 7 for pricing, and prompt 9 if they push back. Keep prompt 10 handy for every stage after you send a proposal.
Save every output in a single document with the job title as a heading. Over time, you build a library of proposals, answers, and replies that you can adapt.
Better Proposals Start With Better Inputs
All ten prompts follow the same pattern: real facts from you, a clear task, firm rules, and a fixed output format. That structure is why Claude writes something specific enough to send, instead of something polished and forgettable.
Pick the next job you were going to bid on and run prompt 1. Whatever it says, you will either save a Connect or write a stronger proposal.
When you are ready to apply the same approach to the rest of your freelance business, JSON Prompt Mastery for Claude has structured prompts organized by workflow. Start with the proposal prompt on your next real job post, and compare it with the proposal you would have sent.