Month: December 2025

Vibe Check Part 3: 5 Costly Vibe Marketing Mistakes—and How I Use AI to Avoid Them

Vibe marketing can electrify a brand, but it can also derail a strategy if it outruns the fundamentals. I have seen campaigns with breathtaking creative fall flat because the message had no anchor in product truth, no measurable goals, and no operational guardrails. In this installment, I share the patterns I watch for, the diagnostics I run, and the AI tools I use to keep the vibe aligned with outcomes.

Learn how to avoid the five most common mistakes in vibe marketing to have more success with AI marketing tools.

At its best, vibe marketing translates product positioning and value proposition into an emotional signal customers immediately recognize. At its worst, it becomes mood without meaning. The difference is disciplined product management: clear go-to-market strategy, outcomes vs output OKRs, rigorous A/B testing, and a feedback loop that connects creative choices to customer behavior.

Mistake 1: Mistaking mood for strategy. Early drafts often lean on catchy lines or trending aesthetics that don’t map to customer jobs-to-be-done or competitive differentiation. When I feel that drift, I force the team to articulate the core product promise, restate the positioning, and tie each headline to a measurable outcome. If a message cannot be traced to a specific hypothesis, audience, and metric, we rewrite it before it ships.

Mistake 2: Chasing trends instead of customer truth. Vibes built on whatever is viral this week rarely compounding learnings. I push for continuous discovery with interviews, in-product surveys, and sentiment analysis, then let gen ai generate multiple narrative variants grounded in actual quotes and objections. We evaluate with A/B testing and an explicit minimum detectable effect so we don’t declare victory on noise. That keeps our experimentation eval-driven, not anecdote-driven.

Mistake 3: Measuring vanity, not meaning. Reach and likes can be directional, but I optimize for activation, time-to-value, retention analysis, and conversion lift across the funnel. I instrument journeys in a unified analytics platform with Amplitude analytics and CRM integration so we can connect vibe exposure to outcomes. If the creative lifts click-through but hurts downstream activation, it’s not working—no matter how cool it looks.

Mistake 4: One vibe for every segment and channel. Audiences experience value differently, so the same creative rarely works in ads, landing pages, and in-app guides. I use LLMs for product managers and CustomGPT workflows to adapt the message by segment and stage, then validate with product tours, in-app prompts, and targeted lifecycle emails. The goal is coherence, not uniformity: a consistent story tuned to the context where decisions happen.

Mistake 5: Unbounded AI experimentation. Without AI risk management and data governance, teams can unintentionally ship off-brand or non-compliant copy. I set privacy-by-design standards, define approval thresholds, and establish context window management so models stay on-brief and on-policy. We log generations, review outputs against brand guidelines, and use retrieval to ground messaging in approved claims.

My practical playbook is simple: define the hypothesis tied to positioning, generate creative options with gen ai, pre-qualify with qualitative feedback, run A/B tests with clear success criteria, and iterate only on variants that move a business metric. Product trios align weekly on learnings so marketing signals and product-led growth motions reinforce each other. When the vibe matches the value and the data, momentum compounds.

Vibe marketing is not the opposite of rigor; it is rigor expressed emotionally. With the right AI strategy, measurement discipline, and governance, the creative spark becomes a durable advantage—and your brand earns the right to keep the spotlight.

Inspired by this post on Amplitude – Perspectives.

December 4, 2025
From No-Code Hack to 10,000 Weekly Calls: Inside Perk’s Voice AI That Actually Works

I love real-world AI that ships, scales, and actually solves painful customer problems. This story checks every box. As a product leader who has brought agentic AI to production environments, I was captivated by how a small, focused team at Perk took a no-code voice AI prototype and turned it into a system that reliably makes 10,000+ calls per week to prevent failed hotel payments.

What happens when you combine a real customer problem, a no-code prototype, and a team willing to listen to every single call?

Steven Payne (Product Manager), Gabriel Stock (Senior Engineering Manager), and Philipe Steiff (Senior Software Engineer) from Perk share how they built a voice AI agent that calls hotels to verify virtual credit card payments, preventing travelers from arriving to find their rooms unpaid. This is a textbook example of linking operational pain to a high-leverage AI solution.

