We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Three operators on rebuilding around agents
Zapier. Wade Foster says Zapier MCP is now Zapier's fastest-growing area. Users install it in the agent they already use, and the agent builds their automations in code. He calls Zapier "a code-based product now, even though the users aren't" . His test for an agent-first product: find what agents are still bad at that the models and harnesses won't fix. Then build a tool that an agent can sign up for, buy and use the way a person would . On cost, he tells customers to have the agent build a workflow rather than act as one. Deterministic Zaps run about 71% cheaper in some benchmarks than an agent that reasons from scratch on every run . His view on competing with the AI labs: the best companies quickly drop experiments that new models make pointless .
Ramp. Ramp counted 7,000 pull requests from non-engineers in Q2, mostly from its customer-experience team. Two years ago that number was "functionally zero" . The speaker contrasts this with the usual path, where a ticket goes from PM to designer to engineer and ships two months later, if it isn't marked "won't fix" . Ramp says its MCP usage is growing about 10% per week, and it began onboarding customers to its Glass harness this week .
Replit. When vibe-coding competitors spent heavily on ads, Amjad Masad chose "unsexy" enterprise work instead. Replit asked customers like American Express what would make them comfortable building mission-critical apps on it, and that enterprise business has compounded . With agents handling task-level work, he says staff now spend more time with customers and on "what's worth building" .
The common thread: agents are becoming customers for PMs to design for, as well as tools that change who on a team ships.
The PM role: prototypes over PRDs
Aakash Gupta passes on Postman's founder saying that PMs there are "building APIs and prototyping in Claude instead of writing PRDs," and that designers ship PRs through Cursor. Gupta calls it a harder job that needs taste and technical instinct . Market data points the same way. Juicebox's data on recruiter outbound searches shows falling demand for software engineers, rising demand for PMs and faster growth for AI engineering. Design hiring is down 20% year over year. Lenny Rachitsky says this matches his own job-market report . Gupta's Levels.fyi analysis covers 5,013 PMs and 47,318 engineers. PMs start $25K behind engineers in pay, catch up around year 8 ($256K vs. $260K) and earn more after year 12 .
Context is built through the work
In TBM 452, John Cutler lists ways context-sharing fails even among competent people. Experts can't put tacit judgment into words, the people asking can't say what decision they're trying to make, and clarifying questions come across as tests of competence . He questions the hype around "giving AI context." Instead of making ever more knowledge machine-readable, he suggests designing AI that builds context the way people do, through collaboration, observation and doing the work together .
A thread where PMs asked how to get better at prompting landed in a similar place. The top reply calls poor results "a clarity of thought issue," not a prompting problem . Another commenter warns that too much context, or outdated context, can ruin a session . A third keeps a doc tree on how their systems work that the agent reads. The agent researches and records what it finds before it writes any ticket, so each new chat doesn't start from zero .
Pricing: high conversion hid one-time demand
A music-library transfer app found that its free limit converted well, but most subscribers cancelled after their one transfer. After a decade of flat revenue, it made basic transfers free and now charges only for auto-sync and playlist tools. Revenue "dropped significantly" . One reply argues that a flat per-transfer price would have kept the one moment users clearly paid for . Another says to pick leading signals now, such as second-month return rates and sync conversions, and set a date to review them .
Sharing that actually spreads
In an r/startups thread, one commenter offers a test for viral sharing: can the person who receives the shared item get value in under a minute, and is your app the obvious way to get more? Quizlet study sets pass. Streaks mostly help retention, not acquisition . Another suggests measuring how many recipients open a shared result without signing up. If almost none do, the share "is just noise" .
- Parabus grew from a founder noticing an airfare price drop and a refund policy; after testing ways to find purchase data, the founders used email receipts to automate refund requests. At one point, one in 20 signups saved money within minutes.
- The founders listened to how customers described Parabus to friends and found that they naturally raised the 25% fee as a concern. They introduced a two-sided referral deal with a 20% fee for each side, after which referrals surged.
- Ramp’s customer research found people wanted more money left in their bank account, not just points or cashback; its product thesis was to create value by reducing waste, and it measures customer dollars and hours saved. The next phase also aims to help customers grow revenue and make necessary spending more productive.
- Ramp said it had begun onboarding customers to Glass that week; the product connects company systems while respecting individual permissions, sharing skills, and allowing model selection and cost/latency trade-offs, such as accepting 10% longer processing for a 50% lower price. Ramp also reported 7,000 Q2 pull requests created by non-engineers—mostly customer-experience staff—versus functionally zero about two years earlier, and contrasted same-day fixes with traditional ticket paths that could take months.
- Daffy separates giving into two decisions—how much someone can afford and whom to support—and encourages setting money aside first; it reports that every member cohort it tracked increased giving over time, with a dedicated fund making it easier to act when inspired without reconsidering the budget each time.
- Daffy applies engagement patterns to giving: members set a goal, receive celebratory confetti, count recurring donations toward the goal, and get an annual progress update with a nudge to increase it.
- Daffy says its family features came from member requests; accounts support up to 24 members, who can see donations and recommend gifts for the account funders to approve, edit, or deny. Members also asked for matching gifts, prompting Daffy to add campaigns for up to 15 nonprofits at once, with automatic matching of donations up to a set amount and phone alerts to the campaign owner.
- To reduce anxiety and an extra decision before donating stock, Daffy lets all members recommend whether and how long to hold donated shares and suggest portfolios; Daffy reviews recommendations against its investment policy.
Lenny’s Newsletter Product Pass added OpenRouter, PloyAI, Sentry, TextExpander, and LangSmith by LangChain; the one-year tool bundle now includes 35 products for Insider subscribers at $400/year and 22 for Annual subscribers at $200/year. The additions cover access to hundreds of AI models through one API and bill, growth-marketing agents, error monitoring, prompt and text shortcuts, and AI-agent observability. Codes are limited and first-come, first-served, and popular products may sell out.
Muse head of product Mona Sarantakos said shopping became a bigger use case than she had expected, pointing to an unanticipated product-use pattern.
- Zapier shifted from no-code UI abstractions to a product where agents write code and build automations; Wade Foster says Zapier MCP is its fastest-growing area. His strategic advice is to build specialized capabilities alongside evolving models and discard experiments when new model advances change what works.
- Treat agents as a new product platform: where models or their harnesses do not provide a needed capability, build tools agents can discover, sign up for, buy, and use.
- For cost control, have an agent build a deterministic workflow instead of repeatedly reasoning through routine tasks; Zapier reports some benchmarks showing Zaps are about 71% cheaper. Routing tasks to cheaper models or using code and no model can also reduce costs, but products should make those optimizations accessible without requiring users to understand model routing.
- Enterprise connector risks can block automation; Zapier invested in visibility and fine-grained permissions for data access, positioning governance as a reason to standardize on its platform. Foster says one large enterprise moved from concern to requiring connectors and automations to run through Zapier. Enterprises often limit AI assistants to basic tasks because of fears about connecting tools, while governance that contains major risks could let employees automate more work.
- For agent workflows, broad access to raw information across tools can improve outputs, but write permissions still need careful controls, checks, and decisions about where humans stay in the loop.
Recruiter outbound searches show growing demand for PMs while software-engineering demand is falling; AI-engineering demand is growing even faster, and design hiring is down 20% year over year. Lenny says these trends match his broader findings. His 2026 tech-job-market report also identifies PMs as “winning in the AI era” and says every role now requires AI skills.
Use a clear company story as shared product decision context: it should explain the customer job, why the approach works, and where the company is going; without it, product teams may build disconnected features and internal debates can lose a common framework. As a company scales beyond the founder’s direct involvement, capture customer questions, difficult product tradeoffs, and changes of mind so product decisions retain their original context; preserve the meaning when deciding what to share, rather than letting polished retellings lose what made the insight useful.
Muse identifies two major activation levers: relatable word of mouth, since ads do not resonate until people see someone like them using the product, and reducing first-prompt paralysis with idea starter packs that let users begin by saying “Let’s do it.”
- After vibe-coding competitors entered, Replit prioritized businesses operating on its platform, emphasizing reliability, scalability and security and working with customers such as American Express on mission-critical applications rather than matching competitors’ ad-heavy marketing; CEO Amjad Masad said enterprise business compounded and is now a primary focus alongside SMBs.
- Replit positions its platform as a secure, governed environment for AI agents, citing zero-trust principles and work on its sandbox and underlying operating system; Masad said Replit was affected by “about zero” of roughly 100 zero-day vulnerabilities over the past year, attributing this to a stripped-down kernel with less attack surface.
- At Replit, agents automating task-level work have shifted employee time toward customers, collaborative ideation and deciding what is worth building; Masad describes this as a “self-driving company” in which mundane tasks are left to machines.
- A Group/Lead PM at a professional-services firm with 3,000+ personnel described a new rapid-development lab building employee-efficiency tools with Claude Code: user and stakeholder feedback goes to Claude, and the team ships changes while reviewing PRs, without formal PRDs, user stories, or Figma artifacts. The author later clarified that guardrails and a design system are in place.
- The discussion suggests a stage-dependent approach: emphasize execution and shipping while seeking early fit, then formalize prioritization and delivery as adoption grows and support and maintenance costs emerge; proposed controls include security scans, governance, consistent UI/UX, and change management. A commenter also recommends grounding efficiency work in end-to-end workflows and outcomes, and suggests a shared knowledge space for requirements and architecture as a quick win.
For someone new to a company and writing strategy for an app area, commenters recommend reviewing prior strategy docs to understand audience expectations and learning the product, customer, and market context rather than relying on a generic template. Another commenter questions assigning a new hire to draft strategy before checking whether an area strategy already exists and argues that building organizational credibility should come first. To get past writer’s block, a commenter recommends Claude’s “grill me” feature or dictating thoughts for transcription.
- Product teams’ context-sharing breakdowns can stem from the interaction rather than lack of competence: requesters may not specify the decision or information they need, experts may struggle to explain tacit judgment, and mismatched detail levels can make questions feel like competence tests and answers seem cryptic.
- Build shared understanding through work, not explanation alone: combine upfront framing with observing, practicing, giving feedback, and solving problems together; frameworks can support this process but do not replace it.
- For AI-enabled workflows, the article proposes designing AI to develop context through collaboration, observation, experimentation, and doing work together, rather than continually requiring people to make knowledge explicit and machine-legible.
- As agents make prototyping, testing, and production work cheaper, product teams face a sharper “should we build it?” question: judgment, taste, and ruthless prioritization matter more, since teams can now build bad ideas quickly and bloat products.
- Treat other software products as a source of product experiments: identify the behavioral mechanics beneath a successful feature rather than copying its surface, then test whether those mechanics support a behavior that matters to your users. A strong product learning loop is to observe, form a user-relevant hypothesis, build the smallest test, measure what changed, and retain the learning either way.
- One commenter’s role-scope rule of thumb maps Associate PM to a feature, PM to a product, Senior PM to multiple products, Director to multiple verticals, and VP to multiple focus areas; they note that scope shifts with company size, giving the example that a Senior PM might own a whole product at a 100-person company while a PM at Atlassian might own one tab.
- An Associate PM reported owning three products, separate backlogs, engineering teams and sprint ceremonies, with overlapping customers and meetings taking more than half the day; several replies characterized that scope as heavy for an Associate, while another commenter said managing four to five small-team projects can work in a setup with centralized communications and automated action-item/backlog updates.
- Suggested workload-management practices include aligning team cadences, asking engineering leads to help run scrums, batching email and Slack responses, and protecting product-work blocks; one commenter recommends tracking a week of work and using the breakdown to make the case for support if true product work is below roughly 30–40% of the time.
- Product discovery should distinguish a standalone product from a feature that belongs in an existing platform: automating call-recording data into CRM fields may be a feature of the CRM or call recorder, while a weekly AI-generated rep-performance video was presented as a “solution in search of a problem” without clear customer demand. Monaco’s founders say hundreds of customer conversations surfaced a recurring early-stage startup pain point—too many GTM tools across CRM, data, and email sequencing, with uncertainty about what to choose and how to use them—which informed their product direction.
- For AI products, the speaker contrasts reactive pre-AI systems with an AI-native architecture in which agents do work before the user interacts with the interface; he argues that this shift could enable new category leaders and is difficult for legacy systems to adopt.
- Aakash presents a Postman founder’s account of PMs building APIs and prototyping in Claude, while designers ship PRs through Cursor; he argues this can cut the idea-to-prototype feedback loop from weeks to hours and signals a move away from PRDs and handoffs at leading companies.
- Aakash says the PM hiring bar is shifting: efficient PMs should reuse prompts for PRDs, strategy reviews, prototype critiques, LLM judges and experiment analysis. Technical GitHub evidence—including vibe coding, open-source contributions, repo literacy and AI prototypes or context engineering—is presented as an expectation. He says side projects can help in the job market, especially revenue-generating AI products or free tools with many users.
- In Aakash’s Levels.fyi analysis of median total compensation including stock and bonus, covering 5,013 PMs and 47,318 engineers, PMs start $25K behind, approach parity around year 8 ($256K vs. $260K), and pass engineers after year 12; PM compensation grows 2.8x from year one to 16+, compared with 2.1x for engineers.
- For product-development communication, the advice is to ask why, check that you and others understand, be concise, and set and protect a clear meeting goal.
- First Person Labs’ Second is designed as a persistent personal-context layer: it builds a model of a user’s memories, preferences, goals and other personal context, then shares that context with other agents so users need not repeatedly explain what they want.
- The product’s bet is on proactive, long-horizon assistance rather than just reacting to prompts or notifications. An early user described Second flagging changes to an event’s weather outlook without being asked; the founder framed this kind of cross-event “reflective” assistance as connecting a user’s priorities and activity over time.
- The team described model selection as a cost-and-fidelity tradeoff: route routine analysis and retrieval differently from less frequent, higher-level questions such as a user’s goals, and choose between pre-analyzing context for deeper insight or reasoning over raw logs at query time.
- Second was described as available, with inference capacity still being scaled for a responsible rollout. After finding UI and personal-page design difficult, the team narrowed its own surfaces to texting and an API, focusing on the underlying system and enabling others to build applications on top.
- For Smart Rotation, the poster reports iterating beta requirements through 20+ user interviews and feedback channels; the beta reached 50+ accounts and 1M+ calls, with a reported 5.3% lift in connection rates.
- For Messenger SMS, analyzing A2P registration rejections and adding in-product education increased registration from about 4% to 15%; the poster also established error and delivery metrics and coordinated launches across sales, support, and marketing.
- For AI products, the poster used competitive analysis and blind surveys to define quality scores and OKRs, then used customer needs and behavioral data to guide product decisions; they report a 15% increase in OKR score.
A cross-posted career discussion asks whether to take an AI product-management role at a big consulting firm despite a significant pay cut . A commenter describes the proposed cut as 25% and recommends negotiating, reasoning that an employer-initiated offer may leave room .
- Focus on requirements clarity rather than elaborate prompt formulas: state the desired outcome, ask what information or clarification the agent needs, and iterate; after getting a good result, ask the AI how to prompt for it more directly next time.
- Ground the task with brief, relevant context and direct-reference documents. Too much or outdated context may hurt results; one commenter also warns that conflicting examples and instructions can degrade output, so audit what context the agent is using.
- For repeat PM work, maintain reusable product/system knowledge and ticket-writing guidance rather than relying on fresh chats: let agents consult those files and relevant systems, research and document findings before drafting tickets, and update the files as knowledge accumulates. Keep human judgment involved: one commenter recommends writing down your own thinking first so the agent does not steer it, and another describes AI as organizing—not doing—their thinking.
Notes on building products people love when software gets cheap
Notes on building products people love when software gets cheap
I keep thinking about Meta and how ruthless they have been for years about taking mechanics that work somewhere else and making them their own.
Stories worked, so they put Stories everywhere. Short form video worked, so they went hard on Reels. Public text worked, so they built Threads. There are plenty more examples.
People usually talk about this like Meta has no shame about copying, which is fair enough, but I think there is a much more useful lesson buried in what they have been doing.
Meta is a consumer company. Their business depends on understanding what gets people to create, share, connect, consume, come back, and generally spend more time with their products.
When someone else spends years and a bunch of money discovering a new behavior that people clearly like, why wouldn’t Meta study the hell out of it?
Someone else already did a ton of the expensive discovery work for them.
In a weird way, Meta has treated the rest of the consumer internet like a giant external product lab.
I think every software company is going to need to get much better at doing some version of this.
Software is becoming way too easy to build for product development to keep working the way it has.
A lot of the scarcity used to come from implementation. You could have ten ideas that sounded good and maybe have the engineering capacity to seriously pursue two of them. The cost of building forced a bunch of prioritization on you whether you liked it or not.
That is changing fast.
Agents can already build prototypes, instrument things, test implementations, review code, fix issues, and do more and more of the production work around software. I expect that to keep moving quickly.
Eventually “can we build this?” becomes a pretty boring question for a lot of software.
Then we are left with the question that has always been harder anyway.
Should we build it?
This is where I think things get interesting.
There are thousands and thousands of software companies running product experiments for us every day.
They are spending their own time and money figuring out better ways to onboard people, create habits, collaborate, review work, build trust, share things, discover things, verify things, delegate work, build reputation, create marketplaces, personalize experiences, give feedback, make something multiplayer, and pretty much every other behavior you can imagine inside software.
We get to watch all of it.
I don’t mean make a spreadsheet of competitor features and start cloning whatever looks cool. That is probably one of the fastest ways to turn a good product into a pile of shit.
The interesting part is figuring out the mechanic underneath the feature.
Take a pull request.
On the surface it is a developer tool feature. Underneath, someone proposes a piece of work, the work becomes visible to other people, feedback gets attached directly to it, people can inspect it asynchronously, approval changes its state, and the whole history sticks around afterward.
That mechanic can travel pretty far outside software development.
You could apply versions of it to AI generated work, marketing, finance, design, legal, operations, research, and plenty of other things.
Stories are another obvious example.
The interesting part was never just that a photo or video disappeared after 24 hours. The mechanic lowered the pressure to create, which made people more willing to share, then made consuming those updates incredibly easy, showed the creator who watched, gave people an easy way to reply, and created another reason to share again later.
There is a whole behavioral system underneath the visible feature.
Once you start looking at software this way, categories get a lot less useful.
A game can teach an enterprise product something. GitHub can teach an AI company something. TikTok can teach a research tool something. Marketplaces can teach agent products about trust. Consumer social products probably have a lot to teach B2B software about getting people to contribute more without making it feel like work.
You are basically looking for machinery that has already proven it can change human behavior.
Then you figure out whether that machinery can help with a behavior that matters inside your own product.
That part is important because every company has a different thing it should actually care about.
Meta has spent a lot of time caring about attention because attention is tied pretty directly to their business.
An AI product might care about whether people trust an agent enough to delegate increasingly important work to it.
A marketplace might care about every successful transaction making the next transaction easier to trust.
An analytics product might care about turning evidence into a decision and then getting that decision turned into an improvement.
A company building software for teams might care about work leaving enough useful context behind that someone else can pick it up later without needing another meeting.
Whatever it is, figure out the behavior first. Then go hunting for mechanics that might help create more of it.
I can see companies eventually having entire libraries of these things.
This mechanic increases contribution without requiring a giant reward.
This one reduces the anxiety of sharing unfinished work.
Another one makes verification more likely.
Some mechanics build reputation as a byproduct of normal use.
Others make a workflow multiplayer.
A few only work once you have enough network density.
Some work incredibly well in games and completely fall apart when you move them into productivity software.
Over time it probably becomes more like a graph than a library, especially because AI can help us watch so much more of the software world than a product team ever could on its own.
An agent could watch product launches, changelogs, screenshots, demos, reviews, user complaints, open source projects, App Store updates, and whatever else we can throw at it. It can start finding patterns, breaking mechanics apart, connecting them to behaviors we care about, and eventually suggesting how they might translate into our own products.
Then another agent can build the prototype.
That sounds a little sci-fi when you write it all out, but we are already close enough to pieces of this that I don’t think the direction is particularly hard to see.
The funny part is that all of this makes the human side more important to me.
Judgment gets more valuable when building gets cheaper.
Taste matters more when you can add almost anything.
Knowing which behavior actually matters becomes more important when you can optimize a hundred different ones.
Understanding why something worked somewhere else matters a lot more than noticing that it worked.
And knowing when to leave the damn product alone might become one of the most valuable product skills of all.
I also think this means ruthless prioritization gets more important, which sounds backwards at first.
For a long time engineering scarcity saved us from ourselves. A bunch of mediocre ideas never got built because there simply wasn’t time.
We are losing that protection.
We are about to become extremely good at building bad ideas quickly.
That is probably going to create a whole new class of bloated products made by teams that confuse the ability to build something with a reason for it to exist.
The companies I would bet on are the ones that get really good at the learning loop.
See something interesting somewhere in the world. Understand what is actually happening underneath it. Form a hypothesis about why it might matter for your users. Build the smallest thing that lets you test it. Put it in front of people. Measure what changed. Keep the learning whether the idea worked or not.
Then do it again.
Meta figured out a version of this because their business forced them to. Their old Little Red Book is full of ruthless prioritization, keep shipping, the quick inherit the earth, code wins arguments, everything is up for debate, and a bunch of other ideas that make a lot more sense to me when I look at them through this lens.
They built an organization that could watch human behavior change, move quickly when they saw something important, and keep learning.
AI is going to make some version of that useful for pretty much every software company.
The entire software industry is becoming an external R&D lab that you get to learn from.
Everyone else can help discover what works.
The code to try it yourself is getting cheaper every day.
Which means knowing what deserves to exist is going to matter a hell of a lot more.
- As agents make prototyping, testing, and production work cheaper, product teams face a sharper “should we build it?” question: judgment, taste, and ruthless prioritization matter more, since teams can now build bad ideas quickly and bloat products.
- Treat other software products as a source of product experiments: identify the behavioral mechanics beneath a successful feature rather than copying its surface, then test whether those mechanics support a behavior that matters to your users. A strong product learning loop is to observe, form a user-relevant hypothesis, build the smallest test, measure what changed, and retain the learning either way.