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.
TBM 452: Contexting vs. Context

I have observed highly experienced people struggle to describe their expertise, the information they needed (or used), the decisions they needed to make (or made), and what they know about a situation. This doesn’t mean they lack expertise or aren’t making good decisions. In fact, their expertise may be part of the reason they struggle.
This can manifest in many ways: struggling to explain your value in a job interview, having difficulty defending a decision when challenged, trying to teach someone else how you work, or attempting to establish shared context with colleagues so you can make decisions together. These situations may look very different, but they all involve making knowledge and reasoning explicit that normally operate in the background.
With AI and all the hype around “sharing context,” the ability to make what we know, assume, and need explicit matters more than ever.
Or does it?
Gary Klein and others have observed that experts often rely on rapid pattern recognition and tacit knowledge rather than “classic” decision making (identify decision, compare alternatives, articulate information needs). Expertise allows them to make good judgments without necessarily being able to explain every step of their reasoning. The more experienced you become, the less you may need to consciously practice some of these meta-skills.
Exhibit A: Job interviews. Interviewing is absolutely a skill, but being able to reconstruct and explain your decisions on demand is very different from making those decisions in the flow of actual work. We sometimes mistake being good at interviewing for being good at the job itself.
During a recent coffee chat with a product leader friend, we stumbled on a contradiction. They had to laugh about it when we sketched it out. First, they felt continuously “put on the spot” by the repeated questions from their reports. “I thought I made this clear, but either I didn’t, or they just don’t get it.” Next, they decried how hard it was for their reports to frame the information they actually needed. “How am I supposed to help if they keep dealing with generalities and vague commentary on our strategy?”
That would have been interesting enough, but then they immediately made the connection between those behaviors and their own experience with their manager.
“They don’t share any nuance and expect me to fill in all the blanks. Of course I can, but it feels like a competence test. They constantly seem frustrated by the decisions I make, but when I ask for feedback, it’s incredibly hard to decipher their thought process. Frankly, they’re not very good at explaining their reasoning, despite being awesome at their job.”
There was a pause.
“Wait. I’m basically a hypocrite.”
The problem works on multiple levels.
When we need context, we may struggle to articulate exactly what we need, what we already know, and which decisions we’re trying to make. Meanwhile, the person we’re asking may struggle to explain something they “just know.” Our questions can feel vague, repetitive, or poorly framed to them. Their answers can feel incomplete, evasive, or unnecessarily cryptic to us. Both sides can walk away frustrated, questioning the other’s competence, without recognizing that they’re struggling with different sides of the same problem.
Over the years, I have been involved in many context-sharing exercises. And I’ve seen my fair share of exercises go south, even when everyone involved was highly competent, well-intentioned, and genuinely interested in collaborating.
The failure modes include:
Difficulty articulating tacit knowledge. People know what they’re doing, but struggle to explain how they know what they know, what they’re paying attention to, or how they arrive at decisions.
Difficulty articulating what context is needed. The person asking for context may not be able to explain what they’re trying to decide, what they already know, or what information would actually help.
Mismatched expectations about the level of detail. One person provides a high-level explanation when the other needs specifics, or dives into details when the other needs the big picture. Neither necessarily knows what context the other already has.
Perceived challenges to competence or authority. Questions intended to clarify someone’s reasoning can feel like tests of their expertise, especially when the person asking doesn’t explain why they need the information.
Confusing a good explanation with good judgment. People who can articulate their reasoning clearly may appear more competent than people who struggle to explain themselves, even when the latter are better at the actual work.
The assumption that explaining is the best way to share expertise. Sometimes watching someone work, examining a recent decision, or solving a problem together reveals far more than asking people to describe their thinking in the abstract.
What makes these failures particularly tricky is that they often look like problems with the people involved rather than problems with the interaction itself.
Let’s dig into the last point (#6).
One of the most natural ways humans develop shared context is by working alongside one another. We observe, act, ask questions, respond, and gradually develop a shared understanding of the situation. We don’t necessarily articulate all the relevant context in advance. Much of it emerges through the work itself.
Great teachers in professional and vocational settings are skilled at balancing upfront context (e.g., concepts, principles, techniques, and safety considerations) with opportunities to get started, explore, and practice. They work within earshot and eyeshot. They continuously model, observe, and offer feedback, gradually increasing the level of difficulty and responsibility. They know when to step in, when to step back, and when to let someone figure things out for themselves. Frameworks/models don’t replace that. At best, they support and structure the process of developing shared understanding through practice.
With all the hype around “context layers” and “giving AI context,” I think we miss something fundamental. Humans aren’t naturally tuned to articulate context on demand. Nor are we particularly good at identifying the context we need or recognizing the context we already have.
The 4Es of cognition (embodied, embedded, enactive, and extended) offer a useful perspective here. So much of cognition involves interacting with our environment, working alongside others, collaborating to make sense of situations, and using tools and artifacts that embed context in our surroundings. We don’t simply retrieve context from our heads and apply it to situations. We develop shared understanding through conversation, observation, experimentation, and action. We discover and create context through the work itself.
Perhaps the challenge isn’t just figuring out how to give AI more context.
Maybe we should stop assuming that the answer is to make more and more of our knowledge explicit, structured, and legible to machines.
What if, instead of constantly asking humans to adapt how they work to accommodate AI, we got better at designing AI to participate in how humans actually develop context—through collaboration, observation, experimentation, and doing the work together?
I’ll end with a quick story. Recently at work, my teammates and I were exploring elaborate ways to make sure AI had all the right “context.” Eventually, we realized we were overcomplicating things. We were trying to avoid doing the work of developing shared context ourselves.
So we just had a meeting.
- 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.