RE: Engineers As Consultants Pt. 10: When A Subcontractor Doesn't Deliver

pmoyle111 — Tue, 19 Aug 2014 23:56:01 GMT

I had a consulting/product development co back in the mid eighties to late mid 90's. I had both full time employees and hired temp contractors. I endured similarly described problems and many other types which would take me a book to recite.

One advantage I had was a good lawyer whose computers I maintained. The key is to have an iron clad contract that specifically states that they are not an employee and liability for damages resulting from poor or incomplete performance. Also that all IP is specifically proprietary and confidential and is owned in entirety by the company. I would have called his bluff, and had my lawyer send him a letter. No lawyer would have touched his case.

In more recent years, I prefer to work as a "contractor" for engineering temp agencies. I get paid hourly, every week. Contracts can last years some times. The agency gets some of your cash, but you don't have to wait 30, or heaven forbid 60 or more days. It's a little different, but largely, it's a lot less trouble and more profitable.

RE: Engineers As Consultants Pt. 10: When A Subcontractor Doesn't Deliver

DAB — Mon, 11 Aug 2014 19:28:18 GMT

Another good post.

You did a great job of highlighting the need for RISK analysis when hiring a subcontractor.

When you have to use someone other than your trusted group, I would suggest asking one of your trusted group to see if they have someone available that THEY trust.

As you stated, reaching this level as a consultant is the scariest time in your life. It brings new meaning to the term "Trust but Verify".

In the end, you can seriously damage the trust of YOUR customer if you have one of these episodes. Damage control is essential and as you pointed out, getting rid of the problem helps keep your investment time to a minimum, especially if you have alternative options for the same skills.

DAB