AI Prompts for Freelance Proposals

Most freelance proposals fail before anyone reads past the first sentence. Not because the work is weak. Because the language is generic, the framing is wrong, and nothing in the document makes the client feel understood.

AI changes the speed at which you produce proposals. It does not automatically change their quality. A generic prompt produces generic output. Specific context, fed into the right prompt structure, produces a proposal that reads like you did your homework, understand the client’s situation, and know exactly what they need.

This is a working prompt library for every stage of proposal creation: research, section drafting, proposal types, review, and performance analysis. Use it as a system, not a grab-bag. Start with the context setup prompt every time. Everything else builds on it.

Why Proposals Fail, and What AI Changes

Three patterns kill most freelance proposals before the client even considers price.

The first is generic language. Phrases like “I have extensive experience” and “I’m passionate about delivering quality work” appear in thousands of proposals every day. They signal nothing. Clients read them as noise and move on.

The second is a features-first structure. Listing what you do before establishing that you understand what the client needs is backwards. Clients are not buying your process. They are buying a solved problem. When a proposal leads with methodology instead of problem understanding, it reads like a brochure, not a response.

The third is a vague investment section. Unclear pricing, unexplained structures, and missing payment terms create friction at the exact moment a client is deciding whether to move forward. From what Ruul sees across hundreds of thousands of freelance transactions, the investment section is where proposals stall most often: not because the price is too high, but because the structure is unclear.

AI addresses all three, but only if you use it correctly. AI can generate client-specific language faster than you can write it. It can structure your proposal around the problem before the solution. It can write a confident, clear investment section with the right framing. What it cannot do is supply the context you have not given it.

The prompts in this library are designed to extract specific, client-relevant output. They will not work without the information you bring to them.

The Context Setup Prompt: Complete This Before Any Proposal Section

This is the most important prompt in the library. Run it first. Every prompt that follows assumes this context exists and will produce generic output without it.

Context Setup Prompt:

I’m preparing a proposal for the following client and project. Use this context for all subsequent proposal section prompts.

Client: [company name, size, industry, what they do] Their stated need: [what they described wanting] Their underlying problem: [what you believe they actually need to solve] Their likely decision criteria: [what matters most to them: speed, quality, cost, specific expertise] My relevant experience: [your most relevant work and outcomes achieved] My proposed approach: [brief description of how you’d tackle this] Project scope: [deliverables, timeline, approximate investment] Competition: [are they likely getting other proposals, and from whom]

Usage note: Paste this into your AI session at the start. Every prompt in this library references this context. The more specific you are here, the more useful everything else becomes. If you find yourself writing “[company name]” without filling it in, stop. That is the problem this prompt is designed to prevent.

The underlying problem field is where most freelancers underinvest. A client who says they need a new website may actually need a higher conversion rate. A client who says they need copy may actually need a positioning fix. Fill this field with your genuine read of what is going on. AI can then frame the proposal around the real issue, not just the stated one.

Prompt Set 1: Proposal Research and Preparation

Before you write a single section, understand who you are writing for. These prompts help you sharpen your read of the client, clarify your differentiation, and choose the right structural approach.

Client Intelligence Gathering

Prompt:

Based on what I know about my client [paste context setup], help me identify: (1) the business problem behind their stated need, (2) potential unstated concerns they might have about this project, (3) what a successful outcome looks like from their perspective, (4) the objections I’m most likely to face in this proposal. Use this to sharpen my proposal’s problem framing.

Usage note: Run this before drafting any section. The answers will shape your opening, your approach, and your investment framing.

Competitive Differentiation

Prompt:

I’m competing for [project description] against other [freelancers / agencies / in-house option]. My relevant differentiators are: [describe your specific advantages]. Help me articulate 2–3 specific reasons why I’m the right choice for this particular client, framed as client benefits rather than my credentials. Avoid generic claims like “attention to detail” or “great communication.”

Usage note: Force the AI to stay specific. If it produces claims that could apply to any freelancer, ask it to try again with more concrete language tied to the client’s situation.

Proposal Approach Selection

Prompt:

I’m deciding how to structure my proposal for [client and project description]. Options I’m considering: (1) [approach A], (2) [approach B], (3) [approach C]. Based on what I know about this client’s priorities and the nature of the project, which approach is most likely to be persuasive? What are the risks of each?

Prompt Set 2: Proposal Section Drafting

These prompts produce individual sections. Use them after you have completed the context setup prompt. Each prompt references that context, so paste the relevant details in where indicated.

