people often think that the hardest problem to solve for any product intelligence tool is data pipeline or infra but instead the hardest thing to crack is how (rightfully) opinionated can you make your tool.
you can show all the statistics on a dashboard and nobody would care but put a single valuable opinion and look at the product go to the moon.
now i used to think that the opinions that our tool would have are my opinions(my team's) for a specific problem but lately i've realised that it's the wrong path.
the right path is to actually make a product that gets opinions from the data it stores from real actual users.
if onboarding A has more steps, is more annoying to complete, has a hard paywall, asks for a review, bla bla bla but it has a higher conversion rate(as per the sessions) than onboarding B which is much simpler and smaller,
@lucent_ai must point that the better onboarding was A no matter what any human thinks.
the next obvious question: how does the product really know when to form an opinion vs when to ignore when it sees a session? there is no right or wrong answer to this but we think of this problem a bit differently.
its not about when to form an opinion vs when to ignore but rather its about in what medium is that data useful, to form an opinion. there must be one.
the medium could be anything:
aggregages: daily vs weekly
features: bugs vs insights vs signalling
end user: developers vs GTM
every error, every successful session, every failed workflow has some magical insight hidden in it and we at
@lucent_ai want to uncover it for you.
come try us out(linked in the first comment)
its free for the first 400 sessions btw.