Now, once you’ve hit the perfect job that you want to make a proposal for, and then use one of the following strategies to make your proposal:
#1 – Exploit missing information in the job description.
Nine times out of ten, the job description is incomplete. So start your proposal by introducing yourself and making a query, asking for details about the incomplete bit(s). This shows that you actually read the proposal, and keeps your proposal interactive, so you are very likely to get at least a matter-of-fact reply, which you can then turn into a conversation and finally close the deal. Feel free to add any other remarks you wish to make about the job right in your proposal.
#2 – A Clever Alternative
Sometimes, and this happens often in projects involving code, the job description proposes a solution that is not ideal, so I write up a quick proposal proposing an alternative that is better/faster/cheaper. This doesn’t happen too often, but when it does, it works incredibly well!
#3 – A proposal with samples
This works especially well for writing jobs, or “remove the background in this picture”-style jobs, you can start your proposal with a brief introduction and then indicating that you are a perfect fit for the job by giving very closely related samples. Whenever the ToS allows it, you might even do a quick “mock up” (for a design job) or write a paragraph or two demonstrating how you would tackle the particular writing job at hand. This small effort goes a long way in catching the attention of the client, and if your style is appealing, then the job is as good as yours!
At all costs, avoid doing a generic proposal that just introduces you and says that you are the best person for the job, without any explanation of why, and without any reference to the job at hand. An impersonal proposal is as good as a non-existent one.
Don’t be afraid of providing your own thoughts and ideas about the project at hand. Remember that anything in your proposal that demonstrates that you have read the job description with some attention and that you actually care for the project is a going to work wonders.
Read the job description VERY carefully and watch out for instructions in them – if there are any, then follow them! For instance, many job descriptions say the following:
Neglect this instruction and your proposal may get completely ignored!
For technical work, if you get questions, provide prompt replies, and don’t be afraid of spending time and being detailed and through. Pre-sale support gives further evidence that you know what you are talking about, and that you care enough. For creative work, again, don’t be afraid of pursuing discussions if they are initiated. The conversational proposals have worked the best for me – and make sure you clarify everything upfront – the scope of the project, the timeline, and the pricing, and leave no room for confusion going forward!
Most importantly, don’t be afraid of failure! I’ve had, on occasion, proposals turned down after long conversations and even interviews over phone, and almost every time it is for a reason beyond my control. There are good proposals that never get looked at or are rejected outright. It is perfectly normal to have to make multiple proposals before you can land a client. Some websites even show the acceptance rates for freelancers – look them up if you need concrete evidence 🙂
So – persistence is going to be key. Don’t expect your very first proposal to come through – and never take a rejection personally. If you ever get an explicit and reasonable reason for rejection from a prospective client, then take note of it and make that a learning experience.
Also, you never know when your efforts may pay off even if you lose the particular job that you were making the proposal for. I’ve had people who couldn’t take me up for whatever reason, but who either referred me to other people or have simply returned later on, just because the pre-sale experience made enough of an impression!
Author Bio:- Charles West is a professional content writer and blogger since last 2 years. I have writing expertise in technology and certification topics specially. I love to share that recently I passed my C90-03Aexam from VMware. Thanks for reading.