What Happens When You Skip the Discovery Phase (Real SaaS Examples)

I have had this conversation more times than I can count. A founder calls us three months after launch. The product is live. The team worked hard. But signups are low, users are dropping off after the first session, and nobody can explain why. They want us to fix the UX. When I ask what research was done before the build started, the answer is usually the same: we talked to a few people, we knew the market, we had a clear vision. No formal design discovery process. No user research. Just assumptions and momentum. This is not rare. It happens constantly in SaaS. And the cost is always higher than people expect. So I want to walk through what actually happens when teams skip the discovery phase. Not theory. Real examples from real products. And what a proper design discovery process would have caught before a single screen was built. First, What Is the Discovery Phase? The design discovery phase is the work you do before design and development begin. It answers one question: what should