What started as a hackathon experiment in Make.com became a production system handling over 10,000 calls per week across multiple languages. Along the way, the team learned hard lessons about prompt engineering for voice (numbers, pronunciation, and a very "Karen-like" first version), how to break a single monolithic prompt into structured conversation stages, and why listening to actual calls beats any amount of theorizing.

From a product management perspective, this approach aligns perfectly with eval-driven development and continuous discovery. Structure the problem, instrument aggressively, ship safely, then listen—deeply—to real interactions. In my own teams, I’ve seen that nothing accelerates iteration on agentic AI like closing the loop between qualitative call reviews and quantitative evals.

They built a working prototype without writing a single line of backend code.

They structured the call into discrete stages (IVR, booking confirmation, payment) to improve reliability.

They created two eval systems: one for call success classification, another for conversational behavior.

They scaled from five calls a day to tens of thousands per week while maintaining quality.

This is a detailed look at building AI for real-time human interaction—where the stakes are high and the feedback is immediate.

Guests: Steven Payne, Product Manager, Perk; Gabriel Stock, Senior Engineering Manager, Perk; Philipe Steiff, Senior Software Engineer, Perk.

What stood out to me was how Perk's team identified an AI use case by connecting prior experimentation with a real operational problem. Why they chose Make.com for prototyping—and shipped to production without touching backend code—underscores how far no-code can take you when paired with crisp problem framing. The evolution from a single prompt to structured conversation stages (IVR handling, booking confirmation, payment request) is exactly how you harden agent behavior for production.

Breaking up the agent's task dramatically improved reliability. They also built two eval systems: classification for success rates and LLM-as-judge for conversational behavior. Even with automation, the team still listens to calls manually—a practice I strongly endorse for uncovering edge cases, trust issues, and UX nuances that dashboards can’t show.

The challenge of prompt engineering for voice—numbers, booking references, and text-to-speech markup—was non-trivial. Expanding to German revealed that prompts in native language improve results. And, as often happens with operations-heavy rollouts, this project uncovered other operational problems they didn't know existed—valuable signal for the roadmap.

Resources & Links: Perk. Make.com — No-code automation platform used for the prototype. Twilio — Voice/telephony provider. Eleven Labs — Text-to-speech provider (used in early experiments).

Chapters: 00:00 Introduction to the Team; 01:54 Understanding PERK's Mission; 02:59 Challenges in Travel Booking; 07:27 AI Solutions for Customer Care; 09:52 Prototyping with AI and Voice; 17:00 Implementing AI in Production; 25:51 Learning Through Trial and Error; 26:40 Prompting Challenges and Solutions; 27:58 Iterating on Prompts and Evaluations; 30:08 Scaling and Production Challenges; 32:43 Advanced Evaluation Techniques; 35:32 Real-World Applications and Success; 49:07 Future Directions and Expansion; 53:53 Conclusion and Team Reflections.

My product takeaways: Start with clear operational pain and measurable outcomes (e.g., payment verification). Use no-code to validate quickly, then progressively harden. Treat voice AI like any production system: break it into deterministic stages, add guardrails, and measure both outcome and behavior. Pair automated evals with hands-on reviews. And when going multilingual, write prompts in the native language—your accuracy will thank you.

If you’re exploring agentic AI for operations, this is the blueprint: tight scoping, Make.com for speed, Twilio for reliability, structured prompts for control, and an eval-driven loop to scale quality with confidence.

Inspired by this post on Product Talk.

December 4, 2025
Unlocking the 7% Retention Rule: How Early Activation Fuels Compounding, Long-Term Growth

I’ve learned to spot durable growth early. When we launch something new, I look for one deceptively simple signal that predicts whether the product will compound or stall: the percentage of users who come back one week later. It’s a small number with big implications for product-led growth and retention analysis.

Discover why 7% of users returning after one week signals long-term growth, and how early activation separates top-performing products from the rest.

Why does this matter so much? A 7% day-7 retention floor tells me we’ve earned a second interaction from a meaningful slice of our cohort, not just a curiosity click. That’s the first hint of habit formation and repeatable value—evidence that onboarding, user activation, and the core value proposition are doing their job. When the curve holds at or above this threshold, growth investments tend to work harder because cohorts keep giving back.

