How to screw up tech due diligence

It’s easy…just act like you are answering the questions without really answering them. You might get by doing this for a while, but sooner or later someone will call you out. People (like me) will conclude you haven’t the slightest.


The questions: What version of PHP did you use? What AJAX libraries did you use? Were any other libraries used?
The bad answer: “nope, php and ajax”
Conclusion: You could have said you stayed at 4.x because of your host, that you pulled from, and peppered in a reworked OSS plugin. Something. But you didn’t have a clue.

The question: What database and version are you using?
The bad answer: “mysql latest version”
Conclusion: Not entirely off the hook, but was that MySQL 4.1 or 5.0? A lot of leased equipment comes of the block with one or the other, but who cares eh?

The question: What web server are you using?
The bad answer: “dedicated server”
Conclusion: Now that answer WAS off the hook. Clearly, you are now in dumbass land.

I’ll stop right there. The bottom line is…I’m no tech maven, but even I know the basic platform questions to ask. Nowadays, most people do.

If someone asks you some simple due diligence questions and you don’t know the answer, it’s ok to say so. But don’t say you’ll go get the answers and then return with garbage. The inquirer has little choice but to assume you are full of it.

PS: Those answers were actually provided to me, just recently. The other party got pissed when I immediately called it a day, and actually accused me of wasting THEIR time. Nice.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.