• Pixar's story-reel process — validate before building the expensive thing. Films start as ~4,000 storyboard drawings assembled into a narrated/temp-dialogue "story reel" — a cheap, low-res 2D version of the movie — and teams iterate ~8 times on plot, script, and dialogue before committing to 3D production. Lasseter: "If it's working in our story reels, when we animate it and put color to it, it's going to work even better. If it's not working in story reels, the animation won't save it." Jobs: it "lets us beta test and iterate on our films before we actually make it," a reason the hit rate differs. The point: story and characters must work in the cheap 2D form first, surfacing concept problems before expensive production. Acquired
• "Singles and doubles" content portfolio strategy (Paramount → Disney under Eisner/Katzenberg): keep production costs low, avoid A-list stars/directors, and bet on script/story quality plus "high concept" (an idea whose originality can be conveyed briefly); source undervalued talent (comebacks, up-and-comers) — "a young Warren Buffett strategy of looking for cigar butts" with a guaranteed return. Eisner memo: "Not even the greatest screenwriter or actor or director can be counted on to save a film that lacks a strong underlying concept." Katzenberg: "celebrity can open a film, but celebrity can't carry a film." Result: 27 of the first 33 films were profitable. Acquired
• Disney Plus — a strategic product bet (rationale, trade-offs, outcomes). After ESPN's subscriber losses surfaced in 2015, Disney chose to build its own streamer rather than stay a licensing supplier: Netflix's algorithm would otherwise control whether families saw Disney content, and Disney had no direct consumer relationships or data (no emails, no demographics, no DTC revenue except parks). Launched Nov 2019 at $6.99/month with "incredibly laudable" clarity of product vision. Trade-offs taken: walked away from hundreds of millions in pure-profit Netflix licensing (~2% of company profits) and ordered every studio to ramp production for the service. Outcomes: 10M signups in 24 hours, 26M in the first quarter, 100M in 16 months (vs. 60–90M five-year target), but ~$13B cumulative losses before turning barely profitable (~$1B last year), and 132M subscribers remains subscale vs. Netflix's 325M. Acquired
• The content-treadmill vs. brand-scarcity trade-off. A scale streaming service's #1 job is retention — "you need to feed the beast" with a constant fire hose of new content — structurally the opposite of Disney's flywheel of scarce, premium content; every marginal sequel/spin-off risks devaluing the differentiated library, and "if you have a bunch of bombs in a row, I think less of the Disney brand." Streaming is a scale-economies business (Netflix: $45B revenue, $13.5B operating income vs. Disney's streaming at half that revenue and barely profitable), so the winning service is the "kitchen sink" — broad content for broad appeal. Disney's realistic path: clear #2, subsidized by other businesses, dialing back production so the flywheel heals. Acquired
• Portfolio risk signal for franchise-driven businesses. Since ~2016 (Moana, Zootopia) Disney has launched no new commercially successful franchise — "everything after that that was big box office... is harvesting existing IP," and new Pixar originals now gross only ~$200–400M while sequels set records. "Product market fit is an evolving thing... the market is changing," so owned distribution (even at lower profit) is now the way new IP reaches audiences. Acquired
• Subscription bundling as churn mitigation. ESPN's new DTC service (ESPN Unlimited, $30/month) launched at the end of 2025, aggressively bundled with Disney Plus and Hulu (both for an extra $6/month) — bundling captures casual subscribers and reduces churn, since bundle subscribers don't re-evaluate each app's monthly value. Acquired
• Career tactic: reframe a candidacy on the future. Running for Disney CEO as the #2 to an unpopular lame-duck incumbent, Bob Iger knew every board question would be "why you from the failed previous administration?" His only chance: "completely reframe the situation. This isn't about what happened in the past. This is only about the future" — he hired a political campaign consultant and ran on three concrete pillars (high-quality branded content, embrace technology, expand global reach), and won the role. Acquired
• Pricing power when supply cannot scale. When Eisner took over, Disney park ticket/parking prices had been flat since Walt's death (parking: $1) despite 1970s inflation — "5 to 10x" headroom meant raising prices added pure incremental profit with zero operational change. Today, attendance is down from its 157M pre-pandemic peak (145M/year) but per-visit spend has climbed ~5%/year for decades, making parks ~60% of operating income; with physical capacity capped, pricing is the scaling lever, backed by $60B announced park/cruise capex in 2023. Acquired
• Internal tooling as a product decision. Disney invested ~$10M in fixed-cost software (CAPS, built with Pixar) that replaced hand inking/painting and expensive multiplane cameras — "better, faster, and it keeps the budget down" (The Little Mermaid: 3 multiplane shots; The Lion King: hundreds). One fixed cost that raised quality while cutting marginal production cost. Acquired

Typeform's lead PM Sun and senior director of research Lee present Research Flow, an AI-moderated mixed-methods research tool, as a fix for a core PM bottleneck: PMs juggling roadmap, leadership ideas, competitor moves, and customer feedback need validated data fast, but researchers often can't deliver in the 48-hour window stakeholders demand, so teams historically moved forward without research Product School. The trade-off they cite: surveys are fast but "just tell you what happened," while moderated interviews add nuance but require scheduling, live presence, note-taking, and transcript analysis Product School.

• Core method: Research Flow runs quantitative and qualitative data in one study — the PM sets the structure and an AI moderator follows up with each respondent based on research goals Product School. Follow-ups adapt to each answer and reference earlier statements, so the session feels like a real conversation rather than survey branching logic Product School.
• Implementation steps: build study questions in a chat interface with an agent trained on research methods; it probes (e.g., "what decision will this research drive?") and suggests uses such as shaping product direction or prioritizing concerns, or upload an existing script Product School. Lee notes that being crisp on what decision the research feeds and who the stakeholder is makes someone a better product builder Product School. Studies start with a welcome screen and screeners, and each question can carry up to three AI-moderator follow-ups to capture nuance behind Likert-scale answers Product School. The team steers non-researchers to this self-serve tool when the four-person research group can't service every request Product School.
• Recruitment: from inside the product, source respondents from Prolific (general population/B2C) or User Interviews (experts such as buyers and doctors), or share a link with existing customers; studies can run in multiple languages with responses generated in that language, and via video, voice, or text depending on the audience's comfort Product School.
• Live case study (trust in AI): a 5-question study (4 multiple choice, 1 open-ended Product School) with 25 respondents put average trust at ~3.5/5 Product School. Synthesized insights: accuracy/verifiability are the core trust blockers; users want AI to do the heavy lifting but not decide alone; technical tasks (data analysis, code interpretation, Q&A) earn trust while emotional depth is off-limits; creative tasks spark enthusiasm but hesitation Product School. 24 of 25 respondents raised accuracy/reliability, across 90 mentions Product School.
• Impact and output: Lee estimates traditional fielding would have taken 10–12 hours, versus synthesized insights in "a few hours or just a couple of days or just a few minutes in some cases" Product School; during the webinar, completions rose from 25 to 37 in about nine minutes with topics, sentiment, quotes, and mentions updating in real time Product School. Outputs include an executive summary, topic/sentiment breakdowns, per-respondent summaries, and highlight reels with verified, non-hallucinated quotes Product School.
• Adoption and influence lessons: Lee initially rejected the tool — "hard no... making my life harder" — and after the team iterated on feedback from internal researchers and dozens of customers, her team adopted it in late January/early February, replacing competitor tools and internal workflows Product School; she fact-checked every synthesized highlight for two months before conceding the tool's synthesis was as good as or better than her own Product School. An average like 3.5/5 is not actionable — stakeholders ask "why," which the follow-up questions answer — and one authentic sound bite (e.g., a sports fan recounting ChatGPT confidently giving wrong information) can be more influential than all the data when making a roadmap case Product School.

Computer-use agents have crossed from demo to production: the best model scores 85% on OSWorld-Verified (was 42% a year ago; humans ~72%), and production deployments are built on raw APIs with custom harnesses, not consumer agent products @fabrisera2000.

• Buyers pick vendors on reliability, security, and ROI - the model is rarely the deciding factor (models are already good enough); the biggest differences come from the harness around the model: verification, escalation, and error handling @fabrisera2000. Failure modes matter more than benchmarks, so design for failure from the start @fabrisera2000.
• The moat is context, not model: execution is commoditized, while durable advantage is workflow-specific knowledge (runbooks, credentials, test cases, a recorded video of the job); buyers want proof of hours saved and junior-engineer operability @fabrisera2000.
• Best-fit tasks are protocol-following, standardized, repeatable work with clear verification (CRM updates, QA, portal logins, IT tickets, order/contract processing); agents fail where output can't be cross-checked or success isn't observable at runtime @fabrisera2000.
• Field cases: a CPG platform runs ~15-20M portal interactions/month with agents as self-healing fallback for scrapers, halving the scraper-maintenance engineering team; a systems integrator runs 27 workflows processing ~1,500-2,100 IT tickets/day, aiming to redeploy 20-25% of headcount; an agency automated recruiting end-to-end using a cheap non-frontier model @fabrisera2000.
• Economics: agent inference costs ~$6-8/hour (range $3-15 depending on harness), roughly break-even with offshore BPO (~$10/hour) and 70-80% gross margin vs US back-office labor (~$30-45/hour); agents are slower than people (2-3 min human task takes 8-10 min) but run 24/7 and scale without hiring. A common pattern: run once, cache as deterministic code, and call the model only on breakage to cut cost per run @fabrisera2000.
• Next frontier: multi-agent orchestration lacks standard frameworks; progress will come on accuracy, latency, and cost (e.g., accessibility-tree grounding instead of screenshots) @fabrisera2000.

Cursor's Head of Talent Adam Ward shared a hiring playbook via Lenny Rachitsky; Cursor was acquired by Elon Musk for $60B @lennysan. Key takeaways:

• Forward-deployed engineers are the hottest role in tech right now—like the mobile-engineer boom, but compressed from two years to days/weeks @lennysan.
• The traditional recruiting funnel ("funnel of doom") produces mediocre teams because initial responders aren't the top 20%; instead, treat every hire like an executive search: rigorously scope what "great" means, map the 50 best people in the world, and pursue them relentlessly @lennysan.
• Role scoping is the most under-invested step; without it there's no sourcing strategy, pitch, or assessment; resist the "logo shortcut" of copying another company's definition @lennysan.
• Work trials are the highest predictor of success; Cursor runs on-site work trials that generate technical, values, and collaboration signals; removing them dropped hiring confidence significantly @lennysan.
• Post-offer is a danger zone (reneging, long gaps); Cursor runs it as a campaign—dinners with incoming hires, laptop shipped early, community before day one @lennysan.
• Sourcing: avoid "Who's the best engineer?"—ask hyper-specific questions tied to scoping; triangulate names independently mentioned by multiple trusted people @lennysan.
• For "bad timing" candidates, shrink the ask to "our next conversation," plant seeds over weeks/months, and use "home games" (shared meals, office visits) @lennysan.
• Closing is a team sport: daily standups on candidate motivations/objections, dedicated Slack channels; "caring is free" is the biggest unfair advantage—candidate satisfaction hinges on feeling genuinely wanted; focus on "the one," not the 10 @lennysan.

Lenny Rachitsky's podcast episode with Adam Ward, Head of Talent at Cursor, covers the playbook behind building high talent-density teams: why the traditional recruiting funnel—the 'funnel of doom'—guarantees mediocre hiring; Adam's three-step playbook for hiring the top 1%; the rise of the forward-deployed engineer; today's 'tale of two cities' talent market; the biggest mistake founders make with their first recruiting hire; and the worst question to ask when sourcing talent @lennysan. Context: Cursor is described as having competed with every major AI lab and incumbent, continued to win, built one of the most talent-dense teams in history, and been bought by Elon Musk for $60 billion to help SpaceX win the AI race @lennysan.

• Service design leader Vonnie Lang (UK public sector) argues the line between optional consumer products and services people rely on is blurring: when a product becomes a lifeline, teams inherit a duty of care whether they choose it or not, and the classic optimization/growth playbook "wasn't designed for any of this" — a new playbook is needed Mind the Product.
• "Average users" and "edge cases" don't exist Mind the Product. Case study: a nameless supermarket bank (grocery and banking arms serving very different demographics) revised its customer strategy and asked the team to "start with the people who have the least" — underserved families with two parents earning under £25,000 combined, often in persistent debt Mind the Product. Context: one in five UK residents (13.4M people, 4M children) live in poverty, below 60% of typical median household income Mind the Product. Research produced a composite persona of a young mom running a full envelope-budgeting system who knew every pound — one of the most sophisticated money managers the team met, disproving the assumption that struggling users are bad with money Mind the Product.
• Flip the design order: build first for the people who have the hardest time staying in your product or service, and the benefits lift everyone — plain English on gov.uk, for instance, helps second-language speakers, people under heavy cognitive load, and users in a hurry Mind the Product.
• "Eat your greens": separate needs from wants — wants get users in, but long-term needs keep them there, and needs shift across life chapters, so design for the user's future self Mind the Product. Follow design decisions forward and ask who the user is 6 months, 3 years, or 5 years later; buy now pay later was made frictionless by design so people committed without weighing consequences — teams should add "speed bumps" (guardrails) as in school zones Mind the Product.
• "Leave the building": dashboards and completion rates can look great while missing the real story — two users' identical click patterns in a banking app hid one person casually checking discretionary spending versus another anxiously doing mental arithmetic about direct debits and overdraft charges Mind the Product. Research doesn't need to be expensive: two people, train fare, a box of chocolates, and a day excused from meetings yielded ~200 post-it notes of insights; a quick, short, sharp, regular "sniff test" beats a six-month ethnography Mind the Product. Watching a user at a bus stop with a child in their arm writes the design brief — one-handed, low-data, on-the-move, interruptible — and failing any of those means "your product fails in the real world" Mind the Product.
• Closing call: protect the user care that drew you into the craft even as deadlines, dashboards, targets, KPIs, and shareholders push it out — you can still move fast without breaking the people on the other end Mind the Product.

• Hiten Shah (@hnshah) argues agents are the new website: the late-1990s website cycle — where a service market formed around builders who reduced the "cost of misunderstanding" — is repeating at much higher speed. A proposal "can tell you more about a market than a demo" because it prices the distance between seeing an agent work and trusting it with real work @hnshah.
• The most revealing line in an agent proposal is monthly maintenance: an example proposal (email, invoices, call-memory, privacy/control, keep-local) included discovery, phased implementation, and a monthly maintenance relationship, and the durable business will belong to whoever remains responsible for an agent's performance long after the initial build @hnshah.
• Agent maintenance becomes trust preservation because agents degrade silently — acting on stale context, missing exceptions, or producing plausible-but-wrong answers, with skills drift — unlike a broken website that announces its failure. Systems need evaluation, monitoring, correction, permission review, and periodic redesign @hnshah.
• Recurring demand is ordinary business work (email triage, call memory, CRM hygiene, invoices, internal search, lead routing, reporting); agents become valuable when they hold context across people, tabs, inboxes, and memory and reliably carry work forward. The build work is "operating design": deciding what the agent can see, which tools it may use, when it may act, how output is checked, and what happens under uncertainty, plus memory, permissions, escalation paths, and learning from failure @hnshah.
• Market signals: Fiverr reported an 18,347% increase in searches for AI agent freelancers over six months in 2025 (from a small base), and Microsoft's 2026 Work Trend Index found organizational factors (culture, manager support, talent practices) accounted for more than twice the reported AI impact of individual effort — individual experimentation is outpacing company redesign, and that gap is becoming a market @hnshah.
• Platforms will compress the middle: Shopify turns natural-language requests into Flow automations and generates custom admin apps via Sidekick; Salesforce says Agentforce reached $800M ARR and 29,000 deals by early 2026. Horizontal "we make AI agents" offers will age quickly; durability rises with the cost of error and specificity of context — strongest in vertical workflows, cross-system integration, private/local environments, and evaluation-heavy systems, because platforms can standardize actions but accountability takes longer to standardize @hnshah.
• The framing post: every business owner eventually asked "Who can make this work for me?" about websites — a question that created an enormous industry — and they are about to ask it again about agents @hnshah.

• Shreyas Doshi argues there is no single template for a great PM: highly effective PMs differ widely, succeeding via analytical strength, ability to drive teams, design talent, or deep domain intuition, despite weaknesses elsewhere; the idealized "always humble, great communicator, instantly responsive" PM doesn't reflect reality. Shreyas Doshi
• There is similarly no magic trait: Doshi has seen equally effective PMs with fixed and with intense growth mindsets. Shreyas Doshi
• The one mindset he finds highly correlated with PM effectiveness is not shying away from hard, ambiguous problems. This is a mindset, not a skill — skills are coachable, mindsets are learnable but not teachable; it typically changes through experiences, often failures, only when someone is ready. Shreyas Doshi
• Because all product work involves problems, Doshi says the advanced skill is judgment about which problems to solve and which to leave alone. Strong problem solvers without this discernment try to fix everything and end up on a treadmill: solving one problem creates downstream problems, and chasing those keeps teams on unimportant work; leave some nails alone. Shreyas Doshi

Priam Bagani, head of product at an AI billing infrastructure company, presents a framework for pricing and monetizing AI products in a Product School talk. Key points:

• AI product pricing is fundamentally different from SaaS: per-inference/agent-run margins, user-level unit economics, and consumption (not seats) as the value driver Product School.
• Pricing unit options form a ladder: raw tokens/compute → credits (e.g., Lovable) → units of work (e.g., CodeRabbit prices its Slack agent per minute) → outcome-based (e.g., Finn $0.99 per resolved ticket; HubSpot $50 per resolved conversation); choose based on product and customer Product School.
• Cursor's packaging: Pro $20 includes $20 of frontier-model spend; Pro Plus $60 includes $70 of frontier spend plus generous own-model usage; economics work via auto-routing to own models, spend caps, and 60-70% of revenue from enterprise deals (seat fees, pooled usage, governance controls) Product School.
• Lovable's credit model: subscription + credits with rollover/top-ups and daily 5 free credits that expire daily to drive habitual usage; credits abstract across design, hosting, and AI features, and users see per-action minutes/credits consumed Product School.
• Enterprise AI contracts require four primitives: entitlements (pooled usage, departmental splits, overage rates, not-to-exceed caps), commitments, ramps (e.g., $3M deal spread as $700K/$1M/$1.3M over years), and price/settlement — every element is negotiable Product School.
• Monetization infrastructure must meter/rate usage events in real time and keep an auditable credit ledger; design principles: preserve user momentum (hold-and-authorize, thresholds/alerts at 80%/95%), provide usage transparency, and treat limit-hit moments as smooth monetization opportunities (upgrade/top-up) Product School.
• Manage pricing changes deliberately: Figma Make ran free from launch (Dec 2025) until they understood usage before enforcing pricing; Cursor publicly apologized for a poorly communicated pricing change — consider grandfathering, cushioning, and clear communication Product School.
• Design questions: What unit of value will customers recognize on the invoice? Is usage bounded (sell predictability) or volatile (pass through/dual fixed+consumption)? Who decides and how fast (PLG vs enterprise)? What happens at usage walls? How will pricing evolve? Product School

• A PM at a 60-person B2B SaaS for regulated orgs (bank statements, government notices, utility bills) deploying its first status page on Atlassian Statuspage faces CEO fears that larger competitors (none with a status page) will use it to attack uptime; enterprise contracts already require publishing uptime stats and SLAs, and the page is live but not connected to health APIs yet r/ProductManagement +1.
• Visibility should not be all-or-nothing: Statuspage can restrict which services, components, and metrics each authenticated customer group sees — e.g., SLA-based transparency per customer — or just expose basic health with a simple "watermelon" display r/ProductManagement.
• A login-gated status page is a viable middle ground: only logged-in customers see it (and content can be tailored if a subset of the base is affected); if login itself is down, swap in a public-facing page r/ProductManagement +1.
• Launch quietly and validate: publish the page without an announcement, gather client-stakeholder feedback on its value, then use that feedback to prioritize changes and argue for/against keeping it r/ProductManagement.
• One PM's launched public cloud status page — with region- and feature-level categories so customers subscribe only to relevant events — deflected "hundreds of thousands of support calls" over years and was expanded beyond Sev1 incidents r/ProductManagement.
• Outages become public whether or not you have a page; your own page lets you control the story, and in regulated enterprise sales a public page signals operational maturity while its absence makes security/procurement assume poor reliability r/ProductManagement +1.
• If a public page would expose poor reliability, customers already know; use it as leverage to push reliability improvements if the PM has enough clout to make it a CEO goal — and if uptime numbers are weak, consider tiered pricing: a standard tier tolerant of brief outages plus a higher-priced "High SLA Guarantee" tier on a VIP instance that receives updates only after the general population proves reliability r/ProductManagement +1.
• Before committing, ask what problem the status page solves and whether customers actually care about availability r/ProductManagement.

Kavak's agent-per-customer bet (case study). Kavak — a vertically integrated used-car marketplace in Latin America, headed by AI lead Ali Masa — bet the company on agents, asking 'how would we build Kavak in 2035 with GPT-10-level intelligence?' a16z. The answer: every customer gets a dedicated agent with its own virtual machine, memory of years of interaction history, and a hard long-term goal (maximize customer lifetime value), rather than workflow automation a16z. The bet: agents outperform the best hired human on conversion, LTV, and customer experience a16z. Results: agents handle 96% of interactions and 95% of transactions, with 100,000–200,000 agents instantiated daily a16z; NPS and customer satisfaction tripled; agent conversion beat the human team by 50% at launch and now 2.1x a16z; car loans that normally take 2+ months in Mexico are approved in under 3 minutes a16z; warranty rates fell ~20–26% after mechanics received the agent sidekick 'El Mike' a16z. An agent CEO running a carved-out city in Mexico raised profits 50% in its first month against a 2x goal a16z.

Eval-driven development. 'Evals over agent demos': spend roughly equal engineer time, tokens, and money on evals as on the agents themselves, and evaluate business outcomes — did the customer convert and re-engage — rather than superficial KPIs like call count or minutes a16z. Kavak's measurement shifted from transactional (cars bought/sold) to relational (LTV per customer) a16z.

Architecture trade-offs. Kavak ran tens of thousands of agents on a multi-agent workflow-graph harness in production, then concluded with Opus 4.5 that the graph paradigm constrained the intelligence; it destroyed two years of working systems and rebuilt on a VM-per-agent harness with memory, evals, and CLI access to every company API — the 'self-improving organization' a16z.

Scaling playbook. To go AI-native: (1) redesign the company and its APIs around agents rather than layering ChatGPT onto the existing org; (2) generate data and feedback loops by putting agents live in front of customers; (3) shift success metrics to relationships and LTV a16z. The transformation must be top-down with a clear 3–5 year plan, not bottom-up hackathon use cases a16z.

Token-tier ROI framework. Tier 3 = agent tokens whose per-token ROI is directly measurable; tier 2 = indirectly measurable (e.g., developers in the codebase); tier 1 = generic copilot/chat usage with unknowable value — where most companies sit. Track that each token maps to business benefit a16z.

Org and career implications. The org becomes flat, senior, cross-functional teams that build agents, work for agents, or work in the physical world a16z. Kavak retrains everyone from CEO to mechanics through a six-week Jedi Academy that ends with shipping production agents; staying relevant means upgrading skills every month or two a16z. Masa's advice to builders: tools are democratized, so build deep for an AI-native future — superficial AI adoption yields only ~6–10% improvement while redesigning the company around AI yields the large gains a16z.

Lenny Rachitsky shared a video with Adam Ward (Head of Talent at Cursor) addressing hiring mistakes, covering the “funnel of doom” and how to fix your hiring process @lennysan; the full conversation is available on YouTube @lennysan.

Shreyas Doshi published a new video on the problem-solving mindset, covering whether this mindset is immediately coachable, why problem solvers must also develop great judgment, and the downsides of solving all problems @shreyas.

Lenny Rachitsky posted a video titled "The worst question to ask when sourcing great talent" @lennysan, and in a reply pointed to his full conversation with @wardadamp on YouTube (https://www.youtube.com/watch?v=zegYJ6dhIg4) @lennysan.

Atlassian PM evangelist Axel Suria shared AI-assisted GTM workflows for product teams:

• As AI lowers the cost of building, discoverability and market differentiation (GTM) become costlier; distribution is increasingly the hard problem — quoting Box CEO Aaron Levie Product School.
• Differentiates skills (bundled instructions telling an agent how to act) from agents (orchestrate multiple skills via tool calling and loops until an outcome) Product School.
• Dia's Morning Brief surfaces a daily, context-rich to-do recap (Slack, Jira, calendar via MCP) with embedded skills like drafting briefing talking points Product School.
• Built a Rovo Studio automation that triggers when a Jira Product Discovery work item moves to 'production': it drafts a landing page brief and passes it to a Replit agent that generates/publishes a page mock-up, then comments the link back on the work item — cutting hours of back-and-forth with the creative team to minutes Product School.
• Jira Product Discovery tips: custom fields with a RICE formula for stack-ranking; program/tactics/deliverables hierarchy in board view; matrix, timeline, and opportunity-solution tree views linking bets to deliverables and OKRs; shareable live roadmap URL so stakeholders can self-serve status Product School.
• Atlassian's Teamwork Graph is now exposed via MCP/CLI, allowing agents to pull Atlassian context into Claude, Cursor, or Codex Product School.
• For measuring webinar impact, cross-referenced Databricks, Salesforce, and goals via MCPs to build a dashboard in ~30 minutes (vs weeks of tickets); turned the workflow into a reusable global skill and made it available to his team through a Slack on-demand command Product School.
• Recommended pattern: start from your heaviest day-to-day problems and then find AI solutions; be kind to yourself amid pressure to deliver more with less Product School.

Hiten Shah shares cost-strategy guidance (via Shishir Mehrotra): at enough volume, every AI workload becomes a decision about what to rent and what to own, and open models give companies a path to turn repeated work into infrastructure they control @hnshah.

Grammarly's approach: many companies hit cost problems by routing every call to a frontier model @shishirmehrotra; instead, because Grammarly was building its own models before GPT-2, most of its 100B+ weekly LLM calls go to models it built itself, often fine-tuned from open source (e.g., Llama or Gemma) and served on its own infrastructure. The instinct to reach for the biggest model for everything is misguided — most workloads that run at scale don't actually need it @shishirmehrotra.

Hiten Shah (@hnshah) notes AI now makes it possible to "procrastinate at 100 commits a day" @hnshah — high commit volume no longer signals real progress, a caution for PMs tracking team productivity via activity metrics.

• Hiten Shah describes four AI marketing systems he and Sam Asante built around marketing jobs they already do, including two Hermes agents in Slack and a media system that saves hours and may be turned into a product @hnshah +1.
• The systems gain advantage from specificity: they encode the builders' context and decisions, turning each marketer's private operating system into executable software; tools that look too specific are where the edge comes from @hnshah +1.
• One system deliberately uses multiple sub-agents and a real-time interface, complexity the author normally avoids but accepted because the job required it; a model becomes an agent when its harness lets it see, do, remember, and check @hnshah.

• Samuel Spitz, AI product PM at Replit, argues the traditional PRD is dying: it's annoying and slow to write, translating the product in your head to text and back is lossy, requirements constantly change, and implementation reveals hidden constraints Product School. At Replit, PRDs are still written but almost always after a prototyping phase, which speeds up product development Product School.
• New AI prototyping workflow for PMs: express precise requirements in natural language, let a vibe-coding tool like Replit generate a first branded version, iterate based on team feedback, then hand off to engineers; PMs without design or coding skills can do this, often in under an hour, cutting weeks off the implementation cycle, and sometimes much of the code is already written by the agent before engineers start Product School.
• AI makes internal tooling accessible to PMs: low-code tools were still semi-technical, but now PMs without engineering backgrounds can build dashboards, automations, and workflow tools; people closest to bottlenecks can fix inefficiencies, and five to ten such tools can transform an organization Product School.
• AI compresses timelines and levels expertise: a week-long internal tool build can become a one-prompt task, and PMs can push back on "impossible" estimates by pointing to a working prototype they built in one prompt Product School.
• PMs also use AI coding agents for long-tail tasks such as one-off data requests, emails, go-to-market lead sourcing, and recruiting research Product School.
• Replit builds slide decks as websites because AI models excel at web design but produce templated slide outputs; this is used for pitch decks, sales decks, and internal presentations, with decks typically taking 4-6 minutes Product School.

• OpenClaw founder validated product-market fit by building a WhatsApp relay for personal annoyance and observing strong emotional reactions from friends, including nontechnical friends who were upset when told the tool wasn't ready for them. Y Combinator
• Launching the agent in a public Discord server triggered overnight virality (800 messages while he slept), and within 8 months the project attracted 18,000+ issue/PR contributors and 111,000+ total issues/PRs. Y Combinator
• Feature creep: every new feature shipped with a config option to avoid breaking setups, accumulating ~9,500 configuration options, making comprehensive testing impossible; "It is infinitely harder to evolve software that has users." Y Combinator
• Dependency risk: over-optimizing for one model provider backfired when the provider gave 24 hours' notice before disabling subscriptions; "Your dependencies business model is your business model." Y Combinator
• Security hardening trade-off: extensive sandboxing and permissions made updates slower and broke user workflows, while most users didn't value the security abstractions. Y Combinator
• Personal brand as a moat: "Everything you can build can be forked or cloned, but your name cannot," making personal brand more important than any single product. Y Combinator
• Enjoyment drives output: "Fun is velocity. The weeks I enjoyed building, the product got visibly better." Y Combinator
• First-user strategy: the founder should be user number one, with friends as the next ~20 users; if the builder isn't excited by the product, it likely won't succeed. Y Combinator
• Distribution is the hardest problem in an AI era where building is easy: "eyeballs are kind of the the most expensive currency." Y Combinator
• For new startups, he advises building something you personally want to use and choosing "hard and boring" categories because they attract users who appreciate the solution. Y Combinator