What makes a good Website Proposal and how to write one

Computers & TechnologyInternet

  • Author Jeremy Taler
  • Published October 11, 2010
  • Word count 409

The idea of writing a website proposal can seem at times overwhelming to some freelance web designers. Why you ask? Because being skilled in the art of writing code, working with software and in general developing great websites, doesn't necessarily translate into being able to successfully sell your services to a prospective client. Hey, just saying!

"Yeh, and so what!" I hear you say. "They can go to my website and see my portfolio and testimonials - I don't need to worry about a proposal."

Sure, but at the end of the day, you’re still going to have to present a proposal when applying for new work.

You see, what matters most to a potential client is what you can do for them, not what you did in the past for someone else. Your past work is a good indication of what the client can expect, but it is your website proposal that will tell them exactly what they should expect. A client wants to know if you understand their needs and requirements, what you are going to develop and deliver, how long the project will take, what are the project costs, etc. A website proposal provides the perfect platform for addressing all these points. Trust me, you do not want to take a half-hearted approach when it comes to writing a proposal.

So what does all this really mean?

Well, it means that if you are able to write a well-planned and prepared website proposal, then you have an excellent chance of convincing the client that you are the person for job. You’ll show them that you’re experienced, skilful and confident enough to take their idea from inception to delivery. Conversely, if you write a proposal that misinterprets the client’s needs and lacks quality and substance, then you might as well kiss your chance goodbye.

So what makes a good website proposal? Firstly, it must be structured correctly and include relevant project criteria such as Project Overview, Site Objectives / User Requirements, Deliverables (i.e. functional and technical specifications), Project Benefits, Website Architecture, Project Phases and Timelines, Project Considerations and Assumptions and Project Costs.

A good website proposal should also explain your solution in an easy to understand manner. It should read and flow well and engage the client’s interest.

Bottom line ---> a well-written and structured proposal leads to more work, while a bad proposal equals less work, more stress and more headaches.

Jeremy Taler works as a Freelance Web Developer out of Chicago Illinois, helping people and businesses with their website and programming needs. His website can be found at Website Proposal Template

Article source: https://articlebiz.com
This article has been viewed 579 times.

Rate article

Article comments

There are no posted comments.

Related articles