These reports look too good.
Back when I built custom MS-DOS database applications (Clipper), one of my clients was a small partnership which also had some private investors. It eventually came to light (to me, anyway, since I worked closely with him) that the junior partner was going to make a move for total control of the operation.
JR. PARTNER: I’ll be meeting with the investors tomorrow night.
ME: OK.
JR. PARTNER: I’m going to tell them that [Sr. Partner] is basically incompetent, and that I should be put in charge of the business.
ME: Oh, OK.
He then goes into an extensive monologue on company “problems” and his plans, all while I’m fiddling around with the app on the PC. Eventually, he winds down.
JR. PARTNER: So, are you with me?
ME: Huh?
JR. PARTNER: Are you going to go to the meeting with the investors with me tomorrow night and back up my position?
ME: You know, this really is none of my business. I’m just the guy you guys hired to build this app for you.
JR. PARTNER: So you won’t be there?
ME: No, I don’t think so.
I then start printing a bunch of transaction and sales reports for him to look over, which, if memory serves, was really why we were having that particular meeting in the first place. He looks over them as the printer spits out the pages.
JR. PARTNER: These are too good.
ME: Huh?
JR. PARTNER: The numbers. Too good. The investors will side with him.
ME: …
JR. PARTNER: Can you do something about these reports?
ME: What do you mean, reformat them?
JR. PARTNER: No, the numbers. Change them. Make them look a lot worse.
ME: …
Talk about warning signs. gave him some technical BS on why the data couldn’t be changed after it’s been reported and hurriedly wrapped up all my work in less than a week. Made sure I had my final check in hand upon installation of the last deliverable, and I was out of there. Last I heard, the company had folded within 3 months.
Eldon Sarte
http://eldonsarte.com