$ cat prompt.txt — Web Development

Freelance Web Project Proposal — Scope, Price & Close a $5k+ Build

A proposal that scopes the build, frames the price as ROI, and closes — without scope creep or free revisions.

20–40 min intermediate Claude Opus, GPT-5#freelance#web-dev#proposal

intro.md

A web project proposal does two jobs: it closes the client AND it protects you from scope creep and endless free revisions. Most freelancers send a price and a vibe. This prompt writes a proposal that scopes the build precisely, frames the price against business ROI (not hours), and sets the boundaries that keep the project profitable.

$ cat prompt.txt | pbcopy

The prompt — copy & paste

prompt.txt

You are a freelance web developer who closes $5k-$25k projects with a 40%+ proposal win rate. Write a proposal for the project below that closes AND protects me from scope creep.

INPUTS:
- Client's business (what they do, who they serve): {{client_business}}
- Project brief (what they asked for): {{project_brief}}
- My rate or the project budget: {{your_rate_or_budget}}
- Timeline: {{timeline}}

WRITE THE PROPOSAL:

1. THE PROBLEM (reframe in business terms)
2-3 sentences proving I understood their actual goal — tie the website to their business outcome (more leads, higher conversion, credibility), not just "a new site".

2. PROPOSED SOLUTION
What I'll build, in the client's language. The approach + the stack (briefly, in benefit terms — "fast, mobile-first, easy for you to update").

3. SCOPE (the protection layer — be specific)
- IN SCOPE: an explicit bulleted list (exact pages, features, integrations, # of revisions)
- OUT OF SCOPE: an explicit list of what's NOT included (this single section prevents 80% of scope-creep disputes)
- Assumptions (client provides copy/images by X, etc.)

4. DELIVERABLES + MILESTONES
Phase 1 / 2 / 3 with what the client sees at each, tied to {{timeline}}.

5. INVESTMENT (not "cost")
- The price ({{your_rate_or_budget}}), framed against ROI ("a single new client from this site pays for it")
- Payment structure: deposit + milestones (never 100% on completion)
- What happens for out-of-scope requests (hourly rate for additions)

6. WHY ME
2-3 sentences of relevant proof (similar projects, results). Placeholder if needed.

7. NEXT STEPS + CTA
A clear, low-friction close: "Reply 'approved' and I'll send the deposit invoice + we start [date]." A specific date, not "let me know".

RULES:
- Confident, consultative, not desperate.
- The OUT OF SCOPE + payment-structure sections are non-negotiable — they protect the project's profitability.
- Total: scannable, not a wall of text. The client should be able to skim it and say yes.

Also: 3 likely client objections + how to respond.

$ variables_to_fill_in

$ man playbook

Step-by-step playbook

How to actually use this prompt for the best results.

01
Reframe the brief into a business outcome
Clients don't want 'a website' — they want more leads/sales/credibility. The opening must prove you understood the business goal, not just the feature list. That's what separates you from the spray-and-pray bidders.
02
Make the OUT OF SCOPE section explicit
This is the most important section and the one freelancers skip. Listing what's NOT included (extra pages, ongoing maintenance, copywriting) prevents the 'oh, I assumed that was included' disputes that kill project margins.
03
Always structure payment as deposit + milestones
Never 100%-on-completion. A deposit (commitment) + milestone payments protects your cash flow and filters non-serious clients. The prompt builds this in — keep it.
04
Close with a specific next step + date
End with 'reply approved and we start [date]', not 'let me know your thoughts'. A concrete next action with a date converts far more proposals than an open-ended close.

$ man tips

Pro tips for better output

›Price by project value, not hours — AI lets you deliver in 1/3 the time, so hourly billing punishes your own efficiency. Charge for the outcome.
›Attach a 60-second Loom walking through the proposal for projects over $3k — it 2-3×'s close rate by adding the human + demonstrating expertise.
›Bill out-of-scope additions at a stated hourly rate from the start — it makes scope creep a revenue stream instead of a margin leak.

$ echo $YIELD

What you'll get

output.md

A complete proposal (problem reframe, solution, in/out scope, milestones, ROI-framed pricing with payment structure, why-me, and a dated CTA) plus 3 objection responses.

$ man faq

FAQ

How do I stop clients from endless 'small' change requests?

The explicit OUT OF SCOPE list + a stated number of revision rounds + an hourly rate for additions. When a client asks for something outside scope, you reference the proposal and quote the hourly — it becomes billable, not a free margin leak.

Should I show my hourly rate or a project price?

Project price. Hourly billing penalizes you for being fast (and AI makes you fast). Price the outcome — a marketing site that brings the client one new customer pays for itself, and that's the frame that closes.

$ ls /prompts/web-development