In short
- Open with their problem, not your introduction.
- Show two relevant examples, not your best five.
- Ask the question the brief left open.
- Break the price into parts and say what each assumes.
A client with fifteen proposals is not reading them, they are sorting them. The first two lines decide which pile yours lands in, and almost every proposal spends those two lines on the author. The fix is not a better introduction; it is not having one.
What the client is reading for
Underneath the polite language, they are checking four things: did this person read the brief, have they done something like it, do they understand what makes it hard, and can I work with them. Everything in a proposal should serve one of those.
A structure that fits on one screen
- 1Their problem, in your words. One or two lines showing you understood what they are trying to achieve.
- 2How you would approach it. The shape of the work, not a lecture. Three or four lines.
- 3Relevant proof. Two examples close to their situation, with your part in each made clear.
- 4The question. The thing the brief left open that would change your estimate.
- 5Price and timing. Broken into parts, with what each assumes.
- 6One next step. What happens if they reply.
Six paragraphs. If it runs longer, it is usually a template with the client's name dropped in, and that reads exactly as it sounds.
Openings
Weak
Hi, I am a passionate full-stack developer with 8 years of experience and a proven track record delivering high-quality solutions.
Better
You have final Figma designs and a launch at the end of October, so the risk here is the CRM connection rather than the build. I have wired HubSpot forms into three Next.js sites, and that part usually takes a day once we have API access.
The second version proves it read the brief in its first sentence, names the actual risk, and shows relevant experience without a paragraph about the author. It also tells the client something they did not know, which is the fastest way to earn the rest of the read.
Ask one real question
Every brief has a gap. Finding it is the strongest signal you can send, because it shows you have already started thinking about the work. Ask about the thing that would actually change your estimate: which system it connects to, who approves, whether the content exists, what happens to the old data.
One question, not five. A list of questions reads like a form, and it moves the work of replying onto them.
Price so it can be discussed
A single number can only be accepted or refused. A breakdown can be negotiated, trimmed or expanded, and it shows you thought about the parts instead of picking a figure.
| Stage | Includes | Price |
|---|---|---|
| Build, pages 1 to 6 | Designs implemented, responsive, two revision rounds | $X |
| CRM connection | Form wired to HubSpot, test submissions verified | $Y |
| Launch | Cross-browser pass, deploy, access handover | $Z |
Say what the price assumes, in one line: designs final, content supplied, access on day one. That sentence is what protects you later when one of those turns out not to be true. How to price freelance work covers setting the numbers themselves.
What to leave out
- Your life story, your degree, and how passionate you are.
- A portfolio link with no explanation of which piece is relevant.
- Promises of unlimited revisions, which price the worst client into every job.
- Guarantees about results you do not control.
- Anything you would have sent to a different job unchanged.
Applying without wasting your budget
On Open Lance a proposal costs bids from your balance. The number depends on the type of job rather than its budget, so a large fixed-price job costs the same to apply for as a small one, and nothing can be bought to push a proposal above yours. Current costs are on the pricing page, and finding work and bids explains where bids come from.
The arithmetic follows: applying to everything is expensive, applying carefully is not. Ten considered proposals beat fifty copies of the same one, and cost less to send.
After you send it
If a client shortlists you or opens a conversation, they are interested. Reply with the same specificity you opened with, and do not reprice the job in the chat before you understand what changed. If you hear nothing, one short follow-up after a few days is reasonable, and then leave it.
How long should a proposal be?
About one screen. Long enough to prove you read the brief and can do the work, short enough that the client finishes it. Six short paragraphs is a good target.
Should I include a price if the client did not give a budget?
Yes, with your assumptions written down. A proposal without a number leaves the client no way to compare you, and the assumptions give you room to revise it once you know more.
Do templates work?
A structure you reuse works well. A body of text you reuse does not, and clients recognise it immediately. Keep the skeleton, write the first paragraph and the question fresh every time.
How many jobs should I apply to?
Fewer than you think, chosen for fit. Since applying costs bids, the return comes from being one of the three proposals that clearly matched, not one of the thirty that arrived.