The lever behind that signal is early activation. I define the activation moment as the first time a new user experiences product value—sending a first campaign, integrating a CRM, or completing a workflow that solves their primary job. If we reduce time-to-activation and increase the activation rate, day-7 retention rises. This is where in-app guides, product tours, and thoughtful tooltip design shine: they remove friction without overwhelming the user.

Instrumentation is non-negotiable. I set up event tracking and cohort analysis in tools like Amplitude analytics and Pendo, define a crisp activation event, and review retention curves by first-seen cohorts. We run A/B testing with a clear minimum detectable effect (MDE), validate improvements in activation and day-7 retention, and then double down. The objective is always outcomes over output: fewer features, more value delivered.

Process matters as much as tooling. Product trios using continuous discovery keep us close to user problems, while empowered product teams move faster with context and clear outcomes vs output OKRs. When we connect these practices to a unified analytics view, it becomes obvious which changes move the 7% needle and which are noise.

In practice, I’ve seen a launch turn the corner by clarifying the “aha” moment, cutting onboarding steps nearly in half, and swapping a generic walkthrough for contextual in-app guides. Activation jumped, day-7 retention crossed the threshold, and suddenly our PLG motion became efficient—paid acquisition started compounding instead of leaking.

If you’re below 7%, start by tightening the activation definition, instrument the funnel, and remove the top three sources of friction. If you’re above 7%, stabilize it across segments, scale with targeted in-app guides, and keep iterating via A/B tests to protect that early win. Either way, the rule provides a clear, pragmatic checkpoint for product discovery and growth.

The takeaway is simple: focus the team on earning the second visit. Nail early activation, then build repeatable systems that make the 7% retention rule your new baseline for confident, long-term growth.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Stop the Leaky Bucket: Proven Moves to Turn User Growth into Durable Retention in 2025

More signups are exhilarating—until the retention curve tells a colder truth. I’ve led launches where top-of-funnel spiked, only to watch active usage slide week over week. That’s the leaky bucket problem in action: acquisition outpaces activation, engagement, and retention, so net growth stalls.

Losing users as fast as you acquire them? Get exclusive insights from our 2025 Product Benchmark Report on how to fix the leaky bucket problem and drive lasting growth.

When I assess a product’s trajectory, I reframe the goal: our job isn’t to add users; it’s to create retained value. In product-led growth, durable growth comes from systematically increasing activation and Day 7/30 retention, not just traffic. That shift aligns teams on outcomes vs output and turns experiments into a compounding engine.

Diagnosis comes first. I run a retention analysis by cohort in Amplitude analytics (and corroborate with Pendo for in-app behavior) to pinpoint where the flow breaks: sign-up, onboarding, first value, habit formation, or paywall. Then I define a crisp activation metric—what specific action within a time window predicts long-term engagement—and measure time-to-value for each segment.

From there, we remove friction. Simplify onboarding, trim non-essential fields, and guide users to the “aha” with in-app guides, product tours, and contextual tooltips. Seed accounts with sample data, pre-built templates, and smart defaults so new users experience the core value in minutes, not days.

We prove impact with disciplined experimentation. A/B testing with a clearly calculated minimum detectable effect (MDE) prevents false positives, while a continuous discovery cadence with product trios keeps us close to real customer problems. Every test is tied to leading indicators—activation rate, Day 1/7/30 retention, and weekly engaged usage—not vanity metrics.

Activation does not live in product alone. Pricing and packaging, lifecycle messaging, and customer support all influence early habit formation. Align GTM and product on one retention-centric scorecard and instrument a unified analytics platform so every team sees the same truth.

Once the core journey holds water, we layer in expansion: prompts that surface adjacent value at the right moment, educated upsells tied to outcomes, and permissions or collaboration features that invite team adoption. That’s how growth becomes efficient and compounding instead of brittle and expensive.

If this resonates, you likely have more of a prioritization problem than a traffic problem. Fix activation, measure retention rigorously, and let acquisition follow. Patch the leaks, and growth stops being a hustle—and starts being a flywheel.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Unify Your Analytics to Accelerate Growth: Cut Costs, Boost Clarity, and Decide in Real Time

I’ve led product teams through the pain of scattered dashboards and contradictory metrics, and I’ve seen how it slows decision velocity and quietly inflates costs. When insights are fragmented, roadmaps drift into opinions and meetings multiply. A unified analytics platform changes the conversation—from noise to signal, from lagging to leading indicators, and from guesswork to confident execution.

