Paul Strauss, Business Software Developer

We have a relaxed talk about what the business does and what is the problem that needs to be solved. After I get sufficient details about the project, I go back to my desk and, using the notes from our discussion, I will design an app which meets their unique needs and solves the problem they are having. I will spend a few days writing about and working out the details of my solution. I present that document to the client for them to review. There are several purposes for this document: 1) document my understanding of their needs; 2) allow the client to correct any misunderstandings or omissions; 3) come to an agreement of what I will deliver; 4) estimate the time to complete and the price. There may be more than one version of this document if substantial changes need to be made once the client reviews it. When we agree on the scope of the project, the price, and the payment schedule, I will commence work.

As soon as possible, I will deliver a preliminary version of the program. I ask that the client work with it a bit to get a feel for what will eventually be delivered and since it is early on in the development process, they can ask for changes. Some changes may effect the amount of effort required and may therefore effect the final price, which will have to be discussed.

When the final version of the project is delivered, I allow some time, at least two weeks for the client to actually use the program and assure himself that it is what he needs and that it works as it should (that there are no bugs). I will fix any bugs as soon as possible and deliver the new version. Again, the client is given some time to use the program. Once it seems to be correct and complete, the final payment is due.

However, there still may be bugs lurking in some hidden corners that don't show up right away so I offer this guarantee: I will fix any errors at no additional cost that appear for at least six months after the final delivery, given that no one else has changed the program.

I have 5 years of formal college coursework, focused on Chemistry (my major) and Computer Science (because I also found that interesting). This means that I've had a great deal of scientific training, but I also have a good foundation in computing, including some very advanced mathematics courses. All this helps when it comes to writing a program, not just because I've learned the  techniques, but I've learned how to approach and solve problems. That is, I have excellent analytical skills.

If I have done a thorough preliminary design of the project, I can offer a fixed price for the project. I ask for 1/3 down when work commences, 1/3 when I deliver the final version, and the final 1/3 after the client has used the program for several weeks without finding any errors.

If the client wishes, I will bill for my exact time at a rate of $60 per, accumulated and rounded to the nearest quarter hour.

Take a problem-oriented approach. Focus on what needs to be done rather than how it should be done.