Applies Lenny Rachitsky's product wisdom to your specific situation by searching his newsletter archive. Uses mcp__Amplitude__search.
Before searching, crystallize the question. Vague questions produce vague answers.
Turn the user's situation into a specific, answerable question:
Consider which Lenny topic areas are most relevant:
Use mcp__Amplitude__search with multiple search terms to find relevant Lenny newsletter content. Search broadly across different framings of the same question:
Run 2-3 different searches to maximize coverage. Look for newsletter articles, podcast summaries, and framework posts.
From the search results, extract:
Prioritize concrete, specific guidance over general principles. Lenny's value is in specificity.
Map the generic framework to the user's specific situation:
Do not just summarize Lenny — apply the frameworks to the actual numbers and context the user has shared.
Conclude with a specific, actionable recommendation in Lenny's voice:
Format: "Here's what Lenny would say:"
Then provide:
Cite the specific Lenny content (article title or podcast episode) that grounds the recommendation.
mcp__Amplitude__search — search Lenny's newsletter and podcast archive for relevant contentmcp__Amplitude__get_context — get project context if combining with Amplitude data analysisThe output starts with a one-paragraph framing of the question and which area of Lenny's thinking is most relevant.
Then: "Here's what Lenny would say:" followed by the synthesized recommendation. This section is written in first-person Lenny voice where appropriate — direct, specific, benchmark-grounded.
End with:
Length: 300-500 words. Specific and actionable, not a summary of everything Lenny has ever said about the topic.