Hacker Newsnew | past | comments | ask | show | jobs | submit | sarreph's commentslogin

We’re heading to sleep as we’re on London time! Thanks to everyone who commented & for providing feedback. It’s been immensely useful to hear everyone’s perspectives.

Please reach out to us if you would like to at product@kenobi.ai


You shouldn't be(!) We have a very high bar set up to be met to be considered bot traffic. Sometimes we are at the behest of the model providers and there's way more latency + even timeouts under higher load.

We get asked this a fair amount and the way we’re strategising on it is to build more opportunities for the site owners to define context as part of the broad site research that goes into creating the interpolations.

If I was to do this, I'd decide on what audiences my site was targeting and ensure the landing page had pre-approved content for each of them. Then I'd only use the LLM to rearrange the pre-approved marketing content, such that it puts the content that it thinks best targets the visitor above the fold. This way, the worst the LLM can do is to order the content incorrectly, and the visitor would need to scroll to see the content that targets them.

Even better, the LLM can make up rules for matching traffic to targeted profiles (corp IPs shows enterprise content, gov IPs shows gov offering, EU IPs shows European hosting options, etc). This way you don't use an LLM while rendering the page, reducing cost and speeding up page load times.


That's a lot of words to say you have no idea how to do it.

If you would be willing to give us another chance please email product@kenobi.ai with the site you used and we can get the research context that it generated fixed! (This has been a bit of an issue for some users, when the research gathering agent goes down the wrong track)

We think that in commercial buying there will still be a place for “discovery”, where B2B visitors gain from being able to independently digest public facing materials themselves. And that this will mean the adoption of agentic browsing is slower than people think.

However, we did already start experimenting with the agentic browsers like Atlas and Strawberry — I built a PoC for the former. But this is still very much experimental!

Edit:

Just wanted to add that your question is a prescient one and it is something we get asked a lot by investors, VCs etc, but hardly ever by people who run businesses with websites, or the people who visit them / do commercial buying.


Aah! Thanks for reporting! We’ve seen that in a couple of cases. Feel free to reach out to product@kenobi.ai with the site you’re using and we’ll look into it for you.

So right now (what we’re demoing), we do “on demand” personalisation, so there isn’t an SEO angle there really. However, we started with pre-rendering changes onto hardcoded URLs and while that did affect content, we didn’t see any SEO issues come up since these URLs were being used in campaigns only.

Thank you. Accessibility came up in another comment and to be honest we've only thought in terms of _preserving_ accessibility so far, not _improving_ it (as you're suggesting) -- would love to see if we could explore something along these lines soon even though right now we're focussed on B2B...

> if the buyer enters their company and the copy just changes into what we think they want, are they going to lose trust that the copy is a true representation of our focus?

Great point. That's pertinent to how we've been configuring the research → computing "intent" pipelines. Our focus right now is mainly just to streamline content and show brands "in context" as much as possible without having too much of an "opinion".

Your idea about showing how specifically the company could be helped + a use-case is lovely way of putting some of the more complex layout generation ideas we've been working on!


Appreciate the candid feedback!

The number one request we have is to integrate deanonymisation, so you’re right on the money there. That’s coming in the next couple of weeks or so…

Wrt the changes being text-based for now, we do actually have image and complex element and layout generation working, but have kept it as an experiment for pre-rendered pages until we are confident we can get it right in most cases. (Some early beta users used Kenobi to send out in some cases thousands of customised landing pages with imagery)

We‘re also starting our on demand product with text only precisely because we want to hear what people think we should be working on next as we are a super small team of three!


I do appreciate you taking the time to respond. I wish you luck.

I suppose I was frustrated due to a mismatch of expectations and the fact that I do things like this every day with AI, it feels rather trivial to me.

But I can see how it may appeal to a wider market. I remember coming across a couple websites that were doing this automatically pre-AI, simply detecting who I was and displaying it in some basic ways. And yeah it was a bit weird, but it sure stuck in my mind for a long time, and it was a data-broker type company anyways, it triggered the thought "well if it can do this with me, it must have good data about everyone".

And I can see the more general case for B2B to surface the right use-cases for the user and such. I've interacted with many people with a business profile that would certainly click a "just show me what I care about" button, hell many technical people would love it too just to remove all the whishy-washy hype language and just see what the thing does.


Thank you!

> many people with a business profile that would certainly click a "just show me what I care about" button

You've encapsulated better than I did the kind of visitor segment we're building for right now.

> I do things like this every day with AI, it feels rather trivial to me.

I also agree with this sentiment. It's how I started ("surely it can't be hard to jiggle a page around now with LLMs") and it mostly worked! But the edge cases and heuristics are also proving to be a big chunk of the effort "iceberg" :D


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: