Product answers without the query bar.
Cedric reads events and funnels from PostHog and says what changed this week, so the whole team can ask product questions in plain words.
$50 in free credits when you sign up. No card needed.
- Product analytics answers questions people stopped asking, because asking meant learning the tool.
- Cedric reads events and funnels and answers in the channel, in plain words, caveats included.
- Before-and-after questions become one sentence: did the release move the funnel, and at which step.
- 'What changed this week' arrives as a readable summary, not a wall of charts.
- Short windows and small samples get flagged, not hidden behind confident percentages.
What can a PostHog AI agent do?
Every product team has the same asymmetry: the questions come from everywhere, the ability to answer them lives with whoever knows the analytics tool. So most questions go unanswered, and decisions ride on anecdote. A PostHog AI agent removes the asymmetry: anyone in the channel can ask what users actually do, and Cedric reads the events and funnels and answers in plain words.
The sharpest use is before-and-after. A release ships; the honest question is whether it moved anything. Cedric compares the funnel across the boundary and answers at the step level, where the drop-off fell, where nothing changed, which is the difference between 'the launch went well' and knowing what worked.
An AI employee reading your product data has one more duty: honesty about uncertainty. Five days of data is five days of data, and a step with forty users does not support a percentage with a decimal point. Cedric flags the caveat instead of burying it, which is what makes the rest of its answers worth acting on.
After the release
Did the new onboarding work?
Lena Brunner9:14 AM
@Cedric did the new onboarding change the signup funnel?
CedricAPP9:15 AM
Since Tuesday's release the funnel completes at 34 percent, against 28 before. The gain is all at the invite step, where drop-off fell from 41 to 29 percent; earlier steps are unchanged, so the shorter invite form looks like the cause. One caveat: five days of data. I would read it again after a full week before calling it.
Events and funnels
What users actually do, step by step, answered without anyone building a query.
What changed
This week against last, release against before, at the step where it happened.
Caveats included
Short windows and small samples flagged plainly, so the numbers stay trustworthy.
Connect PostHog in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect PostHog from the dashboard
Open the Integrations page and sign in with PostHog on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what changed in the product this week?". You describe the outcome; Cedric picks the PostHog actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold PostHog into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
Product data closes the loop the other tools open: GitHub says what shipped and when, and PostHog says what it did to behaviour. Upstream, Google Analytics covers the site before signup, so the whole path from first visit to activated user is readable in one place.
Ship, measure, read it out in the channel: the loop most teams describe in their handbook, actually running.
Where the limits are
Cedric reads PostHog; it does not define your tracking. Events, funnels, and what counts as activation are set up in PostHog by your team. If the instrumentation has holes, expect them named, not filled with guesses.
Cedric sees what the PostHog connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes, natively. PostHog is one of the apps Cedric knows deeply, with a built-in playbook: connect it once from the dashboard and ask in plain words, with no workflow to build and no fields to map. It sits alongside 3,200+ other connectable apps.
That is the point. Support, sales, and founders can ask what users do in plain words and get plain answers, without anyone learning a query interface.
Yes: ask for the weekly funnel read and it posts on cadence, with movement against the previous period called out. A release week can get a daily read until the picture settles.
Deliberately blunt. A short window or a small sample gets said out loud, and 'no meaningful change yet' is an answer it will actually give.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Let the product speak for itself.
Install Cedric, connect PostHog, and ask what your users actually did this week.
100K credits ($50) on sign up. No card needed.