Skip to content
Drako Podcast

Episode 09 · Customer journey mapping · Cross-regional

What the Product Tells You

Customer journey mapping with product analytics — why the journey map, not the dashboard, is the operating document of a growth-stage startup.

This episode is scheduled. Audio, transcript and video highlight publish with the episode.

Why this episode, why now

Every startup now has a product analytics tool. Very few have a customer journey map that the engineering team and the marketing team both recognise as the description of the business. The tool is installed in an afternoon; the map takes weeks of argument about what an "activated" user actually is. This episode is about the second thing, and about why the first thing is worthless without it.

The tooling has changed in two ways that make this the moment to talk about it. First, the category has consolidated around a small number of platforms with generous free tiers — PostHog bundles analytics, session replay, feature flags and experiments in one open-source stack and says most of its customers never leave the free plan; Mixpanel moved to event-based pricing in early 2026; Amplitude remains the deep-behavioural choice for larger teams. The constraint is no longer access to data. Second, the 2026 Aleph × Benchmarkit report, built on full-year 2025 actuals from 342 SaaS and AI-native companies, puts the median CAC payback at 16 months — with a top quartile at six months or less and a bottom quartile at 24 months or more. That spread is not explained by tooling. It is explained by whether a company knows where in its journey users convert, stall and churn, and whether it acts on that every quarter.

Daniel's training was in marketing and information systems, taken together, and his early career ran through digital agencies and seed-stage startups in London, Singapore and Sydney — the environments where the marketing team and the engineering team argue about what the numbers mean. Customer journey mapping is the fifth stage of the Drakopoulos Ventures engagement framework: mapping every step from first touch to retention, and the systems behind each. The firm's SaaS case study — an automated funnel architecture for user acquisition, mapped across the funnel and tracked against conversion and customer acquisition cost, reviewed quarterly — is the worked example this episode returns to.

The thesis is plain. Instrument the product before you market it. Agree the event taxonomy jointly between engineering and marketing. Write the journey down. Then let the quarterly review read the journey rather than the dashboard.