"Escape fragmented tools with a unified analytics platform that accelerates growth, reduces costs, and empowers smarter, real-time decision-making."

Here’s what “unified” means in practice: one source of truth that connects product usage, marketing attribution, sales pipeline, and customer support signals. With CRM integration, consistent event taxonomy, and retention analysis in place, every team works from the same playbook. Cohorts, funnels, and lifecycle metrics become part of daily rituals, and insights flow directly into product discovery and go-to-market decisions.

The impact is tangible. Product-led growth becomes predictable because activation, engagement, and retention are measured the same way across functions. Experimentation accelerates as A/B testing cycles tighten and learning compounds. Outcomes vs output OKRs stay visible and honest, helping us prioritize what moves the needle. Costs come down as redundant tools are rationalized and manual data wrangling disappears. Most importantly, real-time decision-making replaces weekly retrospectives with timely action.

My playbook for getting there is straightforward: start with a tool and data audit; define a clear north-star metric with a handful of leading indicators; standardize event names and properties; connect the data layer to your CRM for closed-loop visibility; instrument product tours and in-app guides to drive user activation; and institutionalize continuous discovery so every insight informs the roadmap and sprint planning.

Governance and trust matter as much as dashboards. Invest in data governance and a clean tracking taxonomy so metrics are trusted across the organization. Document definitions, automate quality checks, and maintain privacy-by-design from the start. The goal isn’t more data—it’s better decisions, faster, with confidence.

I’ve watched teams cut time-to-insight from days to minutes, reallocate budget from underperforming channels to winning ones, and ship with far greater conviction. When the organization rallies around a unified analytics platform, stakeholder debates shrink, velocity increases, and the value proposition to customers sharpens.

If growth, cost savings, and smarter decision-making are on your agenda this quarter, commit to unifying your analytics. Start small, prove the value in one journey (like activation to retention), then scale. The moment you align your teams to a single source of truth is the moment your product strategy becomes unmistakably clear.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Crack the AI Search Code: How Startups Win Recommendations in ChatGPT and Perplexity

AI search is reshaping how customers discover emerging products, and I’ve seen firsthand how this shift rewards startups that speak clearly to both humans and machines. Learn how LLMs like ChatGPT and Perplexity decide which startups to recommend and what signals help a brand get discovered in AI search.

In practice, AI search behaves less like a list of blue links and more like a synthesis engine. These models look for credible, consensus-backed, well-structured sources they can cite with confidence. That means your brand’s discoverability hinges on technical clarity (schema, structure, speed), topical authority (depth, citations, expert bylines), and evidence of real-world adoption (reviews, case studies, third-party validation).

I start by mapping buyer intent across the entire journey—category exploration, problem framing, solution fit, integration needs, ROI, and competitive comparisons. Then I design a page system that answers each intent with precision: clear “About” and “Use Cases” pages, integration-specific pages, objective "X vs Y" comparisons, transparent pricing, and a living FAQ that mirrors the exact questions users ask in conversational queries.

Structure matters. I add JSON-LD schema for Organization, Product, FAQPage, HowTo, and Article where appropriate; keep canonical URLs consistent; and ensure titles, meta descriptions, and Open Graph data reinforce the same story. Clean sitemaps, a sensible robots.txt, and fast, mobile-first performance reduce friction for crawlers and increase the odds that LLMs extract accurate snippets.

Authority is earned off-site as much as on-site. I prioritize third-party signals—G2/Capterra reviews, analyst mentions, reputable press, open-source repos with README clarity, academic or industry citations, and credible partner integrations. LLMs heavily weight these external proofs when recommending solutions, especially for B2B and regulated categories.

On your site, demonstrate expertise. I include expert bylines with real credentials, cite primary sources, showcase customer outcomes with verifiable metrics, and make methodologies transparent. Shallow, keyword-stuffed posts don’t help; comprehensive, up-to-date explainers with references do.

Make your content retrieval-friendly. LLMs favor text they can segment, anchor, and quote. I structure pages with descriptive headings, short paragraphs, and linkable anchors; offer HTML-first documentation (not just PDFs); and provide copyable code or configuration steps when relevant. This also sets you up for a retrieval-first pipeline in your own product experiences.

