How To Write A Really Bad Web Development Proposal

As a freelance Web Developer, you have one purpose in life – make more money by developing kick-ass websites in the fastest time possible….;)

Crucial to this process is how well you write the Web Development Proposal.  Why you ask?  Because without a well-presented and solid proposal, the client won’t be impressed, they won’t be swayed and they most likely won’t give you the job.  No job, no money, no good.

So how to write a proposal that screams "pick me"?  Firstly, it needs to be compelling and easily understood, flow well and not overwhelm the client with superfluous information.  It must also provide a project overview, address the client’s needs, offer practical solutions, list project benefits, detail the project lifecycle and timelines, supply cost breakdowns and so on. 

Get these aspects and features wrong and you might as well kiss your chances of winning the bid goodbye.  Get them right and, well, it’s champagne and kisses all round...:)

To write a really bad Web Development Proposal doesn’t take much effort really. In fact, you can do it by following these 2 simple steps below :

Not Doing Your Research

The best way to lose a client is to misinterpret their needs by proposing recommendations that aren’t in line with what they really want.  You see, requirements analysis is critical to a Web Development proposal because it shows the client that you understood their objectives for the project. 

Solution : Research the business and thoroughly review their requirements, then be specific about the problem they want solved.  A detailed requirements analysis sets the stage for your specifications (i.e. how you are going to meet their needs and objectives), which in turn helps set the Scope of Work, appropriate timelines and costs. 

Grammar and Spelling Mistakes

- beleive instead of believe
- copywrite instead of copyright
- sentences that go on forever with no pauses
- paragraphs so long that you need an aspirin to continue reading

Spelling and grammer mistakes are the footprints of a sloppy and unprofessional Web Developer. The fastest way to make your Web Development Proposal come undone is to not dot your I’s and cross your T’s (pardon the pun). 

Solution : Run a spell check against your document and give it several proof reads (preferably from 1 or 2 other persons).  Seems simple doesn’t it?  It is in theory, but you’d be surprised how many people stuff this up.

And that's it....two simple steps for ruining any chance you have at securing another Web Project.

Tina Pixon