Hi,

Each day it gets more dificult to a sole guy or even a small (two to three people) software company to get fairly good contracts. Even more if you are a VFP developer, in which case many companies don't want their systems developed with this tool (the tool is not the point here).

Even small companies (customers) want systems that require different developer skills to develop it, and that are hard to find in just one person, mainly when they want to go internet.

The problem is: sometimes you face a project where you (or your small company) don't have all the skills necessary to get it, and you loose the contract.

Last week I've been talking to two fellow developers to arrange a way to group different skilled people, each one keeping their own independency, with their own companies etc, but whenever there is a project requiring people with different skills we could form a team and try to get the contract.

People told me this is what is been called a developers network. I found it a very good idea, and would like to have as much information about this as possible, to see the good and bad points, how this arrangement should be presented to the customer, if there should be a project leader, if there should be only one contract or one to each team member, how it should be handled when mantainance should be done etc.

Searched the internet about this subject and didn't get anything usable. If somebody could help me in this subject, pointing where I could find information, arcticles, white papers, people already working in this fashion that could exchange experience, posting ideas and pitfalls about it, I would be very grateful, and think many other fellows facing the same problem, I am, would to.

By the way which is the correct form to reference a network made up by developers?

• Developer Network
  
• Developers Network
  
• Developer's Network
  
• Developers' Network
  

Thanks.

Fernando