From a product and platform angle, I expose trustworthy documentation and a clear trust center—security, compliance, data governance, and privacy-by-design content. When a user asks an LLM whether they can safely deploy your solution, these pages often get pulled into the answer.

Evaluation closes the loop. I run an eval-driven development process for content: a stable prompt set that mirrors real queries, regular tests in both Perplexity and ChatGPT, and analytics to track referrals from AI-driven sources. I iterate headlines, schema, and on-page structure, then tie changes back to engagement and pipeline using A/B testing where it’s appropriate.

Don’t neglect comparison and alternatives pages. Fair, well-cited pages that address trade-offs and points of parity build trust—and they give LLMs succinct, quotable language for recommendation contexts. Clarity beats hype every time.

Finally, keep your corpus fresh. I schedule quarterly content reviews, retire outdated claims, and highlight release notes and integration updates. Freshness signals help models favor your content when they resolve time-sensitive queries.

If you treat AI search as a product surface—one that rewards precision, provenance, and performance—you’ll dramatically increase your odds of being recommended where it matters. That’s how I operationalize AI discovery for startups: intent mapping, structured content, external authority, a retrieval-friendly corpus, and a rigorous eval loop.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Stop Chasing New Users: The Surprising ROI of Win-Back Campaigns That Actually Work

Over the years, I’ve learned that the most overlooked growth lever isn’t a shiny new channel—it’s bringing back the customers we already earned. When I rebalanced budgets from top-of-funnel acquisition to reactivation, the payoff was faster, more predictable, and far more cost-efficient. Reactivation compounds because it’s built on trust, product familiarity, and data we already have.

Discover why reactivating dormant users delivers better ROI than new acquisition. Learn how to identify and bring back at-risk users via targeted campaigns.

Why does this work so well? Dormant users once saw enough value to sign up, activate, or even pay. The barriers to return are lower: familiarity reduces friction, time-to-value shrinks, and the cost to engage is a fraction of new-user CAC. In practice, I’ve seen win-back motions outperform new acquisition on payback time, expansion potential, and long-term retention—especially when we design the right triggers and messages.

My approach starts with rigorous retention analysis. I define the behaviors that signal risk—declining frequency, shrinking session depth, stalled onboarding milestones, or missed “aha” moments—and map them to lifecycle stages. Using a unified analytics platform with CRM integration, I can see who’s drifting, when, and why. That clarity is the foundation for precision reactivation.

On the tooling front, I lean on Amplitude analytics to surface cohorts and leading indicators, Pendo for in-app guides and nudges, and Intercom for lifecycle messaging and human-assisted outreach. The connective tissue is our CRM integration, which ensures we coordinate messages across email, in-app, and sales-assist without creating noise or duplication.

Segmentation is where win-back campaigns gain power. I group users by their last successful use case, plan tier, activation depth, and the specific friction they hit. Cohorts often include “stalled onboarding,” “lapsed power users,” and “trial expired with partial success.” Each segment gets a distinct path back to value—never a one-size-fits-all blast.

Targeted campaigns are then matched to the root cause. For stalled onboarding, I deploy product tours and in-app guides that remove a single key blocker. For lapsed power users, I emphasize newly shipped capabilities tied to their historical workflows. For price-sensitive cohorts, I test usage-based offers or limited-time boosts aligned to value realization, not discounting for its own sake. Every flow is A/B testing-driven and time-bound, with clear exit criteria.

Measurement goes beyond “did they log in.” I track reactivation rate, feature adoption depth, time-to-value, and near-term expansion signals. Holdout groups validate lift, and we set guardrails so campaigns don’t cannibalize healthy cohorts. Over time, these learnings inform product roadmap decisions—what to simplify, what to sunset, and where to invest to prevent churn in the first place.

Operationally, I embed win-back into product-led growth rhythms. Product, data, lifecycle marketing, and support align on weekly reviews, using shared dashboards to tune triggers and content. This creates a reliable growth engine that respects user intent and avoids the trap of overmessaging.

Finally, trust matters. I build reactivation with privacy-by-design principles, transparent value propositions, and easy opt-outs. The goal isn’t to “get the login”—it’s to restore momentum toward outcomes the user cares about.

