A few weeks ago, I thought ArcLab was ready to launch. The product worked, the landing page looked polished, and I felt like all that was left was pressing the button.
Then I started sharing it with other builders.
The feedback wasn't about bugs or missing features. It was about the experience. A few people said it felt too generic. At first, I wanted to explain every design decision we had made, but after reading the comments a second time, I realized something important. They weren't attacking the product—they were describing how it made them feel.
So we made a difficult decision.
Instead of making small tweaks, we rebuilt it.
We rewrote almost every piece of copy, redesigned entire sections, refined the interactions, removed things we liked, and kept questioning every detail until the experience finally matched the product we wanted to build.
That process taught me something I'll probably carry into every future project.
People don't separate your product from the way you present it. If the first impression feels rushed, they'll assume the product is rushed. If the experience feels generic, they'll assume the product is too.
Today, ArcLab is back.
Not because it's perfect, but because it finally feels intentional. It reflects the level of care we wanted people to experience from day one.
We're getting close to launch, and this time, we're excited to share it.
If you've ever rebuilt something after receiving hard feedback, I'd love to hear your story. What was the comment that changed the direction of your project?
Top comments (0)