A winning proposal does not guarantee a project. Its job is to help the client decide whether you understand the problem and can deliver the next step. The strongest proposals are specific, short, and supported by relevant evidence.
Read before writing
Underline the requested outcome, deliverables, constraints, deadline, and any phrase that reveals the client’s priority. If the brief is too vague to price safely, ask one clarifying question instead of pretending you understand it.
A five-part proposal
- Relevant opening: mention the client’s actual problem.
- Approach: explain the first two or three steps you would take.
- Proof: link one closely related sample and describe your contribution.
- Scope: state deliverables, timeline, revisions, and assumptions.
- Question: ask something that helps move the brief forward.
Example
“You need five product images that remain readable on mobile. I would first create one layout, test it at the smallest target size, then apply the approved style to the remaining four images. The attached sample shows a similar product-card layout; the work is labelled as a practice project. Would you provide the original product photos and brand colours?”
Track results instead of guessing
Record applications, views, replies, interviews, and wins. Views without replies usually indicate a weak opening or sample. Replies without interviews may indicate unclear scope. Interviews without wins may indicate pricing, communication, or a mismatch in expectations. Change one variable at a time so the results teach you something.
Safety rules
Never pay to apply for a job, accept suspicious overpayments, or move communication off a platform when its rules prohibit it. Confirm the scope and payment terms before beginning. No proposal can remove every risk, so use a small milestone for an unfamiliar client.
Qualify before you write
A proposal is worth writing only when the job matches your service, available time, evidence, and acceptable payment terms. Check whether the brief identifies a real outcome, whether the deadline is possible, and whether the client has provided enough information to estimate the work. Skipping poor-fit jobs saves application credits and protects your future reviews.
State assumptions clearly
If your estimate assumes that the client supplies final copy, images, access, or brand guidelines, write that assumption in the proposal. Explain what happens if one of those items is missing. This prevents a low quote from becoming an unlimited promise and gives the client a chance to correct the brief before hiring.
Follow up with value
If a client replies, answer the question directly and keep the conversation organised. Send a short recap after a call and confirm the next action. Do not send repeated messages, external files, or personal contact details against platform rules. The proposal opens the conversation; reliable project communication wins the work.
Review your conversion data
Track applications, views, replies, interviews, offers, and completed projects. Read ten applications together and identify one change to test. This turns rejection into a feedback loop without pretending that any proposal format guarantees an outcome.
Show that you read the brief
Quote or paraphrase one specific requirement and connect it to your proposed first step. Mention a relevant sample and your actual role in that work. If the sample is a practice project, say so. A client does not need a complete biography; they need enough evidence to judge whether you understand the task.
Make scope visible
State what you will deliver, what you need from the client, how many review rounds are included, and what could change the estimate. For a website, that might mean one page and responsive layout rather than an undefined “full site.” For writing, it might mean a word range, source responsibility, and approval process.
Follow up without pressure
If a client responds, answer the direct question and confirm the next step. After an interview, send a concise summary. If there is no response, follow up once with useful information and then close the opportunity. Never spam, misrepresent experience, or move payment outside the platform against its rules.
Review proposal outcomes in groups. Good proposals reduce uncertainty, but they cannot guarantee that a client will choose you.
Qualify the job before applying
Check the outcome, scope, deadline, budget, client history, proposal volume, payment status, and your own available hours. A high budget does not make a vague project safe. If essential information is missing, ask a focused question or skip the job. An application credit is not something you need to recover at any cost.
Show one relevant proof
Describe one similar problem you solved or one labelled practice sample. Explain your role and the first milestone. Avoid a long biography and a list of every tool you have seen. If your experience is not exact, say what transfers and what you would verify before starting.
Turn interest into a clear agreement
When the client replies, answer directly, summarise decisions, and confirm what each person does next. State deliverables, assumptions, revisions, payment points, and change handling before work begins. Follow platform communication and payment rules. A proposal can create a conversation, but only a clear fit and reliable delivery can create a healthy project.
