Either approach have pro’s and con’s. By end of the day, it doesn’t matter. What really matters, are the skills of the team (dev and management).
Trust me, fixing own “legacy” code few years old is not much easier than someone’s else code.
Also, assuming that company is on the market for a several years, for most programmers in a dev team it’s “someone else’s” code anyway
And, by the way, it’s easier to acknowledge fundamental flaw in someone else’s approach rather that in your own. Which make it harder to fix “own code”.
What really matters, is a strength of the team, knowledge management, solid system architecture and efficient development processes & Q&A.
I can point on a few (obvious) weaknesses that Curve have in this process, but it really doesn’t matter if they were inherited from 3rd party or “home grown”, as the cure will be exactly the same.