If you’re feeling acquisition fatigue, shift a meaningful slice of budget and attention to reactivation. In my experience, it delivers faster wins, better unit economics, and a healthier product that keeps more of the customers you worked so hard to earn.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
A Product Strategist & Evangelist’s Playbook at Amplitude: Turning Analytics into Growth

I’ve long believed that the Product Strategist & Evangelist role is where analytics meets impact. When I work with teams using Amplitude, my focus is simple: turn product data into decisions that compound, and tell the story in a way that mobilizes people—customers, stakeholders, and empowered product teams alike.

At its core, this role aligns product strategy with business outcomes. I anchor planning to outcomes vs output OKRs, partner closely with product trios, and run continuous discovery to ensure every roadmap item is tied to a measurable customer problem and value proposition. That discipline keeps us honest about what moves the needle.

Analytics is the engine. I start with a clean event taxonomy, dependable instrumentation, and a self-serve insight layer in Amplitude analytics. From activation to retention analysis, I define a few sharp metrics that predict sustainable product-led growth—then I build dashboards the whole organization can trust and use.

Experimentation is where insight becomes action. I operationalize A/B testing with clear hypotheses, guardrails for minimum detectable effect, and crisp success criteria. The goal is speed with rigor: learn fast, ship what works, and retire what doesn’t. Over time, this creates a culture where teams default to evidence rather than opinions.

Evangelism turns analytics into momentum. I practice developer evangelism to meet practitioners where they are, and I translate complex findings into accessible narratives for executives and customer-facing teams. That means live walkthroughs, in-app guides, product tours, and field enablement that shows not just the what, but the why and the how.

Under the hood, a unified analytics platform is essential. I pair it with pragmatic data governance and privacy-by-design so we can scale insights confidently. The result is a flywheel: reliable data, repeatable workflows, and reusable patterns that accelerate every subsequent initiative.

On the go-to-market front, I connect product strategy to positioning, packaging, and enablement. The stories we tell in the market should mirror the value we measure in the product. That alignment makes launches sharper, sales motions clearer, and adoption smoother.

In practice, my playbook is straightforward: clarify the North Star and adjacent metrics, stand up trustworthy pipelines and dashboards, institutionalize experimentation, and continuously translate insights for decision-makers. Done well, analytics stops being a report and becomes a system for growth.

If you’re building or evolving this function, start small and intentional: instrument the few events that matter, ship one meaningful A/B test, and circulate a concise narrative on what you learned. Consistency beats complexity, and momentum compounds quickly when teams see their decisions move the metrics that matter.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Slash Time to Value to Skyrocket Retention: A Proven Playbook for Faster Impact

I’m relentlessly focused on time to value because it’s the fastest, most reliable lever I have to drive user retention and product-led growth. When new users experience an unmistakable win quickly, they stick around, explore deeper features, and become advocates. When they don’t, the best onboarding or marketing can’t save the experience.

Accelerate retention by reducing time to value. Learn how faster product impact drives growth, reduces costs, and keeps users engaged in the long term.

Here’s how I define it in practice: time to value (TTV) is the elapsed time between a user’s first meaningful interaction and the first moment they feel the product’s core value. That “aha” moment is not a vanity milestone; it’s a measurable behavior that correlates with long-term retention in your retention analysis and cohort curves.

In my role leading product teams at HighLevel, I treat TTV as a leading indicator for retention and expansion. It shapes our product discovery, influences our value proposition, and anchors our outcomes vs output OKRs. If a roadmap item doesn’t shorten TTV or deepen recurring value, it rarely makes the cut.

My playbook for reducing TTV starts by identifying the activation metric—what’s the smallest observable action that best predicts retention? For a messaging product it might be sending the first message to three contacts; for a workflow tool, publishing the first automated flow. Once this activation is clear, the job becomes simple: engineer the shortest, most delightful path to that outcome.

Next, I eliminate onboarding friction. I default to progressive profiling instead of long forms, ship sensible defaults, preload sample data, and offer ready-to-use templates. I complement this with lightweight in-app guides, product tours, and well-timed tooltip design—just enough guidance to build momentum without overwhelming the user.

To validate changes, I rely on rigorous experimentation. A/B testing with a defined minimum detectable effect ensures we’re not overfitting noise. I track activation rate, time to first value, feature adoption, and day 7/30 retention. If an experiment improves activation but hurts short-term retention, I dig into the “why” with session replays, targeted surveys, and follow-up interviews.

