[twelvechess]

Ok, your UI/UX is amazing, the experience is awesome. But for me, I don't immediately understand what you do and for whom. What I understand: You tailor my website to the visitor on my site (landing page), which would be pretty cool as an add on. What I don't understand: How you would do that, how do you create a personalized experience for a visitor you don't know something about?

[chrismjelde]

Glad to hear you enjoyed the UI/UX and experience! The ‘how’ is a key question - right now the visitor inputs what company they’re from, and with that info we send out a research agent that compiles a) context on that company, and b) combines that with the deeper research its already done on your domain — essentially it marries up what it knows about you, with what it quickly learns about the visitor, to the customise whatever sections of the website you’ve given Kenobi permission to transform

Obviously a lot of companies have vastly different personas, and this is a harder problem to solve which we are working on.

[topnde]

What they do is ask the visitor from which company they come from. Behind the scenes, this is what I imagine happens: - Kenobi scrapes that website and understands what it does - Has some prompts to transform the text in your website through the lens of your user: eg "Transform this text [your website text here] to appeal to a visitor from this company that does the following [scraped content here]"

Of course internally it might be much more complex than this but this is how I would do this if I had to build it.

[ericmcer]

really? My very first interaction was it prompted me for my company name, and the basic html text <input/> didn't behave correctly.

It had no highlight styling so if you wanted to highlight a portion of your input it would be impossible to tell what the current selection was.

Looks cool, not trying to hate, I just have a pet peeve around native elements having basic function/accessibility features removed during heavy styling.

[fxn-m]

Thanks for the feedback and sorry about the poor UI experience there! That should be fixed now and we'll keep an eye out for more cases like that.

Definitely a balance to be struck with going heavy on styles, whilst not breaking native element features and violating users' expectations!