So, I have this friend… This is the way many people start their stories when they are really talking about themselves, but this time it is not the case. This story is about a friend of mine, we will call him John.
John runs a website which is a store front and information source for a niche market that didn’t realize they were a niche until John’s website. It is a cool idea for sure. John is not a developer. He runs the company and handles all of the marketing and content that goes on.
When John wanted some new features on his site he came to me and we talked. I informed him that as his site was in .net I was not able to do any programming but I could definitely be a consultant on whatever project he was getting done for his company. John then went out and asked for programmers that new .net and who could handle a project of the size he wanted.
I referred my friend Jason Rowland, who accepted John’s RFP (Request For Proposal) and came back to him with a fully fleshed out proposal. Jason’s proposal came in higher than John expected and the timeline was longer than the other proposal that came in.
Sam sent in the other proposal. His proposal was a more manageable number, something closer to what John was hoping the cost would be for this feature and as I mentioned before, he said he could get it done on a shorter timeline.
Well, you know as well as I do that I would not be writing this story down and sharing it if something didn’t go wrong.
John went with Sam, which made sense at the time because he was cheaper and the feature would be done sooner. After the delivery date that Sam had come and gone, and after the money Sam had asked for did the same, John was worried. I had been talking to John throughout this project, even consulting the developer on one of the features and how to handle it so that it was optimal for SEO, and it didn’t get the site de-listed. I noticed that the developer was a little lost, he was trying things that were misinformed and seemed out of place for a developer of the caliber that was needed for this project.
In the middle of all this, someone noticed that the website was hacked into and there were prescription drug links all over in the source of the pages and told John. John asked Jason to look into it, because Sam was so bogged down with the other project. Again, Jason sent him a proposal of what would be needed. On top of that, Jason noticed a huge security leak in the site that would allow future issues if they didn’t cause the original issue itself. Jason told me about what was going on, because he knew I was friends with John and had been consulting with him along the way. I immediately sent John an email showing him the security issue and how his current developer was the cause of it.
John got Jason on the phone, asked him to figure out how much it would cost to fix all the problems and put Jason in touch with Sam. Sam admitted to Jason that he “left a security vulnerability issue on the site because he figured he’d ‘clean it up on the next go-round’”. John was PISSED, and understandably so. He hired Jason to fix the issues on the site.
As of last night, the repairs have cost John $1000 and things are only partially fixed.
What is the lesson here?
When you ask for proposals and you receive them, please do not look at the number at the bottom. Look at the proposal itself, judge the developer on the amount of time and effort he puts into the proposal. This is a good indication of how dedicated he is to his profession and providing a quality product for you.
When Jason did his proposal, he came in considerably higher than Sam. Up front, this is scary to anyone asking for proposals because they KNOW how much money they will HAVE to shell out and there is no guarantee that the product will work or be finished on time.
John has spent more on the project than Sam proposed and more than what Jason originally proposed. Jason will fix the problems, but no one can work for free so it is going to take some money to fix the glitch (READ: to fix Sam’s crappy job).
This is a tale as old as time, because this happens with any contract work. People will consistently worry about the bottom line and not pay attention to the warning signs. Please learn from John so that you do not make this mistake yourself.
The last time I talked to John his comments to me were:
You and Jason are my go-to developers from now on
Thank God you recommended Jason to us
I just wanna say that you and Jason are good at what you do because you convey trust and that you know what the hell you are doing.
Sphere: Related Content