This approach also reduces costs. Faster activation lowers support volume, decreases onboarding hand-holding, and shortens payback periods. On the GTM side, TTV-aligned messaging clarifies our value proposition, improving conversion quality and reducing churn from poorly qualified signups.

Cross-functional alignment is essential. Product, design, engineering, and customer success must agree on the definition of value, the activation metric, and the telemetry required to measure progress. I use product trios to maintain discovery momentum and ensure decisions connect cleanly to measurable outcomes.

A practical 30/60/90 plan helps teams move fast. In the first 30 days, define activation, instrument analytics, and map the current journey. By day 60, ship friction-killing improvements, launch in-app guides, and run your first A/B tests. By day 90, refine templates, tighten empty states, and codify wins into the onboarding system so improvements compound.

The biggest pitfall I see is chasing more features instead of more value, faster. When we focus on shortening the path to a single compelling outcome—and proving it with data—retention follows. Users don’t need more; they need the right result sooner.

If you’re serious about retention, make time to value your team’s most visible operating metric. Shine a bright light on it in weekly reviews, tie it to goals, and celebrate every step that helps users succeed faster. Do this consistently, and you’ll see growth accelerate, support costs drop, and engagement deepen in ways that are both measurable and enduring.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Enterprise GTM Mastery: How I Partner with Product Marketers to Drive Adoption at Scale

I spend a lot of time turning strong product capabilities into enterprise wins, and that almost always starts with a tight partnership between product management and product marketing. The most effective go-to-market strategy is built where customer insight, product value, and revenue goals intersect—and product marketers are the connective tissue that makes this real.

“Michele Morales is a product marketing manager at Amplitude, focusing on go-to-market solutions for enterprise customers”

In my experience, partnering with product marketing leaders on enterprise go-to-market means aligning early on the ICP, the value proposition, and the differentiated messaging that sales can activate. We map buyer committees, refine product positioning against points of parity and competitive differentiation, and ensure our narrative translates cleanly from website to demo to proof-of-concept.

For data-driven execution, I lean on Amplitude analytics and a unified analytics platform approach to validate our hypotheses. We set clear activation and adoption milestones, monitor user activation cohorts, and close the loop with retention analysis to understand which messages and features actually move enterprise accounts from trial to expansion. This is where product-led growth complements sales-led motions, giving us empirical signal across the funnel.

On the launch front, we pressure-test enablement and in-product experiences together: crisp messaging frameworks, in-app guides, and product tours that shorten time-to-value for complex enterprise use cases. The result is a go-to-market strategy that’s both technically accurate and emotionally resonant—clear enough for executives and actionable for end users.

What consistently works: start with real customer pain, express value succinctly, and make the path to first success obvious. Then instrument everything. When product, marketing, and sales can all see the same truth in the data, empowered product teams iterate faster, positioning sharpens, and adoption compounds.

This approach respects the craft of product marketing while grounding decisions in measurable outcomes. It’s how we turn a promising roadmap into repeatable enterprise impact—and why close PM–PMM collaboration remains one of my most reliable growth levers.

Inspired by this post on Amplitude – Best Practices.

December 3, 2025
From Stone Soup to Insights: Eval-Driven Development That Supercharges AI Analytics

I’ve learned that the most powerful AI features rarely emerge from lone-wolf brilliance—they’re born when a community rallies around a shared objective. “Building Amplitude’s AI for insight automation felt a lot like the fable of travelers making stone soup with their community.” That spirit captures how I approach shipping AI for analytics: bring focused ingredients, invite contributions, and let rigorous evaluation transform the result into something extraordinary.

At the core is Eval-Driven Development. Rather than debating preferences, we define explicit evaluation sets, success thresholds, and guardrails, then wire them into CI/CD so every change improves reliability, quality, and relevance. For AI-driven analytics, our evals combine offline judgment tests (precision, recall, hallucination rates), user-centric measures (time-to-insight, actionability), and production health signals (failure modes, latency). When the bar rises, the product improves—continuously and measurably.

