ProductAnalyst.ai - Niko Noll - Interview (German language)
My latest podcast Episode
Nico Noll: Actually Using Product Data – with AI
Nico Noll has been a product specialist for years. Has trained hundreds of PMs – inside companies, in workshops, as a coach. And is now building his own thing: Product Analyst AI. A tool born from his own pain: years spent as a PM where data was theoretically available but practically out of reach.
The core idea is simple yet structural: product data exists in almost every company. But nobody really uses it to make decisions. The bottleneck isn’t the amount of data – it’s access and interpretation.
I am regularly giving trainings for Product Managers on how to live the new PM work augmented by AI - using Claude Code. It’s about PM work, not simply learning the tool.
The Data Gap in Product Management
Tracking runs. Events get logged. Mixpanel, Amplitude, PostHog, Google Analytics – at least one of them is almost always in the stack. But when a PM really wants to know which behavioral patterns predict churn, which users drop off after onboarding, which segments behave fundamentally differently – they’re waiting on a data analyst, a dashboard, or both. Both options: slow, expensive, often simply not available.
Nico experienced it as a luxury when he was a PM at Xing: a frontend analyst and BI analyst always on hand. That’s the exception. The rule: either no data team, or one that’s constantly overloaded.
Thesis 1: Most product decisions happen without current, granular data – not because the data is missing, but because access is too cumbersome. Granular questions take weeks. So they mostly don’t get asked.
Thesis 2: The real problem isn’t a technology problem. It’s an access problem disguised as an analysis problem.
What Product Analyst AI Does – and What It Doesn’t
No “vibe analytics” – no throwing a CSV into ChatGPT and hoping for the best. Instead, a system with clear guardrails: generalized statistical functions on one side. Company-specific context on the other.
The approach: separate what can be generalized (statistical methods, calculation logic, segmentation functions) from what is company-specific (event names, business definitions, segment structures). Both together create a system that delivers reliable answers.
What works today: everyday product management questions. How many users show this behavioral pattern? How does churn rate differ across our segments? What happens on average in the first 30 days after signup?
What doesn’t work yet: the exploratory two-hour sessions with a senior data analyst. The complex strategic analyses. That’s deliberately not the goal – Pareto logic. 80% of the questions teams ask daily are answerable. That’s where you start.
Thesis: When the same question comes from the CEO and from the PM, the same answer has to come out. That’s the difference between a tool for real decisions and one that just delivers the feeling of having analyzed something.
Context Engineering – The Real Differentiator
This gets technical. Worth it.
An LLM without context makes assumptions. And does so with alarming self-confidence. Markus shares a good example: reviewing a bootcamp curriculum. ChatGPT without specific context produces generic output. Then name the deep technical errors, ask again – suddenly the model says it has now activated the necessary knowledge and can actually go deep.
The LLM knows what it needs. It just usually doesn’t get it.
What Product Analyst AI builds because of this: a context layer. What do the event names actually mean – because they often aren’t called “conversion_event” but some cryptic string. How does this company calculate churn rate? Which segments come up again and again? Which metrics are already defined?
All of this gets built out once – currently still manually during onboarding – and then provided to the agent as structured context. The agent pulls context and calls deterministic calculation functions. Combines both. Delivers reliable answers.
Thesis 1: Prompt quality matters less than context management. Whoever builds in context in a structured way gets dramatically better results.
Thesis 2: The people already getting real value from AI, and those saying “it’s all generic” – they differ almost exclusively in how well they manage context.
Data Access for Everyone – Not Just Product
Customer Success wonders whether the upsell from last quarter is even being used by an account. Sales wants to know which customers are showing churn signals. Marketing would love to see which features actually drive activation. All of that is in the data.
But Mixpanel access is usually only for product. And even there, people often don’t really know what’s inside the data.
That’s the bigger picture behind Product Analyst AI: not just serving PMs, but enabling data access for all teams in the company. Without everyone having to learn Mixpanel. Without filing a ticket to the data team. Without waiting three weeks.
Thesis: Most companies have a data access problem – and mistake it for a data analysis problem. The fix isn’t building more dashboards. The fix is making questions directly answerable.
AI in the Entrepreneur’s Daily Life – What’s Really Changed
As a two-person founding team, Nico and his co-founder can now do work that would have either been left undone or required external resources a small team simply doesn’t have.
Concretely: filtering 5,000 relevant companies from a LinkedIn connection list. Automatically qualifying new signups – which company do they work at, what problem might they have, are they a fit? A Python script that would have meant half a day of manual work now gets built in minutes.
Nico says it plainly: it has revolutionized every part of his work. Not in the sense of “I don’t have to think anymore.” Quite the opposite – the quality of his own thinking is now the bottleneck, not the execution of manual tasks.
Thesis 1: AI doesn’t take away jobs. It enables work that simply didn’t happen before – because the resources weren’t there.
Thesis 2: With AI support, you don’t become more efficient at what you were already doing. You can suddenly do things that were simply out of reach before.
The Addiction Factor – and Why Distance Still Matters
Nico runs. A lot. Trail running in the mountains whenever possible. And he travels. Montenegro, Bali. Not as a break, but as a necessary change of contrast.
The background: when repetitive work disappears and almost only strategic thinking remains, mental clarity becomes the real bottleneck. Before, you could “switch off your brain and just do.” That’s no longer possible.
At the same time: AI tools have an extreme addiction factor. Fast results, constant dopamine hits – bang, result. Another iteration, bang, better. Markus directly compares it to social media. And hits a nerve.
Naval Ravikant has a fitting tweet: “Play long-term games with long-term people.” That’s exactly the opposite of the hustle-ADHD currently running through AI circles.
Thesis 1: The more powerful AI tools become, the more important the rhythm around them becomes. Whoever doesn’t actively shape that, burns out.
Thesis 2: Staying outside your own bubble matters strategically right now – not just personally. Living only inside the AI-early-adopter world means losing the feel for what most people actually need and understand.
Signal vs. Noise – How Not to Lose the Plot
Everyone has FOMO right now. The biggest names in the space included. The question is no longer whether you’re missing something – but how to stay able to act anyway.
Nico’s answer: find three or four people who don’t share opinions but show how they do things. Follow them. Tune out the rest.
Thesis: Going deep on AI tools tactically is one of the most strategic moves you can make right now. Whoever understands how these tools actually work has a fundamental advantage – just like at the rise of the internet or mobile.