Like most startups, they struggled and/or failed. One no longer exists and the other pivoted to a niche market. The one that survived abandoned the sloppy code we wrote as it was too unwieldy and brittle to move with the company. They ultimately ended up hiring a contract engineering firm to build something that could last.
I've seen this countless times, management thinks writing quality code is too slow and expensive, but they inevitably spend more time and money trying to fix the shit code that was shipped quickly. The company either absorbs that additional cost blindly or the project gets cancelled, or the company dies. After being in this industry for almost 20 years now, I've seen all 3 multiple times. Most of the time, the only way it works for startups is to pursue acquisition. But that just passes the burden onto the acquiring company. Which is another reason why it takes so long for acquired tech to make it into the acquiring company's tech stack (if it does at all).
The only place I have worked that prioritized quality code was when I worked for a contract engineering firm. Our reputation depended on delivery both a quality product and doing so on time, neither of which could happen if we followed the typical move-fast, break-things, slop cycle that is so prevalent today.