We made “stone soup” by inviting contributions from every function. Data science established gold-standard datasets and baselines. Engineering implemented retrieval, orchestration, and safe deployment paths. Product and design framed high-value use cases, in-app guides, and UX writing that clarified intent. Customer success and support piped real-world edge cases into our evals so the system improved where it mattered. Product trios kept us outcome-focused and empowered product teams moved quickly without sacrificing governance.

Why this matters for analytics: AI insight automation reduces the heavy lift of exploring funnels, cohorts, anomalies, and retention patterns—accelerating activation and product-led growth. With a unified analytics platform and strong data governance, we can surface relevant patterns proactively, explain the “why” behind movements, and recommend next best actions without drowning users in noise. The result is faster decisions, cleaner handoffs between teams, and a tighter loop from observation to intervention.

Our practical playbook is simple but strict: define a clear north-star outcome; curate representative eval sets that mirror real user questions; simulate A/B testing offline before live traffic; instrument time-to-insight and adoption; and integrate evals into CI/CD so regressions never ship. We monitor DORA metrics to maintain delivery velocity while holding quality lines, and we use human-in-the-loop review to continuously refine prompts, patterns, and explanations.

We also learned what doesn’t work. General-purpose prompts seldom transfer cleanly to analytics without domain grounding and context window management. A retrieval-first pipeline improves factuality, but only if metadata and event taxonomies are consistent. And while generative UX can delight in demos, it must earn trust in production through transparent reasoning, privacy-by-design, and predictable behavior under load.

In the end, the stone soup metaphor isn’t about cute storytelling—it’s about disciplined collaboration. When a cross-functional community contributes the right ingredients and Eval-Driven Development keeps us honest, AI for insight automation becomes both credible and compounding. That’s how we turn analytics into action—and how we ship AI products that users rely on every day.

Inspired by this post on Amplitude – Best Practices.

December 3, 2025
Unlock Instant Product Answers: How AI-Powered Resource Centers Elevate In‑App Help

I’ve spent years watching users bounce between product screens, docs, and support tickets when they hit a roadblock. The fastest path to value is always the same: deliver relevant, contextual help exactly when and where the user needs it. That’s why I’m excited about the next wave of in-app guidance that blends behavioral data with AI to anticipate intent and remove friction in real time.

Announcing Resource Centers, Amplitude’s newest in-product help feature that uses behavioral data and AI to serve help content users actually need.

Here’s why that matters. In a product-led growth model, in-app guides, product tours, and just-in-time tips are essential to onboarding and user activation. When help content is informed by real behavioral signals—events, cohorts, milestones—it stops being a static knowledge base and becomes a living system that adapts to a user’s journey. That means fewer context switches, faster time-to-value, and more confident users who can self-serve their way to outcomes.

In practice, the most effective resource centers are opinionated and contextual: they surface content by role, plan, and lifecycle stage; trigger nudges based on key events; and offer multiple modalities (microcopy, short clips, interactive guides) so users can choose how they learn. They also respect pacing, avoiding notification fatigue with rate limits and prioritization rules. Think of this as high-quality UX writing paired with data-driven orchestration—useful, discoverable, and never in the way.

Execution matters. Start with a clear content taxonomy, map help assets to journey stages, and establish a content ops cadence so guides stay fresh. Partner closely with data governance to ensure privacy-by-design and transparent consent for behavioral data usage. Then wire in feedback loops—thumbs up/down, quick polls, and session replays—so you can continuously discover gaps and iterate quickly.

Measure impact with the same rigor you apply to product features. Track activation rates, time-to-first-value, self-serve resolution rates, reduction in ticket volume on targeted topics, and downstream retention. Use A/B testing to validate which interventions move the needle, and segment results to learn what works for new users versus power users. When results differ, treat that as a design signal—not a failure—and refine the targeting.

Rollout thoughtfully. Pilot with a high-friction workflow, localize the help content to the user’s context, and set clear exit criteria before scaling. Align with customer support and success so your resource center becomes the canonical source for in-app help, not yet another content silo. Over time, unify insights across Amplitude analytics and your support stack to close the loop between product behavior and help outcomes.

As product leaders, our goal is simple: reduce effort and increase confidence for every user. AI-assisted, behaviorally triggered resource centers are a pragmatic step toward that future—meeting users where they are, with exactly what they need, at the moment they need it.

Inspired by this post on Amplitude – Best Practices.

December 3, 2025