Newsletter comparison
Lenny's Newsletter vs MKT1 Newsletter with Emily Kramer
Short answer: Choose Lenny's Newsletter if product and growth leadership is the broader job. Choose MKT1 if you are building or repairing a B2B marketing team. Read both when product and marketing decisions must line up week by week.[1][2][3][4][5][6]
An independent guide. Scottie isn't affiliated with, endorsed by, or sponsored by Lenny's Newsletter and MKT1 Newsletter with Emily Kramer. Each publication owns its name, writing, and subscription terms.
A brief from both newsletters · July 31, 2026
See both newsletters in one brief
See what made the brief, what didn't, and the original links behind every included story.
In this brief: Scottie kept the selected stories separate because they added different value.
Reader priorities
A software leader needs practical guidance for building a product people want and a marketing function capable of creating demand.
These are illustrative priorities, not a customer’s data.
What made the brief
- Lenny's Newsletter6 read · 4 included
- MKT1 Newsletter with Emily Kramer1 read · 1 included
Scottie
Scottie example brief
July 31, 2026 · Executive brief
01 / The rundown
- Transitioning marketing teams from single-player AI workflows to shared setups accelerates demand generation and prevents isolated work silos.
- Anthropic's first technical PM shares how eval-driven development loops powered model releases from Claude 2 to Fable.
- Hands-on benchmarks of Claude Opus 5 reveal top-tier intelligence alongside quirks like verbose outputs and strict code refusal boundaries.
02 / The briefing
01 / main
Stop running AI in single-player mode for team marketing
The takeaway: Individual marketers building solo prompts creates messy silos. Scaling demand generation requires a shared multiplayer setup using Claude Code, a centralized GitHub repository, and shared context files so prompt improvements instantly boost team productivity.
Concrete details
- Over 100 marketing leaders cited team adoption and system ownership as bigger hurdles than technical setup.
- The strategy combines three Claude interfaces with a shared GitHub repository and living context files.
Why it matters for this reader: As a software leader building a demand-generation engine, shifting from isolated prompts to shared AI capabilities stops your marketing team from re-solving identical growth problems.
Original sourcesMKT1 Newsletter with Emily Kramer
02 / main
Inside Anthropic's product machine with its first technical PM
The takeaway: Dianne Penn joined Anthropic in 2023 as its first technical product manager alongside just five engineers. She details how an eval-driven development loop helped incubate tools like Claude Code, MCP, and Skills while navigating fast-paced model releases.
Concrete details
- Dianne Penn joined Anthropic in 2023 when the product team consisted of just five engineers.
- Penn's team helped ship every model from Claude 2 through Fable and incubated Claude Code and MCP.
Why it matters for this reader: Building AI products people actually want requires systematic shipping frameworks; Penn's technical PM tactics offer a playbook for leading high-velocity engineering teams.
Original sourcesLenny's Newsletter
03 / main
How to escape pilot purgatory and sharpen product discovery
The takeaway: Staying relevant during slow enterprise sales cycles requires structured touchpoints without pushing hard closes. Software teams are combining product discovery tools directly with Linear while setting clear boundaries around what AI should and shouldn't automate.
Concrete details
- Community insights focus on structured client engagement tactics during long pilot cycles.
- Tactical workflows cover pairing Linear with product discovery tools to simplify backlog planning.
Why it matters for this reader: Keeping prospect deals alive during extended pilots is vital for validation and demand, directly backing your goal of building software people buy.
Original sourcesLenny's Newsletter
04 / main
Claude Opus 5 review: high intelligence with extra neuroticism
The takeaway: Opus 5 shines on benchmark tests but brings a conversational verbosity problem and occasional stubbornness, like refusing to resolve specific git merge conflicts. It swept top scores in one specific task while competing against GPT-5.6 Sol and Gemini 3.1 Pro.
Concrete details
- Opus 5 was benchmarked across seven models and six distinct tasks in blind scoring tests.
- The model earned straight 5s in one specific use case despite struggling with code merge conflicts.
Why it matters for this reader: When evaluating next-gen LLM backends for your product stack, knowing where Opus 5 excels versus where its verbosity wastes tokens saves development budget.
Original sourcesLenny's NewsletterLenny's Newsletter
Action items
- Set up a shared GitHub repository for marketing skills to transition AI workflows from single-player to team-wide automation.
- Audit your software product's AI architecture against Opus 5 benchmark results to optimize model selection for complex tasks.
See every issue behind this brief
Transitioning marketing teams from single-player AI to multiplayer mode
- Marketing teams are stuck in single-player Claude mode. Here's how to go multiplayer.MKT1 Newsletter with Emily Kramer · Included
Product leadership and shipping AI models at Anthropic
- Anthropic’s first technical PM on token maxing, the jagged edge, and living in the future | Dianne PennLenny's Newsletter · Included
Navigating pilot purgatory, product discovery, and AI automation limits
Hands-on analysis and benchmark reviews of Claude Opus 5
- 🎙️ How I AI: Claude Opus 5 Review + Browser use in Codex + How Cursor and a Raspberry Pi makes AI funLenny's Newsletter · Included
- Claude Opus 5 review: this model is brilliant (but annoying)Lenny's Newsletter · Included
Lenny Product Pass expansion
- 11 products I love, free for a year—the biggest Product Pass expansion in 2 yearsLenny's Newsletter · Read, not included
Cursor and Raspberry Pi
- From zero coding background to hardware hacker: How Cursor + a Raspberry Pi makes AI funLenny's Newsletter · Read, not included
The useful difference
The difference that matters
Lenny's Newsletter ranges across product, growth, and team leadership. MKT1 goes deeper on B2B marketing design: org structure, programs, positioning, and the systems behind execution.[1][2][3][4][5][6]
What each is best for
Lenny's Newsletter
Lenny's Newsletter offers a wide operator view of product discovery, growth loops, hiring, management, and new software tools.[1][2][3]
MKT1 Newsletter with Emily Kramer
MKT1 supplies the sharper B2B marketing lens, from running field events to organizing teams around shared AI-assisted work.[4][5][6]
When it’s worth reading both
The pair is useful when a product insight changes the go-to-market plan—or a demand problem exposes a product problem. Scottie can keep those connections while separating advice meant for different owners.[1][2][3][4][5][6]
Sources and official links
- Lenny's Newsletter official publication
- Everyone should be using Claude Code more
- 11 products I love, free for a year—the biggest Product Pass expansion in 2 years
- MKT1 Newsletter with Emily Kramer official publication
- Dinners are the new trade shows. Here’s how to run them well
- Marketing teams are stuck in single-player Claude mode. Here's how to go multiplayer.