Writing software on a consulting basis can often be a losing proposition for developers or clients or both. There are too many things that can go wrong, and that ultimately translates into loss of time and money. The 15% rule we have come up with is intended to create a win-win situation for both parties.



Clients generally get what they want, and development shops make a fair profit. A perfect solution, but so far it seems to be working for us.

This may come as a surprise to some, but we make very little money selling software licenses. The vast majority of our revenue comes through consulting services writing code for hire. Having now done this for several years, we have learned some hard lessons. On a few projects the lessons were so hard we actually lost money. A few months ago I put together somewhat of a manifesto-type document intended to address the difficulties we have faced in developing software for clients. Aim pleased to say that it's made a noticeable difference. My hope is that this bog entry will be read by others who develop software on a consulting basis, so that they can learn these lessons the easy way rather than the way we learned them. What follows in this article is a summary of one of the main principles we now follow in developing software the 15% rule. If you had like, you are welcome to read the full Our Approach to Software Development document. For the impatient, the 15% rule goes like this before undertaking a development project we create a statement of work (which acts as a contract and a specification) that outlines what well do, how many hours it will require, and how much it will cost the client. As part of the contract we commit to invest up to the amount of time outlined in the document plus 15%. That is, if the statement of work says that the project will take us 100 hours to complete, we'll spend up to 115 hours (but no more). As to where-forest and why-toss on how this works, read on. Those that have developed software for hire know that the end product almost never ends up exactly as the client had pictured. There are invariably tweaks that will need to be made (that may or may not have been discussed up front) in order to get the thing to at least resemble what the client has in mind. And, yes, this can happen even if you spend hours upon hour's fine tuning the specification to reflect the client's wishes. Additionally, technical issues can crop up that were not anticipated by the programming team. In theory, the better the programming team the less likely this should be, but it doesn't always end up that way (Microsoft Vista operating system is a sterling example). These two factors, among others, equate to the risk that is inherent in the project. Something isn't going to go right, and that will almost always mean someone pays or loses more money than originally anticipated. The question is who should be responsible to account for those extra dollars? Up until relatively recently, we would shoulder almost all of the risk in our projects. If the app does not do what the client had in mind, or if unforeseen technical issues cropped up, it generally came out of our pockets For the most part it can't a huge problem, but always seemed to have at least some effect (the extreme cases obviously being when we lost money on a project). This seems kind of unfair, doesn't it? The risk inherent to the project is not necessarily the fault of either party. Its just there. We didn't put it there, and neither did the client. As such, it shouldn't be the case that one party shoulders it all.