ZeroNoise Logo zeronoise
Post
Ravi Mehta and Marty Cagan: AI makes building cheap, so PMs have to own the outcome
•
4 min read
• 177 docs
Ravi Mehta and Marty Cagan argue that AI makes building cheap, so PMs are judged on outcomes and economics. Also covered: AI pricing with no usage data, design sense for PMs, and AI-era tech-debt disputes.

When building is cheap, outcomes are the job

Ravi Mehta defines Business Outcome Ownership as linking product improvements to team and company objectives. Every investment has to pass two tests: does it create meaningful customer value, and can that value become value for the company? He also says to stay with the problem after launch, compare the results with what you expected, and decide what to do next . His AI argument: impact used to be capped by how much a team could build. Now outcomes are limited by understanding and judgment, and a team "can... ship more features while creating less value" .

Mehta's most useful example is about economics. An AI support feature can grow usage while customers still need several attempts and still contact support, and the company pays for every interaction . Inference, human review, infrastructure and maintenance belong in the investment case. A feature "can win on usage and still destroy margins." That may be worth it only for a specific strategic advantage with a credible path to better economics .

Marty Cagan says much the same. Most companies use AI to speed up the project model, and teams get faster without getting better outcomes. He cites this "AI productivity paradox" as noted by McKinsey and Atlassian . Strong teams separate building to learn (prototyping to find a solution) from building to earn (building something the business can run on and monetize) . As the cost of building to earn falls, "the bottleneck is what do we build?" . On team shape, he says some teams now have three or four engineers instead of five to ten, while what they own is growing . The PM stays responsible for value and business viability: whether it's affordable, monetizable and compliant .

A warning about metrics

A PM at a very large enterprise says a goal to cut median epic cycle time by 15% led teams to clone aging epics and close the old ones. An internal article then celebrated a 35% drop, with no discussion of the real goal of resolving epics within 90 days .

Pricing an AI product with no usage history

An r/ProductManagement thread offers practical steps:

  • Run an announced trial. Absorb costs for two to three months and say upfront that usage pricing will follow. Expect some users to "go hog wild" and then scale back, while moderate users get locked in .
  • Use COGS as the floor, not the price. Build forecasts with finance, and pilot with a select group first . For school buyers, set tiers by what a teacher or class needs per term. Model peak demand from the calendar, not from traffic .
  • Limit usage by tier. Put a hard cap on the free tier and soft caps (throttling or overages) on paid tiers. The soft caps show who would pay for more .

PMs closer to the build

Aakash Gupta argues PMs need design sense because they are now designing. At AI-native companies they ship to production, and at large enterprises they build AI prototypes . He had Claude Code build a feedback-triage app from one prompt and found three problems. The PRD sat about 470px below the fold. The ranking put a theme with $895K in ARR above one with $1.00M without explaining why. The pasted input took up half the screen . In a separate note he describes Rippling CPO Matt MacInnis's first changes: markdown pushed to a git repo, customer issues found through MCP, and PMs fixing their own copy. Gupta's takeaway is that PMs now need skills such as understanding repo structure and configuring tooling, which used to belong to engineers .

A tech-debt standoff with AI-reliant developers

A non-technical product owner says developers will not touch tech debt until the PO writes stories with acceptance criteria, finds and prioritizes the debt, prescribes fixes and sets time limits. The PO's manager wants them at senior-developer level within three months . The developers reportedly say it's a product-owner failure if a story can't be pasted into Claude and produce a first implementation in one pass . Their AI-generated debt list has 7,700 items, such as "Resolve escape: line 33, file XYZ", and they want the PO to rank them . The PO thinks the developers should own all of this , and most commenters agree.

Launch videos

Hiten Shah says Claude Code built a Beam launch video in nine minutes but left out the one scene showing what Beam does . After reviewing eight product videos, his test for each scene is: what does the viewer understand after it ? One example is Cursor's video, which reaches "All Checks Passed" and a merge button around 19 seconds in. Developers recognize that payoff, and he would hold on it a beat longer .

Ravi Mehta and Marty Cagan: AI makes building cheap, so PMs have to own the outcome
Summary
Coverage start
1 day ago
Coverage end
14 hours ago
Frequency
Daily
Published
12 hours ago
Reading time
4 min
Research time
3 hrs 55 min
Documents scanned
177
Documents used
14
Citations
24
Sources monitored
98 / 99
Insights
Skipped contexts
Source details
Source Docs Insights Status
rahulvohra 0 0
Paul Graham 3 0
Tony Fadell 0 0
Patrick Collison 0 0
Daniel Ek 0 0
Gustaf Alströmer 0 0
Stewart Butterfield 0 0
PM Diego Granados 0 0
👨🏻‍💻☕️ 0 0
scott belsky 4 3
Ryan Hoover 1 0
Janna Bastow simplybastow.bsky.social 0 0
Jackie Bavaro 0 0
Sachin Rekhi 0 0
Dan Olsen 0 0
The community for ventures designed to scale rapidly | Read our rules before posting ❤️ 24 3
Will Lawrence 0 0
Product Marketing 2 0
Ami Vora 0 0
PM Interview: Practice Group for Product Manager Case Interviews 0 0
One Knight in Product 0 0
Aakash Gupta 5 1
Shreyas Doshi's Product Almanac | Substack 0 0
Lenny Rachitsky 0 0
Acquired 0 0
a16z 1 1
Exponent 1 1
Product Alliance 0 0
Product Management Exercises 0 0
rocketblocks 0 0
Product Design 4 0
ProductManagementJobs 12 2
Product Management 78 5
Product Management - The place for all things product 8 3
Product Management 0 0
Aspiring and current tech PM's 0 0
Masters of Scale 1 1
Product Science Group 0 0
How I built This 0 0
SaaStr AI 0 0
productized io 0 0
Lenny's Reads 0 0
The Product Folks 0 0
Strategyzer 0 0
Lenny's Podcast 0 0
AJ&Smart 0 0
Y Combinator 1 1
Product School 0 0
Mind the Product 0 0
@andrewchen 0 0
The Looking Glass 0 0
Leah’s ProducTea 0 0
Run the Business 0 0
Product Managers at Work 0 0
The Product Compass 0 0
Ravi on Product 1 1
Productify by Bandan 0 0
Product Thinking with Melissa Perri 0 0
Product Talk Daily 0 0
The Beautiful Mess 0 0
Gibson Biddle's "Ask Gib" Product Newsletter 0 0
Casey Accidental 0 0
Hiten Shah 21 2
Product Growth 1 1
Perspectives 1 1
Lenny's Newsletter 0 0
andrew chen 0 0
Brian Balfour 0 0
Casey Winters 0 0
elena verna 0 0
Kevin Weil 🇺🇸 2 1
April Underwood 0 0
Julie Zhuo 2 1
Marty Cagan 0 0
Lenny Rachitsky 3 1
Christian Idiodi 0 0
John Cutler 0 0
Teresa Torres 0 0
Gibson Biddle 0 0
Shreyas Doshi 0 0
Adam Nash 0 0
Merci Grace 0 0
Jackie Bavaro 0 0
Hunter Walk 0 0
Brian Balfour 0 0
Scott Belsky 0 0
Nir Eyal 0 0
Teresa Torres 0 0
Julie Zhuo 0 0
Andrew Chen 0 0
John Cutler 0 0
Ken Norton 0 0
Gibson Biddle 0 0
Elena Verna 0 0
Casey Winters 0 0
Shreyas Doshi 0 0
Lenny Rachitsky 0 0
Melissa Perri 0 0
Marty Cagan 1 1