Problem Statement / Executive Summary

The opening of your proposal is the only part most clients read fully. It needs to demonstrate that you understand their situation, frame the problem in terms of business impact, and create the impression that you are the right person precisely because you see the real issue.

Prompt:

Write the opening section of a freelance proposal for [paste context setup]. This section should: demonstrate that I understand their situation better than they may have articulated it themselves, frame the problem in terms of business impact (not just a description of what they described), and create a sense that I’m the right person because I understand the real issue. Under 150 words. First person singular.

Usage note: Read the output carefully. If it describes the client’s stated need rather than their underlying problem, your context setup may need more detail in the “underlying problem” field.

Proposed Approach / Methodology

Prompt:

Write the approach section of my proposal for [paste context setup]. The section should: describe how I would tackle this specific project, explain why this approach is right for their situation (not just a generic methodology), demonstrate expertise without jargon, and build confidence that I’ve thought through the project carefully. Under 200 words.

Deliverables and Scope

Vague language creates room for scope disputes later. Specific language closes it.

Prompt:

Write a deliverables section for my proposal for [paste context setup]. List each deliverable clearly, include enough specificity that the client understands what they’ll receive, and avoid vagueness that could cause scope disputes later. If there are items explicitly not included, note them briefly. Format as a clear list with brief descriptions.

Timeline Section

Prompt:

Write a timeline section for my proposal for [paste context setup]. Project timeline: [describe phases and dates]. Format as a clear phase-by-phase timeline that: makes the progression logical, identifies any client dependencies (what I need from them and when), and builds confidence that the timeline is realistic. Include any relevant caveats about what could affect the timeline.

Investment Section

This section is where proposals routinely stall. Unclear pricing, missing payment terms, and apologetic framing signal that you are not confident in your own value. State the investment clearly. Frame the value briefly. Move on.

Prompt:

Write the investment/pricing section of my proposal for [paste context setup]. My price: [amount and structure]. This section should: present the investment clearly without apology, provide brief framing of value (what they’re getting for this investment), break down the structure if relevant (milestone / phases / components), and include payment terms. Professional and confident. Under 150 words.

Usage note: If the output softens your price or adds unnecessary hedging, tell the AI to remove all qualifiers and restate the investment directly.

About Me / Credentials Section

This is a relevance statement, not a biography. Clients do not need your career history. They need to know why you are the right person for this specific project.

Prompt:

Write a brief “about me” section for my proposal for [paste context setup]. Focus on: my most relevant experience for this specific project, one or two specific outcomes I’ve achieved for similar clients (not a CV list), and why this particular project is a strong fit for my expertise. Under 100 words. First person. Not a biography a relevance statement.

Call to Action / Next Steps

A proposal that ends with “let me know if you have any questions” gives the client permission to drift. A proposal that ends with a specific next step gives the client something to do.

Prompt:

Write a closing and next steps section for my proposal for [paste context setup]. This section should: summarize the key points confidently in one sentence, propose a specific next step (discovery call / kickoff date / questions to answer), create appropriate urgency without pressure, and leave the client feeling positive about moving forward. Under 75 words.

Prompt Set 3: Proposal Types

Not every proposal follows the same structure. A retainer pitch is a different conversation than a one-off project. An unsolicited pitch requires a different opening than a solicited one. These prompts adapt the standard structure for each context.

Retainer Proposal

Retainer proposals fail when they look like project proposals with a monthly price. The key difference: a retainer is a relationship, not a transaction. The client needs to understand what ongoing looks like in practice.

Prompt:

Write a retainer proposal for [paste context setup]. This is an ongoing engagement, not a one-off project. The proposal should: frame the value of ongoing versus project-based relationship, describe what a monthly engagement looks like in practice, explain how scope will be managed in an ongoing arrangement, and position the retainer as beneficial to the client (consistency, priority access, cost efficiency). Adjust the standard proposal structure for this ongoing context.

Usage note: For recurring work, platforms like Ruul’s subscription billing let you invoice retainer clients automatically each cycle; worth noting in your payment terms section as a frictionless collection method.

Unsolicited Proposal

You are initiating. The client has not asked. The opening cannot be a pitch. It needs to be an observation, a specific one, that creates curiosity.

Prompt:

Write an unsolicited proposal for [paste context setup]. This client hasn’t asked for a proposal I’m initiating. The opening must: immediately establish why I’m reaching out (a specific observation about their business or situation), demonstrate that I’ve done my research, and create curiosity rather than immediately pitching. The overall tone: consultative not salesy. Under 300 words for the opening; then use standard proposal section prompts for the body.

