We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Big Ideas
Agents are becoming a first-class product user. Scott Belsky argues that an enterprise cloud product without a roadmap for agents is already behind: agents charged with workflow design will favor efficient, accurate, agent-ready services. Muse makes the direction concrete—an always-on assistant that uses a browser and connected apps, with a 1Password partnership for existing logins. Belsky’s product test is proportionality: users will demand trust and utility commensurate with the data access they grant. PM implication: access, identity, and trust signals belong in the core experience, not a later integration.
Consumer AI may reset the retention playbook. Andrew Chen’s thesis is that workplace AI wins on patterned, verifiable drudgery, while consumer products depend on novelty, authenticity, and parasocial trust; visible AI slop undermines those advantages. He argues that if apps become as cheap to make as content, average retention could collapse and greater-than-20% D30 may stop being the right yardstick. The operating response is a fast cultural feedback loop plus human taste and editing: move quickly, but do not copy-paste AI into customer-facing work.
Tactical Playbook
Separate task conflict from relationship conflict. Teresa Torres and Petra Wille recommend using retrospectives and explicit team charters to surface how a trio works together. Bring disagreement about the work into shared discovery; handle interpersonal friction one-on-one first. When it is opinion versus opinion, run an experiment rather than escalating a debate, and use joint escalation when leadership must intervene.
Instrument the economics, not the whole company. In a low-maturity SaaS organization, first identify the customers driving revenue, renewal timing, gross retention, and upsells; then choose a thin slice of telemetry to improve a specific decision. Existing APIs or open-source tools, one willing developer, and privacy sign-off can be enough to start. A dashboard for one team is a better first move than waiting for a company-wide transformation, especially when “just getting changes out” is crowding out measurement.
Case Studies & Lessons
Grok Bot: isolate, observe, unship. The team built from scratch in a small, physically isolated group; it reached an internal prototype about a month after the first line of code, then went from internal beta to public launch in roughly three weeks. It manually onboarded a couple hundred users over two weeks, including a coffee-shop owner, and watched users develop workflows rather than prescribing them. Before launch, it removed experimental and developer-facing features, focused on backend failures that blocked real work, and reframed the roadmap from “what has been added?” to “what can the product now do?” The team says 99% of automations are created in natural language. The lesson is not simply speed: tight decision loops, unusual users, and aggressive subtraction made capability—not feature volume—the launch standard.
Legora: pair usage with economics. Legora’s scorecard combines 95% gross retention, 300%+ NRR, DAU/MAU above 50%, 17 hours of monthly usage per active user, a 78% competitive-pilot win rate, and positive, improving gross margin. For B2B AI products, usage is an early signal that the work matters; retention, expansion, win rate, and margin test whether that importance becomes a durable business.
Career Corner
Make strong product work legible upward. One Apollo PM scored 8.75/10 at moving metrics but 6/10 at stakeholder management; the CEO noticed the second gap and lacked visibility into a high-performing area. The fix was to map the real stakeholder network, publish discovery takeaways where the trio could see them, and secure an all-hands slot. Two quarters later, the CEO raised the area unprompted at a leadership offsite. The career lesson: every meeting is an interview, and metrics alone do not make impact visible.
Tools & Resources
Local-first reference: Desert Ant Labs launched 18 on-device models across audio, vision, and text with Swift, Kotlin, and JavaScript SDKs; its pitch is no tokens, no logins, and no data leaving the device. It is a concrete reference point for evaluating when latency, privacy, and per-call cost justify moving intelligence closer to the workflow.
