Killing a name noengine could resolve

The company was named after a phrase that is already this city's own nickname. No search engine or answer engine could attach the phrase to the business, because entity resolution, not keywords, is what those systems run on. The name was a growth ceiling disguised as a branding preference.

The positioning underneath had a second problem. The pitch rested on a below-market price claim that could not be substantiated for the flagship building, which made it both unprovable and a regulatory exposure.

• Ran a naming study grounded in entity resolution rather than taste, checked trademark clearance, and rebuilt the shortlist around names a buyer could parse without industry vocabulary.
• Replaced the price claim with a promise about timing and access, which is a statement we can actually demonstrate, and rewrote every page against it.
• Built the marketing site as a block-based CMS covering five developments, and ran a scored conversion teardown that cut required lead-form fields from six to four on the highest-intent pages.
• Built the partner sales kit that opened a second distribution channel: pitch decks, a partnership one-pager, competitive analyses and deal sheets aimed at a named segment of agents, plus the search and paid-social acquisition plan behind it.

The business now has a name that resolves, a claim it can defend, a platform it owns, and a partner channel with the collateral to work it.