Lenny's community roundup 303: a lowball offer, designers earning a seat in product decisions, and where to build an MCP server
Lenny's Saturday member email names three threads — negotiating a lowball offer, designers earning a seat in product decisions, and building an MCP server — and this edition pairs two of them with the free answer already published.
Your Gmail queue picked up one new item since yesterday's digest: Lenny's Newsletter's Saturday community email, which landed at 23:11 last night, Shanghai time. Stratechery has filed nothing since Friday's roundup.
That email is subscriber-only. Its title is most of what anyone without a subscription can read. All three questions in that title can be taken further for free, though: two through older Lenny's posts, one through the protocol's own documentation.
One item in the queue: Lenny's Saturday community email
Community Wisdom 303 — Lenny's Newsletter
Published October 24, 2026, 23:11 Shanghai. Subscriber-only. Bylined Kiyani.
Every Saturday, Community Wisdom collects the most helpful conversations from Lenny's members-only Slack community and writes them up for paying readers. This is edition 303. 1
- Negotiating a lowball offer. The first number came in under what the role is worth. The thread is about what to do with it: how hard to push, and what pushing puts at risk. 1
- Designers earning a seat in product decisions. This one is about influence rather than output. A designer who receives the brief after the decisions were made wants to be in the room while they are made. The PM usually decides who sits in that room. 1
The title closes with "and more", which stands for threads the public page leaves unnamed. The community's own answers sit behind the paywall.
The free reading for the offer
"The 10 commandments of salary negotiation" — Niya Dragova
Free. September 24, 2021. Guest post by the co-founder of Candor. 3
- Read the offer before you argue with it. A low opening number often means the team thinks you have "room for growth", Dragova writes. Her advice is to ask for feedback from the people who interviewed you, and clear up the misunderstanding before you negotiate at all. 3
- A templated middle number says something else. She puts the share of candidates who receive the recruiter's standard opening figure above 80%. Her reading is that nobody on the interview loop is fighting for you, so hold the negotiation until a hiring manager is in your corner. 3
- Ask for the total, then the parts. Her advice is to negotiate overall compensation first, then equity, then a signing bonus, on a call rather than over email. A competing offer is optional; saying you are talking to other companies is enough. 3
The guest post closes by pointing readers to Candor's own salary-negotiation guide. 3
The free reading for the design seat
"The PM 🤝 Design Partnership" — Katie Dill
Free. March 23, 2021. Guest post by the then head of design at Stripe. 4
- The seat is won in planning. By the review meeting, the decisions are already made. Dill gives three reasons to bring designers in early: the team gets the user's voice, gets prototypes and visual storytelling, and the designer gains the context to execute faster later. 4
- "Design goals" and "business goals" are one set. Consistency, usability, accessibility and delight are what drive use, conversion and loyalty, she writes. The real work is sequencing them against each other. 4
- Trust the expertise, and change the noun. Where the call is about user experience, and the designer knows the user and the goals, she says let the designer decide. She also asks PMs to say "my design partner" instead of "my designer". 4
The MCP question has a public answer
The protocol publishes its own documentation, and for a builder that documentation answers the question better than a Slack thread would. 2
MCP is an open-source standard for connecting AI applications to external systems: local files, databases, search tools, specialised prompts. The docs describe it as a USB-C port for AI applications. 2
- There is a build path on each side. The docs cover building servers that expose your data and tools, building clients that connect to servers, and building apps that run inside AI clients. 2
- Architecture and security each have their own page. A server hands a model access to real systems, and the docs keep a security section in the same index as the build paths. 2
- The clients already exist. Claude, ChatGPT, Visual Studio Code, Cursor and MCPJam all support the protocol, so a server built once reaches every one of them. 2
Where to start
If you hold a subscription and one of those three questions is live for you this week, the community email is worth opening. The community's answers are the part nobody gets free.
The offer question and the design question each have a published answer above, written by the same newsletter, that addresses the same question. For the MCP question, start with the documentation, subscription or not.
The rest of the queue is empty. Stratechery's newest item is still Friday's weekly email, which yesterday's digest carried. 5 Lenny's published nothing else in this window.
References
- 1Community Wisdom 303 — Lenny's Newsletter
lennysnewsletter.com
- 2What is the Model Context Protocol? — Model Context Protocol
modelcontextprotocol.io
- 3The 10 commandments of salary negotiation — Lenny's Newsletter
lennysnewsletter.com
- 4The PM 🤝 Design Partnership — Lenny's Newsletter
lennysnewsletter.com
- 52026.43: A New Era — Stratechery
stratechery.com
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.