>Does anyone know of any links for writing up a project?

I could send you one I wrote [over] a year ago - it's an okay example - but the prospect did not buy the project:-)

The best approach is to keep it simple. Approach like a 5th grade science project. It does not have to be specific (like the development language will be "MUMPS" and the database will be "MySQL", etc).

Keep it general. The prospect wants two things - someone they can trust - and a price and delivery schedule that meets their expectations.

Basically you would define the problem (if a legacy system is in place be sure to "praise" it for it's "service", and gently describe why it is being replaced. Thank any "staffers" that you interviewed as you collected information to do the "write-up".

Describe the modular components. Explain how the replacement project enhances (or does not enhance) similar modules in the legacy system.

Be honest - and never - never - say a bad or disparaging word about anything, anyone (even compeditors) related to the project.

Don't be too specific - You don't have to tell them the DB will be "MySQL" or "FoxPro". You don't have to tell them the front end will be developed in Visual Basic. All they really wany is a solution they can depend on - and brand affiliations of the tools used to build it are at the bottom of the list!