RFP Response

Formal RFPs have explicit requirements. Your job is to meet them in priority order, not in the order that makes you look best.

Prompt:

I’m responding to an RFP with the following requirements: [paste relevant RFP requirements]. My constraints are [budget / timeline / team]. Help me: (1) identify the evaluation criteria the RFP is implicitly prioritizing, (2) structure my response to address their stated requirements in their order of priority, (3) identify where I should differentiate from standard RFP-compliant responses. Note: I’ll use standard section prompts for the actual content.

Prompt Set 4: Proposal Review and Improvement

Once a draft exists, AI shifts from creator to critic. This is where some of the highest-value prompts in this library live. A proposal that reads well to you may read as generic to a client comparing four options.

Proposal Quality Review

Prompt:

Review the following proposal I’ve written for [brief client description]: [paste proposal]. Evaluate it on: (1) how specifically it addresses this client’s situation versus being generic, (2) whether it leads with problem/value or features/deliverables, (3) clarity and confidence of the investment section, (4) strength of the call to action, (5) anything a competing proposal might do better. Be specific about improvements, not just general feedback.

Making AI-Generated Sections More Personal

This is the highest-risk problem in AI proposal writing. AI produces competent, professional language. It also produces language that could have been written for any client. This prompt exists specifically to fix that.

Prompt:

The following proposal section was AI-generated and sounds somewhat generic: [paste section]. Here is specific context that should make it more personalized: [describe unique aspects of this client, project, or your relationship]. Rewrite the section to incorporate this specific context and sound less like a template.

Usage note: This prompt is most useful when you notice the output could have been written for any client in any industry. The fix is always more specific context, not better phrasing.

Proposal from Client Perspective

Prompt:

Read the following proposal as a [describe client startup founder / procurement manager / marketing director] who is evaluating multiple proposals. What would your reaction be? What would make you more or less likely to move forward? What questions would you have? What feels generic or unconvincing? Be honest. Proposal: [paste proposal].

Prompt Set 5: Proposal Performance Analysis

Proposals are not just documents. They are data. Each win and each loss tells you something, if you know how to read it.

A note on records: tracking proposal outcomes over time also matters for tax season. If you store sent proposals, win/loss notes, and transaction summaries in one place, you will have the documentation you need without scrambling at year end. Ruul’s tax readiness tools centralise this automatically for every payment processed through the platform.

Win/Loss Analysis

Prompt:

I recently [won / lost] a proposal for [project description]. Here is what I know about the outcome: [describe price was too high / they chose a competitor / they said X / I won and they mentioned Y]. Help me identify: (1) what likely contributed to this outcome, (2) what I could do differently in the next similar proposal, (3) any patterns I should investigate across multiple proposals.

Proposal Template Optimization

Prompt:

I write proposals regularly for [describe your typical project type and client]. Review the following proposal template I currently use: [paste template]. Identify: (1) sections that are likely too generic across different clients, (2) sections where client-specific information should always be inserted, (3) anything structurally weak that might cost me proposals. Suggest specific improvements.

A Note on What AI Cannot Do

AI cannot observe the client meeting you had last week. It cannot know that the client mentioned they had a bad experience with their last freelancer. It cannot pick up that the decision-maker cares more about timeline than budget, even though the RFP says otherwise.

Your judgment supplies that. AI produces the language.

The most effective use of these prompts is not to hand over the writing. It is to hand over the drafting so you can focus on what only you can provide: the specific, accurate read of this client, this project, and this moment. Generic prompts produce generic proposals. Your context turns them into something a client can actually recognize themselves in.

Better Proposals Win More Work. Better Payment Infrastructure Collects It.

Once a proposal converts, the next friction point is getting paid. If you work with international clients, that friction can be significant: cross-border invoicing, currency conversion, and payment delays all eat into the value of the work you just won.

Ruul handles invoicing and payment collection automatically, in 190 countries, so the work your proposals win gets paid without the administrative overhead. No company required to invoice globally. Payouts within one business day of client payment, directly to your preferred method, including USDC via crypto payout if that suits how you work. If you want to understand how invoicing works without a registered entity, Ruul’s Agent of Record model is built for exactly this.

The proposal wins the work. The payment infrastructure makes sure the work actually pays.

Get started on Ruul to collect your next proposal win without the admin friction.