California's New Software Tax Doesn't Say Whether Your AI Consumption Billing Counts
California SB 122, signed by Governor Gavin Newsom on June 29, 2026, reclassifies prewritten software and SaaS as “tangible personal property” subject to state sales tax — regardless of whether it’s downloaded, streamed, or accessed through a browser — effective January 1, 2027. Combined with local district taxes on top of the state’s 7.25% base rate, Jason Lemkin’s SaaStr calculates the effective tax on most California software purchases lands around 8-10%, with the state projecting roughly $2 billion in combined annual state and local revenue from the change. Buyers get no input tax credits or refunds on that increase; vendors have to register and start collecting unless they fall under a $5-million-per-purchaser annual threshold.
Custom software, infrastructure-as-a-service, platform-as-a-service, and human-delivered electronic services are explicitly excluded — but the law is silent on how consumption-based AI billing gets classified, which matters because that’s exactly the pricing model AI vendors are converging on. Anthropic’s May 2026 shift is the clearest example: it moved from flat per-seat pricing ($200/month premium, $40/month standard) to a model where Claude.ai costs $10/month and Claude Code costs $20/month, with actual spend driven by token usage, model selection, and Agent SDK credits that expire monthly without rollover. Forrester analyst Tracy Woo’s framing at the time — “token usage, model selection, Claude Code adoption, and commitment levels will have a far greater impact on spend than seat counts” — is precisely the ambiguity SB 122 leaves unresolved: is a California customer’s monthly token bill a taxable software purchase, an untaxed service, or something the state hasn’t defined yet?
For RevOps and sales teams negotiating California renewals, the practical move is modeling the 8-10% increase into contracts closing before January 2027 regardless of how the AI-consumption question eventually gets settled — and treating any vendor guidance that arrives between now and then as the real signal to watch, since neither SB 122 nor precedent has settled how a state taxes a bill that changes size based on how much of a model you actually used that month.