How to Write a Freelance Proposal That Wins IT Projects

The short answer

A client reads dozens of proposals and spends a few seconds on each. They pick the one where the first lines say: this person understood my problem and knows how to solve it. A structure that works:

1. The client's problem in your own words.
2. One relevant example.
3. A short plan.
4. Two or three clarifying questions.
5. Price and timeline with an explanation.

1. The first line is about the client, not you

The opening of a proposal is often visible in a preview before it is opened. "Hello, my name is…" or "I am an experienced developer" waste that space.

Restate the task so the client recognises their situation:

You need a Telegram bot for booking salon appointments that shows each stylist's free slots and sends a reminder the day before the visit.

If the job post has a detail that is easy to miss, mention it. It is the best sign you read the whole thing.

2. One relevant example

Not a list of every project, but one that is as close to the task as possible. Describe it in one or two lines: what was needed and what you did. Add a link to the work, a repository or a portfolio item on the platform.

If you have no similar commercial project, a study or personal project works if it honestly solves a similar problem. Do not present a study project as client work.

3. A concrete plan

Three to five steps show you are already thinking about the job, not just applying to everything:

• Agree on the booking flow and the list of services.
• Build the bot with stylist, date and time selection.
• Add booking storage and reminders.
• Test on your data, hand over access and instructions.

The plan is not a detailed specification. Its job is to show understanding and sequence.

4. Clarifying questions

Good questions demonstrate experience better than describing it. They target what actually affects the work:

• Where is the stylists' schedule kept today?
• Do you need online payment at booking?
• Who will add new stylists and services?

Questions also give the client a reason to reply, and a reply starts a conversation.

5. How to present the price

• Tie the price to scope. "This amount covers steps 1-4 of the plan. Online payment is estimated separately."
• Offer milestones for larger jobs: a first paid milestone lowers risk for both sides.
• State the timeline and what it depends on.
• Do not underprice to win. A price that is too low raises suspicion and leads to working at a loss.

If the description is too thin for an accurate estimate, say so: give a range now and an exact figure after the questions are answered.

Proposal template

[Client's problem in your words, 1-2 sentences]

I recently built something similar: [project, 1 line] — [link].

How I would approach it:
1. ...
2. ...
3. ...

To estimate more precisely, could you clarify:
- ...
- ...

Price: [amount] for steps 1-3, timeline [N] days.

The template is a skeleton, not text to paste. Clients spot a proposal sent unchanged to twenty jobs immediately.

Follow-up

If the client opened your proposal but did not reply, after a few days you can send one short message that adds value: an extra idea, an answer to a likely question, a note on timing. Do not write "Did you see my proposal?" and do not send a series of reminders.

Mistakes that get proposals ignored

• Opening with a story about yourself.
• Pasting the same text into every job.
• Writing a long wall of text with no structure.
• Listing every technology you know.
• Ignoring direct questions in the job post.
• Promising "fast and high quality" with no specifics.
• Applying to jobs that do not match your skills.