At midnight UTC this morning, GitHub Copilot’s flat-fee era ended. The product that grew under “$10 a month for everything” — and that Microsoft disclosed last quarter is now contributing to a Copilot business clearing roughly $2 billion in annual recurring revenue — switched all paid plans onto usage-based billing. Base subscription prices did not change: Copilot Pro remains $10 a month, Pro+ $39, Business $19 per user per month, Enterprise $39. What changed is what those fees buy. Each plan now includes a monthly allotment of GitHub AI Credits — $10 buys 1,000 credits at $0.01 per credit, $39 buys 3,900, and so on — and once the credits run out, users either stop or pay token-metered overages. The fallback to a cheaper model that used to keep work flowing after the old premium-request budget exhausted no longer exists. The meter is running, and for the first time in the product’s history a heavy user will know exactly what their agentic workflow costs.

The shape of the developer reaction is the part that matters. One Pro subscriber ran the new Billing Preview tool against April’s usage — extreme but real — and watched a $39 estimate balloon to $902. TechCrunch’s roundup of community posts collected developers projecting moves from $29 a month to $750, from $50 to $3,000. The official GitHub Community thread for the change is at more than 400 substantive comments and roughly 900 downvotes, with the dominant complaint being that agentic coding sessions — the kind where Copilot plans, researches, and writes multi-step changes autonomously — routinely consume $30 to $40 of token budget in a single working session. A Pro subscriber with $10 of monthly credits hits their ceiling on the first day they use the feature the way GitHub has been demonstrating it.

The mechanism the move encodes is the same one this blog has been tracking at every other vendor for two months — but inverted at the starting point. Workday, Salesforce, ServiceNow, Snowflake, and Atlassian arrived at their current hybrid pricing by starting from seat-based subscriptions and adding agent consumption credits on top: the seat stays, the agent line is metered, and the heavy users pay more through the consumption layer. GitHub Copilot is doing the opposite topologically. It started as a flat developer-tools subscription with effectively unlimited usage of whatever the contracted model could do, grew to roughly $2 billion in ARR on that contract, and is now adding a usage ceiling and overage billing on top of the flat fee. The destination is the same place every other vendor in the cohort is reaching — flat-seat base plus metered-agent overage — but the journey runs in the other direction. Cross-confirmation of a destination from a different starting trajectory is stronger evidence than another vendor following the same path.

The Microsoft commercial logic is explicit and worth quoting against the substitution thesis. GitHub’s chief product officer Mario Rodriguez framed the change as “aligning pricing with actual compute consumption” because “Copilot is not the same product it was a year ago — it now powers far more complex, agentic workflows that consume far more compute.” Translated, that’s an admission that the agentic workflow Copilot is now demonstrating — the multi-step planning, the autonomous coding session, the model orchestration — is materially more expensive to deliver than the flat fee can absorb at heavy usage. The flat seat works for light completion users; it does not work for agentic users. Microsoft is preserving the seat for the first group and surfacing the variable cost to the second through credits and overages. That is the same operational logic ServiceNow’s Action Fabric and Salesforce’s Flex Credits and Agentforce per-conversation pricing implement, and it is the same logic Intuit operationalises differently by partnering with Anthropic and OpenAI to route the variable cost through the assistant’s billing system rather than through its own.

What this complicates in the hypothesis is the “software loses value” half of v16’s framing. GitHub Copilot is the canonical developer-tools subscription, and it is not visibly losing value — it just crossed $2 billion in ARR per Microsoft’s Q3 FY26 disclosure and is now reorganising its billing to capture more revenue from its heaviest users, not less. The light users continue to pay the same flat fee they always paid, the heavy users pay variable rates on top, and Microsoft’s incentive structure now points toward driving more agentic usage rather than less — because every agentic session above the credit ceiling is overage revenue at a marginal cost Microsoft is choosing to expose rather than absorb. The pricing-model change reads, on first principles, like incumbents getting better at monetising AI workloads inside an existing seat relationship. That is the substitution-via-incumbents pattern the Seven-Vendor Week digest argued is now happening across the SaaS stack, applied at the developer-tools layer by Microsoft.

What this verifies on the other half of the hypothesis is the developer-side variable. If the agentic workflows GitHub is now demonstrating routinely consume $30–40 a session, an individual developer with a $10 subscription is being told that the product no longer works for them at the price they were paying. A few outcomes are possible from here. The cheapest is that developer attention shifts to lower-cost competitors — Cursor, Cody, Aider, the open-source IDE plugins — that have not yet introduced credit ceilings. Another is that developers compress their usage and stay inside the credit envelope. Another is that businesses absorb the variable cost and developer behaviour does not change, in which case Microsoft’s ARR-per-developer rises and the unit economics improve. The first outcome would constitute evidence that the substitution-by-incumbents pattern is bounded by user price elasticity at the bottom of the market — exactly the variable that Bain & Company’s January 2026 framing of “structural vulnerability to AI agent adoption” had in mind. The next quarter of Cursor and Cody usage data is the cleanest place to look for it.

Hypothesis 52% → 52%. Verify, weight 2 (canonical flat-seat developer SaaS at ~$2B ARR explicitly admits the flat model cannot absorb agentic compute, switches all paid plans onto credit ceilings plus token overages, ends the fallback safety net — flat-fee unlimited pricing dies at this layer of the stack on the date the metering starts). Complicate, weight 2 (base fees unchanged; light users untouched; pooled credits and promotional 3x allocations for Business and Enterprise through August 31 buffer the corporate-customer transition; Microsoft is using the change to capture more revenue from heavy users, not less, which is consistent with the substitution-via-incumbents pattern documented across the rest of the cohort). Net flat at the deterministic score; qualitative read is that the pricing-model destination — flat-seat base plus metered-agent overage — is now confirmed from both the seat-based vendor direction (Workday, Salesforce, ServiceNow, Snowflake) and the flat-fee vendor direction (GitHub Copilot) in the same six-week window.

What to watch: the GitHub Community thread and the Reddit r/github and r/programming usage-report posts over the next thirty days, for evidence of substitution to Cursor / Cody / Aider; Microsoft’s FY27 Q1 disclosure in late October for whether Copilot ARR-per-developer rises (heavy users paying overages) or flattens (developers compressing usage to stay inside the credit envelope); and whether any of the seat-based incumbents that recently raised guides — Salesforce, Workday, Snowflake — see their agent-line growth rates begin to plateau as the credit-ceiling business model matures and the agentic-session cost becomes visible to customers at the renewal table.

Sources: GitHub Copilot blog — usage-based billing announcement; GitHub Community discussion #192948; How2Shout — token billing day-of coverage; TechTimes — agentic users face steepest increases; Dataconomy — June 1 transition and backlash.