Proposal Guidelines


Published on

Proposal Guidelines

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Proposal Guidelines

  1. 1. Proposal Guidelines<br />
  2. 2. Proposal is nothing less than a contractual document detailing the solution for the defined requirement……give it the importance it deserves!<br />
  3. 3. Before you start working on a Proposal<br />Make a WBS- listing the name of stakeholders, their responsibilities, deadlines, their ph numbers and mail id<br />Make necessary arrangements for version control, especially the pricing part (adhere to naming conventions)<br />Decide on the proposal format/ template<br />
  4. 4. What should a proposal contain?<br />Executive Summary..a must<br />Understanding of the requirement<br />Scope/ Out of scope<br />Proposal Revisit criteria<br />Solution<br />Project Management- Timelines/ Deliverables and Organization structure<br />Assumptions- Technical/ non technical<br />Expectations from the customer<br />Commercials<br />Annexure<br />
  5. 5. How may pages?<br />A proposal should not exceed 25- 30 pages!<br />If you have more info, bundle it into annexure<br />Point to the annexure wherever applicable <br />Use diagrammatic representation<br />Excessive English usage, a strict NO!<br />
  6. 6. Executive Summary- 1 page<br />Start with thanking the customer<br />Mention that you believe you can provide the solution for the customer requirement leveraging your expertise<br />Write your solution in 2- 3 lines, say using MVC architecture or something…<br />Timelines and cost- This is the crux and will decide if the customer will read the subsequent pages<br />Value ADD/ Cost saving- This is a deciding factor too <br />Why you?- also include 1 line case of similar solution developed for other customer, point to detailed case study in the annexure<br />
  7. 7. Solution- 2- 3 pages<br />If you want to sustain interest in this section, give a diagrammatic representation<br />In case the solution is developed by 3-4 individuals, combine it into 1 solution<br />Most of the time, the teams try to copy and paste the solution from earlier similar proposals, make sure there are no goof ups and the solution provided is for the said solution only<br />
  8. 8. Timelines and project org.<br />Here again, use MPP or Excel to define the timelines, this is much easy to comprehend<br />Map the deliverables against the timelines<br />Make the suggested Org chart in Visio/ Power point and then paste it<br />Describe the important roles and responsibilities<br />It would be good to attach 1 or 2 strong technical resumes<br />
  9. 9. Commercials<br />Use the scientific estimation techniques<br />Be ready with the answer to “what is your basis of estimation”<br />In case you are planning to suggest innovative business model, vet it with the finance team<br />Make sure your deal value has the required margin<br />Keep the cost break up ready, just in case the customer asks<br />
  10. 10. Other sections<br />The revisit criteria should contain 3-4 lines on when the proposal would be revisited- change in scope/ dependency etc.<br />Segregate the internal and the customer dependency<br />Sometimes, the scope of one team might be out of scope for the other team, just be cautious<br />Separate the technical and the business assumptions<br />Customize the case studies<br />
  11. 11. When in doubt, ask!<br />Less time for a quality proposal? ask for extension<br />Unclear requirements? ask for clarification<br />Does the RFP point to some other document? Ask for it<br />
  12. 12. Check before submission<br />Draft the proposal atleast 6 hours before the submission (its tough…but make this a practice)<br />Get the required approvals from the finance team<br />Make sure there are no errors in pricing<br />Get 2 rounds of review done<br />Format, check for spelling mistakes<br />
  13. 13. Thank you!Shripriya.subramanian@gmail.comAlso view my presentation on presales-<br />