I am a sole developer responding to a Request for Quote. The project is significant, and will take me more than 6 months to complete, (if I am the successful bidder).
One of the questions that I need to answer relates to 'knowledge transfer between employees', which is obviously difficult to answer for a sole developer. As a sole developer, how do you help customers understand that the "developer as single point of failure" is no longer such an issue?
Here are some of the points that I will make:
- I am using mainstream tech choices, such as PHP, Laravel
- Skills for these are technologies are very common in the marketplace
- My software architecture follows best practices and uses many OOP design patterns
- The code is very well documented
- All project documentation is stored in a Wiki
- Code is stored in an industry-standard VCS (github), under the control of the customer
Given the above, I think it is reasonable to say that any competent Laravel developer could be working productively on the application within a couple of hours. (Contractual issues aside, of course).
Is there anything else you can add? (I will also present an option where a second developer spends time on the application throughout the 3 year maintenance period, but this will obviously drive the cost up).