So I tried to draft a proposal template

Advice on writing project proposals

You’d think it’s easy to write a project kick-off document.

You just write about what the project is, what the client is getting, blah-blah=blah.

Well, for the people who’ve tried and seen that it actually isn’t that simple… these articles:

1. The basic and straightforward — Writing the Market Requirement Document. By Pragmatic Marketing.

A bit of a boring read, but I like how it outlines the different “component” documents that are needed to contextualize a project.

• Business plan: research regarding market problems, win/loss analysis, market definition and sizing, distribution strategy, competitive advantage
• Product roadmap: Phases of deliverables over the next 18-36 months/ next three or four releases
• Requirements document: persona definitions, prioritization of user scenarios and need gaps/problems

2. I like that this article makes the case for bravery (“What’s different about your company? Why does your company exist?”) in writing project proposals: A List Apart’s A Modest Proposal.

Your words here will dictate the nature of your relationship. Exchanging the role of equal partner for servant is your choice. If you want respect, authority, and control, you must demand it. To do less is a disservice to the client and an altogether unprofessional attitude.

Beyond setting the tone for the relationship, of course, you’re also trying to win some business. The good news for you is that a prudent client—the kind you really want—will choose a web partner on the strength of the entire package.

Be upfront about your business principles. Stand for something. Even if—especially if—your way is controversial or unique. Full Stop might not agree with Bold about whether the customer is always right, but it’s important that Bold’s potential customers do. Meticulously evaluate every client before issuing a proposal. Once you do, don’t panic if they walk because you stuck to your philosophical guns.

3. What kind of client document works for Happy Cog: A List Apart’s Agreements Equals Expectations.

Interesting advice.

Having the cost on the second page.

Listing all potential deliverables, instead of stating what requirements Client will definitely be getting when you haven’t even gone through the project yet.

Basing revision cycles based on maximum hours, rather than number of cycles.

Read the article. Pretty useful.