We don't know for sure. This is built on the intuition that websites are still a one-size-fits-all approach that makes no sense in an age where we have intelligence at our finger tips, able to process and reformulate information that speaks directly to people.
You could see this idea as being on the opposite side of the same spectrum as agentic browsing (which hasn't really taken off yet).
And thanks for the feedback! There are limitations in the quality of the personalizations in onboarding experience due to latency constraints. These get lifted the moment you create an account, and can start doing some more in-depth context gathering of your website and the types of visitors you're likely to get.
Consumers are sick of being the victims of a power imbalance already. Social media sites do this kind of personalization on their feeds, but they do not provide the user the power to control their own algorithm.
If every website is tracking my identity and surrounding me with an echo chamber outside of my control, that is not a good thing.
If the profile and prompt is something the user controls, it could be useful, but it’s still hard to trust it. It takes away the ability to have trustworthy links to information/products, if it’s different for every user, especially if the customization methods are hidden behind opaque LLMs and system prompts.
I do think this idea can make money, but it’s likely bad for the internet consumers and likely to be part of future enshittification.
Damn, that’s unfortunate. We found the logs and looks like apollo returned empty for your domain. I just pushed an update that uses the same enrichment workflow as the rest of the app and looks like it correctly IDed your co. we're using gemini 2.5 flash-lite under the hood, and if it's not grounded it can come up with some whacky results! we'll shortly be shelving it for flash-3-lite as soon as we can
We use apollo and gemini 2.5 flash lite with web search in a quick pass to ground and enrich data on the visitor. Right now, the queries are generic, as opposed to constructing more "tailored" queries based on what the host might be pitching to that visitor.
We're definitely going to be looking into finding more relevant signals on a case-by-case basis, and this kind of idea fits really neatly into that paradigm!
Definitely a balance to be struck with going heavy on styles, whilst not breaking native element features and violating users' expectations!