I renamed my product 24 hours after launching. Here's why.

Yesterday I posted a Show IH about WebHunter — a lead gen and CRM tool for web designers finding local businesses without websites, starting with Spain.
The feedback was better than expected. Four people replied with substantive thoughts. Three of them, independently, flagged the same thing: the name.
Not the product. Not the market. Not the pricing. The name.
The specific argument was this: WebHunter frames the product as a prospecting tool. That's accurate for the first wedge — finding businesses without websites. But the actual vision is closer to a sales operating system for small web agencies: find the opportunity, generate an automatic digital audit that becomes the pitch, manage the pipeline, send outreach, track follow-ups. The name limits the mental category before the product even gets a chance to show what it does.
One commenter put it well: "If they first understand WebHunter as 'find websites to pitch,' that frame can stick even after you add audits, outreach, CRM, and follow-up. That is the risk."
So I changed it. 24 hours in, before any real users, before SEO, before product memory. The cheapest moment to do it.
The new name is Cloza. Evokes "close" without being literal. Works in Spanish and English. No ceiling. New landing is live at cloza.es.
Two things I took from this:
First, the IH community is genuinely useful for this kind of pressure-testing. Not just validation — friction. The best feedback wasn't "great idea", it was "have you thought about what happens when this grows?"
Second, names matter more than I thought before launching. Not for branding reasons. For category reasons. The name is the first mental model your user builds, and it sticks.
Would love to know — has anyone else renamed early based on feedback? And does Cloza land well or does it feel too abstract?