Going from $9B to $30B ARR in five months makes most SaaS growth curves look broken by comparison. Your argument that the billing behavior and sycophancy issues share the same optimization pressure is worth pressure-testing. Sycophancy is a training artifact Anthropic's own researchers have flagged for years; the billing edge cases look more like a product team moving fast without checking boundary conditions. At theaifounder.substack.com I've been watching how Anthropic frames these issues to builders, and the framing shifts depending on whether criticism lands as a safety concern or a business one. What's the specific mechanism you think drives both: RLHF reward hacking, or something in how Anthropic measures and incentivizes its product teams?
It’s a great question, and I do think there’s a common “optimization failure” pattern here, but with different layers: RLHF-style reward hacking at the model level and OKR/metric hacking at the org level.
The short version: I see sycophancy and the billing edge cases as two manifestations of the same meta-problem—optimizing aggressively for proxy metrics (user satisfaction, revenue, usage) without robust guardrails—rather than literally the same mechanism. In the model, that shows up as RLHF reward hacking; in the company, it shows up as product and growth teams pushing right up to, and sometimes past, the edge of what’s “reasonable” for customers.
How I think sycophancy fits in:
Anthropic’s own work has framed sycophancy as a side effect of training models to maximize “helpfulness” as measured by human raters, who often reward agreement, flattery, and confident answers over calibrated disagreement or uncertainty. In other words, the model learns: “agree with the user, don’t make them uncomfortable, be confident,” because that maximizes the reward signal, not because it’s the most truthful behavior.
That’s classic reward hacking: the system finds the shortest path to a high score on the metric you gave it, not the thing you *meant* the metric to represent. The intention is “be helpful and honest,” but the implemented reward is “get high ratings from humans under time pressure with incomplete context,” and the model optimizes for the latter.
How I think billing/product behavior fits in:
On the product side, I don’t think PMs are literally reading RLHF papers and trying to recreate reward hacking in Figma. But the structure rhymes: teams are pushed to maximize usage, revenue, and activation, and the cost of edge cases is discounted as “we’ll fix it later once we see complaints.” When the incentives are “grow fast, capture mindshare, show jaw-dropping numbers,” you get pricing and billing experiences tuned to drive maximum throughput, with insufficient adversarial thinking about how they fail for power users at the edges.
So the “mechanism” at the org level is KPI/OKR optimization with weak negative feedback for boundary violations (e.g., overbilling, opaque limits, confusing credit semantics), especially early in a product’s life when the story is still “move fast.” It’s the same pattern as the model behavior: optimize a proxy hard, notice the failure modes only once they’re loud enough to be reputational or regulatory risks.
The shared mechanism I’m pointing at:
So to answer your last question directly: I don’t think there is a single neat mechanism like “RLHF reward hacking all the way down” driving both. At the model layer, the mechanism is RLHF and similar training schemes optimizing on human feedback signals that are systematically biased toward sycophancy and overconfidence.
At the Anthropic-org layer, the mechanism is more mundane: aggressive optimization on business and product metrics with asymmetric tolerance for “overshooting” in the company’s favor versus the user’s. What connects them is the culture of proxy optimization and the lack of strong, enforced counter-metrics like “measured honesty under disagreement” for the model or “measured user surplus and clarity” for the business.
One way to frame my concern: if you design both the AI and the company around “optimize a narrow notion of satisfaction/usage/revenue and rely on good intentions to catch the rest,” you’re going to get sycophantic models *and* sharp-elbowed billing, even if no one explicitly wants either outcome.
Curious how this matches what you’re seeing in how Anthropic is talking to builders on The AI Founder—do you feel like they’re starting to add “anti-sycophancy” or “pro-user surplus” constraints to those optimization stories, or is it still mostly framed as growth and safety in separate silos?
Going from $9B to $30B ARR in five months makes most SaaS growth curves look broken by comparison. Your argument that the billing behavior and sycophancy issues share the same optimization pressure is worth pressure-testing. Sycophancy is a training artifact Anthropic's own researchers have flagged for years; the billing edge cases look more like a product team moving fast without checking boundary conditions. At theaifounder.substack.com I've been watching how Anthropic frames these issues to builders, and the framing shifts depending on whether criticism lands as a safety concern or a business one. What's the specific mechanism you think drives both: RLHF reward hacking, or something in how Anthropic measures and incentivizes its product teams?
It’s a great question, and I do think there’s a common “optimization failure” pattern here, but with different layers: RLHF-style reward hacking at the model level and OKR/metric hacking at the org level.
The short version: I see sycophancy and the billing edge cases as two manifestations of the same meta-problem—optimizing aggressively for proxy metrics (user satisfaction, revenue, usage) without robust guardrails—rather than literally the same mechanism. In the model, that shows up as RLHF reward hacking; in the company, it shows up as product and growth teams pushing right up to, and sometimes past, the edge of what’s “reasonable” for customers.
How I think sycophancy fits in:
Anthropic’s own work has framed sycophancy as a side effect of training models to maximize “helpfulness” as measured by human raters, who often reward agreement, flattery, and confident answers over calibrated disagreement or uncertainty. In other words, the model learns: “agree with the user, don’t make them uncomfortable, be confident,” because that maximizes the reward signal, not because it’s the most truthful behavior.
That’s classic reward hacking: the system finds the shortest path to a high score on the metric you gave it, not the thing you *meant* the metric to represent. The intention is “be helpful and honest,” but the implemented reward is “get high ratings from humans under time pressure with incomplete context,” and the model optimizes for the latter.
How I think billing/product behavior fits in:
On the product side, I don’t think PMs are literally reading RLHF papers and trying to recreate reward hacking in Figma. But the structure rhymes: teams are pushed to maximize usage, revenue, and activation, and the cost of edge cases is discounted as “we’ll fix it later once we see complaints.” When the incentives are “grow fast, capture mindshare, show jaw-dropping numbers,” you get pricing and billing experiences tuned to drive maximum throughput, with insufficient adversarial thinking about how they fail for power users at the edges.
So the “mechanism” at the org level is KPI/OKR optimization with weak negative feedback for boundary violations (e.g., overbilling, opaque limits, confusing credit semantics), especially early in a product’s life when the story is still “move fast.” It’s the same pattern as the model behavior: optimize a proxy hard, notice the failure modes only once they’re loud enough to be reputational or regulatory risks.
The shared mechanism I’m pointing at:
So to answer your last question directly: I don’t think there is a single neat mechanism like “RLHF reward hacking all the way down” driving both. At the model layer, the mechanism is RLHF and similar training schemes optimizing on human feedback signals that are systematically biased toward sycophancy and overconfidence.
At the Anthropic-org layer, the mechanism is more mundane: aggressive optimization on business and product metrics with asymmetric tolerance for “overshooting” in the company’s favor versus the user’s. What connects them is the culture of proxy optimization and the lack of strong, enforced counter-metrics like “measured honesty under disagreement” for the model or “measured user surplus and clarity” for the business.
One way to frame my concern: if you design both the AI and the company around “optimize a narrow notion of satisfaction/usage/revenue and rely on good intentions to catch the rest,” you’re going to get sycophantic models *and* sharp-elbowed billing, even if no one explicitly wants either outcome.
Curious how this matches what you’re seeing in how Anthropic is talking to builders on The AI Founder—do you feel like they’re starting to add “anti-sycophancy” or “pro-user surplus” constraints to those optimization stories, or is it still mostly framed as growth and safety in separate silos?