Evan Zhou

🫨

Just talked to an AI Product manager making $375K at a frontier lab. She hasn't written a PRD in 8 months. Not "she uses AI to help write them faster." She has not opened a PRD template in eight months because she just doesn't need it anymore. Her day looks nothing like what PMs do: She wakes up, opens Claude Code, and has a working prototype running before her first meeting of the day (not a wireframe or a figma mockup someone needs to hand off to an engineer). A testable version of the idea - built/shipped by her in the same morning. While that prototype is running, she's pulling model outputs and running evals. She knows what hallucination looks like in her specific use case. She knows what latency threshold breaks the user experience. She knows the token cost per query and what that means for margin at scale. She reasons about infrastructure the way a CFO reasons about a P&L. When something needs to be built for real, she doesn't go write a ticket and wait two sprints. She ships the first version herself. hands it to engineering as a working reference implementation, not a requirements doc full of edge cases nobody reads. The meetings she's in aren't about alignment. They're about what's already shipped and what's blocking the next thing. Her mental model isn't: - "manage the roadmap." - "be the voice of the customer." - "facilitate cross-functional collaboration." Those aren't wrong exactly, they're just from a different era. The mental model that gets you to $480K at a frontier lab in 2026 is simpler and harder at the same time: - You are the builder. - The agents are your team. - Your job is to ship. She said the output gap between PMs who operate this way and PMs who don't is already 3 to 4x. And this is inside a lab where literally everyone around her is working the same way. Here's the thing nobody wants to say out loud: the "I write specs and run standups" PM isn't being replaced by AI. The job isn't disappearing into a chatbot. It's being absorbed by the PM sitting two desks over who stopped waiting for engineers and started building herself. Really crazy how fast the job description changed and really crazy how few people have noticed.

@agupta hell yeah, gonna fork and try it with my setup x.com/evanczhou/stat…

Fun update: I got tired of disliking every email client I’ve ever used and built my own. It’s called Exo (for exoskeleton). It’s Claude Code for my inbox. It manages my inbox for me, and it’s open source. Link to repo + some notable features in thread!

Dps, tank, utility, healer

why did i get recommended a calculator ad and why do i want one youtu.be/YTwESBcgoyQ

@KingsongChen github.com/evanczhou/elon…

@evanczhou Cool! Are you sharing the link?

Inspired by this convo, I created an "Elon Algorithm" skill and applied it to my OpenClaw

A CEO from one of our portfolio companies shared this with their team. I’m re-sharing it with their permission, because it resonated and reflects what all founders and CEOs should be communicating. -- We are living through a period of compounding change. And in moments like this, the biggest risk is no longer making the wrong decision. It is moving too slowly while the world moves around you. There are two paths. We can play defense: - Protect what we have - Optimize what works - Wait for clarity It feels safe. It isn’t. Or we can play offense: - Learn faster than the environment changes - Use new tools to solve old problems in better ways - And create entirely new strategies and businesses That’s where the opportunity is. Challenge yourself to do things faster and better than you have ever attempted. Stay uncomfortable. Stay on the front foot.

this is excellent >GitLab founder diagnosed with rare cancer (osteosarcoma) >standard care works but cancer comes back later >medical team says there's not much else to do >"It became my own job to keep myself alive. Nobody else was going to do it for me at this point" >starts researching, assembles his own medical team, uses AI for deep research >“I’ll talk to anyone, I’ll go anywhere, and I can be there anytime" to collect information >does as many diagnostic tests as he can find as often as he can (maximal diagnostics) >develops his own therapeutic ladder with repurposed drugs, personalized medicine, etc >Sid’s cancer currently in remission

By the end of 2026, I predict token spend will be greater than engineering salaries at early stage startups.

@boringmarketer Same

anyone feel themselves using openclaw a bit less lately? personally I feel like it’s memory is not great and it’s tool use even with skills is not close to claude code I like it for quick on the go things but it’s not a workhorse for me by any means at this point

1961: We should ship a CLI 2026: We should ship a CLI

@zebird0 Cowork: safe and sandboxed. Gateway drug, but probably want to graduate to Code at some point. Code: less guardrails, more power. But you need to set up integrations and scaffold. Openclaw: in the background to be proactive while you’re doing other stuff.

Someone please ELI5 when it's better to use Claude Code vs. Co-Work vs OpenClaw on specific computer tasks that a typical non-technical worker would need to do

@katibmoe @dunkhippo33 One

Introducing One. The simplest way to connect and monitor AI agents to hundreds of apps. And we’re open-sourcing the world’s largest integration database powering it: 47,000 agentic actions across 250+ apps. RT + comment “One” for access & 1M free API requests/month.

Your team's ChatGPT tabs are silos. One person knows something, the rest start from zero. I run AI in Slack. 13 channels. One agent sees product decisions, technical builds, strategy threads, everything. Knowledge compounds instead of resetting. That changes what's possible. I wrote about the 10-minute setup ↓

@RampLabs fuck yeah

Today, we're releasing Ramp CLI to let agents manage your company's finances. 50+ tools across cards, bills, expenses, travel, and approvals. Fewer tokens than MCP, and comes with pre-built skills like receipt compliance and agentic purchasing.

@m_franceschetti Using Cowork?

When I'm not working, I'm building. And I'm an inbox zero, so I built a system where Claude checks my inbox every 5 minutes and pings me on Slack with what isn't worth my attention and should be archived. Every hour I spend building, I get back a future day. That's the only math that matters right now.

@danshipper @openclaw @every Can I get access if I subscribe today? 😂

BREAKING! Introducing Plus One: A hosted @openclaw that lives in your Slack and comes pre-loaded with @every's best tools, skills, and workflows. Set it up in one click, and use your ChatGPT subscription (or any other API key.) Bring your Plus One to work: every.to/plus-one Connected to the @every ecosystem Plus Ones automatically use @every's agent-native apps, no setup required: - @CoraComputer for searching, sending, and managing email - @TrySpiral for great writing in your voice - Proof (proofeditor.ai) for agent-native document editing Custom skills and workflows we use and love Plus Ones come pre-loaded with skills and workflows we use ourselves @every —some we've made, and some we think are great. - Content digest—summarizes the publications you read, starting with @every - Daily brief—your day's schedule and to-dos sent to you each morning - Animate—turn any static screenshot into an animation with @Remotion - Frontend—Anthropic's front-end skill (which we use all the time!) We also make it fast to connect Google, Notion, Github, and more to your Plus One. Our goal is to give you a capable AI coworker right away, not a vanilla OpenClaw that you have to teach from scratch. Why we built Plus One @OpenClaw has changed the way we work at Every. We effectively have a parallel org chart of AI coworkers, each with a name, a manager, and real responsibilities. Because of them our workflows are completely different—our company is different—and we would never go back. But getting here has been hard. Claws require a significant amount of manual setup and require a dedicated machine—like a Mac Mini—running 24/7 to stay responsive. We have learned that the hard part of Claws is the infrastructure around them—the hosting, the integrations, the skills, and the ongoing care. We’ve made them work great for our team, and we want to share everything we’ve learned with you. We're letting in 20 people a week to start, and scaling invites quickly from there. @Every subscribers get priority. Bring your Plus One to work: every.to/plus-one

@spenciefy @usv sweet, gonna try tasklet out

I wrote about what we've been working on at @usv over the last few months – building custom software and agents to rethink what an AI native VC firm looks like Now that it's easier than ever to build, we've entered the "build something you want" era of software. When you build your own tools, you can shape and mold them to fit how you and your team work. Turns out, half the battle is just giving your internal agents names that your team likes