-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new AI product in website / docs #8348
Comments
How would this be charged with flags? How does it work? |
A few thoughts:
|
@andyvan-ph and i were chatting about the AI product page and we’re thinking creating a top-level product page for it is wrong (at this point) for a few reasons:
at this point, it feels like it could be a nice landing page, and we can link it from the product analytics page. main points:
could also be a good opportunity to link to an LLM analytics forum topic for feature requests to help us prioritize what to build here. |
James idea: Add "AI engineering" to homepage slider, tease it there, link to docs (on how to use Product Analytics to set up AI engineering insights |
☝️ Works for me! Will close the other PR. We have case studies in progress regardless, so we can launch this in earnest when we're ready |
to use fancy words, i think we already have the primitives needed to be a pretty solid AI product based on https://github.com/PostHog/product-internal/issues/598
the reason i think we should push here - AI is changing how products are built, whilst the market is small today, this will be a very typical use case in a few years' time so we can dominate the space given our strong adoption with AI companies. this means we don't leave ourselves vulnerable to an AI specific product analytics tool appearing
i think the way this would work is pretty much:
Product page
the page could contain something like:
Tutorials
I think we'd do a tutorial for each of:
Product
I don't think we need to build anything new to launch with the above.
However, I think a simple product that steers users through the above could work well.
We could call it AI Engineering or something similar, the flow would be very similar to the experiments flow, but instead the user would choose an AI experiment type (prompts / model parameters / model itself / costs)
I'm not quite sure yet how prompts / model parameters / model are all stored/connected to - maybe this logic needs to sit in their code, but i could see it sitting in PostHog. I'll do customer calls here
The text was updated successfully, but these errors were encountered: