We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
An incumbent that restarted around AI
Podium CEO Eric Rea says the company crossed $150M in AI ARR. The first time Podium reached $150M ARR, it took 8 years. This time it took 2.5 . Three years ago Podium had well over $100M in revenue and tens of thousands of customers, and it still chose to "start over," betting that AI would make much of traditional software obsolete . The product grew into whole operating systems for its industries, "from the AI agents all the way down to the systems of record." Rea says the harder part was changing how the company builds, sells, serves customers and runs . He reports 20,000 agents in use, more than $13B in revenue generated for customers, and that Podium is profitable .
Paul Graham calls Podium a rare middle case between incumbents that "at best adapt" and startups that are AI-native from day one . He frames it as founder mode: a hired CEO wouldn't have the moral authority to "ignore existing revenue streams" . For product leaders, the point is that the rebuild was organizational as much as it was about features.
Quality is a moving target for AI features
Ravi Mehta argues that a successful demo proves little for AI features. Teams need to understand "the range of experiences customers receive" . Quality can get worse without any code release, because models change, information goes stale and user behavior shifts . Customers rarely report this. They double-check answers, go back to spreadsheets, and "quietly quit" the feature . The signals to watch are workarounds and declining reliance . He says senior PMs should set an acceptable performance range rather than a pass/fail line, and when quality falls below it, "reduce scope or change the launch plan — not quietly lower the standard" .
Discovery was always slow. Now it's visible
In an r/ProductManagement thread about AI speeding up delivery, one PM put it this way: discovery "stopped being hidden." Six weeks of validation used to sit inside a 12-week build. Against a 3-week build, the same six weeks becomes the bottleneck . If you don't direct spare engineering capacity, it "gets filled by whoever asks loudest." This PM keeps a short list of work that unblocks other teams, ready to pick up . Others said to use the extra speed for hypothesis testing rather than a feature factory . In r/ProductMarketing, a PMM warned that AI makes it easier for non-leaders to copy segment leaders' roadmaps. They suggested more customer interviews and deliberate launch packaging in response .
Pricing when the user is an agent
Two Stockholm founders building a CRM dropped per-seat pricing after a customer pushed back. He rarely opens the app, and his AI assistant writes about 92% of his updates over MCP . They now charge a small workspace fee plus a fee per company with an open deal. Their worries are harder forecasting, possibly lower revenue, and buyers who "understand seats instantly" . Commenters said seats are dead "wherever the product's value doesn't scale with humans typing into it." They stressed choosing a usage metric customers can predict before the invoice arrives . One noted that open-deal counts track deal volume, not the value the AI creates . Another suggested sizing the base fee so "the worst month" is survivable .
Agent permissions
Hiten Shah shared a cautionary case about Muse. Matt Robb chose "Allow Always" for replies, expecting he would still approve offers. Instead Muse accepted one and shared his pickup address, and a buyer showed up while he was away . The setting's label didn't match what he thought it did, and that matters most when the agent's action is consequential and can't be undone.
Also notable
- AI fluency in performance reviews: Aakash Gupta summarizes Zapier's rubric, with grades of Capable, Adoptive and Transformative. He warns that what counted as Transformative in 2025 may only be Capable in 2026 . He also says "every line you send out, you are accountable for" .
- Landing-page friction: Magic Patterns removed the prompt box from its landing page and its conversion rate "totally tanked" . Tests at Creative Market found that a visible, expanded input converted much better than flows that required a click first .
- Unconfirmed competitor moves: A market-intelligence lead found that hunches in the weekly digest get read as fact . One fix is to tag each item as signal, likely or confirmed, keep everything but confirmed out of battlecards, and tell sales what evidence would confirm it .
- Magic Patterns’ founders spent about nine months on adjacent products; they said none had 10 users who both paid and used the product, while that group came quickly after Magic Patterns launched. The CEO emphasized daily customer conversations and adapting to changing workflows, noting that an internal MCP project unexpectedly became a major way customers used the product.
- As AI speeds up implementation, product teams can spend more time exploring what to build and testing variations and states. Magic Patterns’ canvas supports parallel threads and bringing in PRDs and documentation, but the team found that a canvas is not for everyone and identified onboarding and progressive disclosure as challenges.
- For better AI design results, add relevant company context, design systems, skills, and components before prompting; the CEO recommends spending about 10 minutes on this setup to save hours later.
- Prioritize a clear offer and call to action with low-friction entry: Magic Patterns’ conversion rate tanked after it removed its prompt input, and the interviewer said Creative Market tests found an expanded, visible input converted better than flows that required users to click before entering an email.
- Build customer feedback into daily work: Magic Patterns has every employee handle support, giving engineers direct exposure to user problems; one example was fixing difficulty finding the share button when two primary buttons had the same color. For website tests, the founders recommend asking users for feedback without making it clear that it is your site, to encourage candid reactions.
- For AI products that need sensitive data, the interviewers argued for proactively explaining data access, use, retention, and security to help users feel comfortable trying the product and recommending it.
Lenny endorsed an incident account in which critical PHP vulnerabilities exposed a gap between the recorded inventory of 12 servers and the unknown real count; some legacy systems had unknown purposes or owners. Patching took four hours, while determining what PHP actually ran took eleven. The account also shows the prioritization conflict: finance asked to delay patching over downtime and revenue, and marketing resisted taking a campaign page offline despite the risk of remote code execution.
Lenny says Dario has been right about most AI timelines so far, often even conservatively . Gergely Orosz cites Dario’s May prediction of a 6–12-month window before Chinese models caught up and calls it correct, noting it was five months earlier .
Warp Sciences launched to apply AI and robotics to accelerate medicine development; it raised a $215M Series A led by Lightspeed to bring frontier AI from the browser into the lab and build U.S. scientific capacity. A commenter characterized the approach as a next-generation American preclinical CRO, arguing that robotics- and intelligence-first operations could make it competitive and serve as a model for industrial reshoring.
- AI makes product judgment, not shipping volume, the limiting skill: faster building does not identify the right problem; a reported “five things in five days” launch lacked adoption or customer-feedback evidence, while constant workflow changes can overwhelm users. Use the extra speed to test bets, kill weak ones early, and validate value with customers; as output rises, user attention and perceived value can become constraints.
- More automation does not remove delivery controls: AI-written stories and epics can leave QA unclear about what to test when work has not been validated with users, and prototypes can miss UX, edge cases, or architectural constraints. Vibe-coded demos may help test an idea, but security, compliance, infrastructure, and production code review can still require engineering work.
- AI-assisted internal builds can pressure thin SaaS, but code is not the only moat: one commenter reports rebuilding an internally used SaaS solution costing about €45,000 per year and running the customized version for nearly two months without downtime. Potential defenses raised include domain expertise and customer-learning processes, proprietary data or research, go-to-market reach, and accountable expert support for audited workflows.
- Avoid universal forecasts: commenters describe both useful and poor AI outcomes and caution that results vary across software types and development contexts.
- OpenAI described a shift from ChatGPT users asking questions to using agentic products that do tasks and act as proactive virtual coworkers; it also announced acquiring Orchestra Bio, a platform for AI agents and scientists aimed at accelerating drug discovery and delivery. The company cited 1.2 billion weekly ChatGPT users.
- OpenAI reported 100,000 advertisers across 89 countries and said its business model enables 90% of its 1.2 billion weekly users to access AI for free.
- OpenAI said it had gone live on Google Cloud Platform, allowing it to serve customers across AWS, Azure, GCP, and Oracle; it called the expansion a potential tailwind through 2027.
- OpenAI said a proof of concept with HCA showed it could reduce the time patients spend in hospital by 25%, with the stated aim of moving patients sooner into community care.
Canva introduced Craft, making its first frontier model built specifically for design available to everyone; Canva says it is now the world’s second most advanced AI lab for image generation on DesignArena’s global leaderboard.
Lenny recommends a PM interview-prep toolkit spanning Insider Loops and Never Search Alone, AI Practice Copilot and a guide to using AI in interviews, Ultraspeaking, and guides to product sense and analytical thinking.
- One PM argues discovery has not slowed; faster builds have made its existing lead time visible: six weeks to assess an idea used to sit inside a 12-week build but now stands out against a three-week build. If spare engineering capacity is not directed and useful work is not queued, the loudest requests can take it; keep a short list of work that unblocks other teams ready.
- Use added delivery speed for hypothesis testing rather than simply producing more features: establish discovery and experimentation routines and steer teams away from feature-factory thinking. Protect recurring time for customer calls and quantitative decision-making; one PM says they reserve days each week, not just hours.
- Teams report different capacity needs: one says delivery is not yet faster than discovery and expects a shorter discovery-to-delivery cycle to speed go-to-market; others are using engineering time for maintenance, minor improvements, or long-ignored tech debt.
Warp Sciences launched to apply AI and robotics to developing medicines faster, with a strategy of bringing frontier AI from the browser into the lab; it raised a $215M Series A led by Lightspeed.
An upcoming free 30-minute session will cover choosing among Muse, Grok Bot, and dots, based on what people accomplished with each and where they ran into problems; it will also outline nine jobs for the agents and what should still require human approval. The session is advertised for 10 AM PT the following day.
Kevin Weil and cofounders launched Warp Sciences, an AI-and-robotics company targeting faster medicine development; it raised a $215M Series A led by Lightspeed to bring frontier AI from the browser into the lab. Investor @fidjissimo described the approach as building physical infrastructure where AI can test ideas in the real world, learn from results, and iterate for scientific discovery.
For AI product discovery, look for products enabling activities users could not previously do—not only tools that make existing work faster, better, or cheaper. Early versions may look like toys or hobbies; assess whether the underlying capabilities can improve fast enough to bend into an exponential curve. AI networks may begin as single-player tools and evolve into multiplayer networks, suggesting a possible product path from standalone utility to network.
- Warp Sciences launched with a $215M Series A to apply AI and robotics to faster medicine development and build scientific capacity in the U.S.
- Its product strategy is to provide preclinical CRO infrastructure for drug developers, starting with chemists doing customer work and progressively automating workflows that scientists validate in the lab. The proposed flywheel is that automation enables more experiments and training data, improving science models that can then design better experiments and automate more work. The approach targets a bottleneck Weil identifies in drug discovery: models lack the type and volume of experimental data needed for these empirical sciences.
Kevin Weil announced Warp Sciences, a new company applying AI and robotics to accelerate medicine development; it raised a $215M Series A led by Lightspeed to bring frontier AI into labs and build scientific capacity in the US. Josh Tobin’s accompanying product thesis: automating scientific progress requires automating the experiment loop as well as building smarter models.
Kevin Weil and co-founders launched Warp Sciences to apply AI and robotics to developing medicines faster; the company announced a $215M Series A led by Lightspeed to bring frontier AI into the lab and build scientific capacity in the U.S.
Hiten Shah says the next challenge for AI agents is managing them: after a year building agents and observing where they break, he is focused on making them useful repeatedly; he joined a16z’s inaugural Ops Engineering Fellowship. The fellowship describes ops engineers as connecting operations and engineering by consolidating tools, building the data and context layers agents rely on, deploying agentic workflows with human checkpoints, and driving adoption; operational leaders also decide which workflows to automate first and which KPIs will show whether automation works.
The PO/engineering line-management boundary varies by organization: one commenter separates product scope, backlog priorities, and delivery from HR and people management, while others note that responsibilities can be fluid in small companies. In this thread, the PO says HR check-ins revealed an assumed developer-management role that had not been discussed; they were already handling demos, training, bugs, vendors, and delivery, without clear management authority or budget. They later said developer reporting was absent from the job description and they had no resources for the added responsibilities. Replies recommend clarifying reporting lines, authority, and support, and asking the manager which existing duties should be deprioritized rather than trying to absorb everything.
Hiten Shah previewed a practical AI-agent comparison: Claire Vo found Muse’s results varied widely across three everyday jobs, and the planned comparison of Muse, Grok Bot, and dots will cover nine jobs and when a person should step in; it was scheduled for the next day at 10 AM PT.
Muse’s “Allow Always” replies setting created a consequential permissions mismatch: Matt Robb expected to approve offers, but Muse accepted one, shared his pickup address, and a buyer arrived while he was away. The incident illustrates the product risk of broad agent permissions when users expect approval before consequential external actions or disclosure.
