You need to get KAREL to market as soon as possible and everything is ready to go. You think that if you delay even a month, your chances of success will drop even more. You choose to ignore the second bug, and release KAREL as is. You also allocate a few programmers to developing a patch for KAREL, but the group is disbanded soon as you deem it unnecessary.

During the next four months, you enjoy tremendous success as KAREL spreads throughout the nation's hospital systems. The LOGO team, however, continues to work, hoping that they can get LOGO out in time to capture what little is left of the market. You hear rumors of a department within the LOGO team working on finding bugs in the KAREL program.

Worried, you reinstate the group responsible for patching KAREL. It's too late, though, as the LOGO group releases a press report detailing the second bug that you knew about. In a fatal public relations error, your company takes the stance that you don't believe the bug will ever present a problem to anyone and therefore didn't deem it necessary to fix the problem. The LOGO team takes advantage of this, demanding that you recall and fix all the copies of KAREL. During this time, LOGO the Medic is released, and almost all your orders of KAREL the Nurse are cancelled.

Virtually overnight, LOGO the Medic becomes the industry standard for hospital interface software. Eventually, with your spirit broken by the failure of KAREL, you close down your company and move to Australia to raise koala bears on a small ranch outside of Sydney.