writing proposals?

Out of context: Reply #8

• Started
• Last post
• 17 Responses

• maikel0

  try the following...
  write an executive summary outlining scope, cost, schedule and all the other requirements.
  then write in full a description of the project.
  try to explain technical jargon in plain english or add a glossary. put 'further reading' in case they want to understand the technologies better. it will show that you can communicate even with the non-geek kind.
  in your breakdown include how many people, how many hours and the cost per resource. you will find easier to justify how much you charge if you do that...

  and try to bullshit very little or none. people don't like reading this shite anyways...

  maikel 0Permalink

  UpvoteDownvote

  Flag

  • never, ever state the number of hours. What you do has value for beyond the time it takes to implement.Amicus
  • btw... have you ever estimated the no. of hours correctly? No? well there's another reason not to state hours.Amicus
  • mate, it is an estimate, that you update regularly. have you ever used project / merlin?
    maikel

  Show [[ numHiddenNotes ]] more notesAdd Note

  SaveCancel

View thread