You decide that once again, the safest alternative is to rewrite the faulty code to maximize the safety of KAREL. Three months later, your programmers declare that KAREL is as bug free as they will ever get it and is ready for release. Unfortunately, on the same day, the LOGO the Medic team announces that they will be releasing LOGO within a month, way ahead of schedule.

Rushing to get KAREL on the market at the same time as LOGO drives up expenses even more, but you can't jack up the prices because LOGO is also out on the market. Your sales are also not as high as analysts had expected, mostly due to the fact that LOGO has snatched up much of the market share you had planned on getting by releasing earlier. You've wasted too much time and too much money developing KAREL, to the point that the whole project is only mildly profitable.

But at least you didn't get sued.