Pricing narrative · Lifecycle

Price certainty is part of the product.

A messaging, communications, and field-enablement response to GitHub Copilot's shift to usage-based billing. Written 18 August 2026, pre-decision, for Copilot GTM leadership. Revised 16 September 2026.

RolePMM · internal recommendation
DomainDeveloper tools · Pricing
TriggerUsage-based credits, live 1 June 2026
DecisionRequired by 1 September 2026
The situation

The transition landed. The invoice has not.

On 1 June, premium requests were replaced by metered AI Credits across every plan. Base prices held: Business $19, Enterprise $39 per user per month. Completions stay free; chat, CLI, agents, and code review are metered.

Promotional credits for existing customers replaced the standard allowance from June to August only; they were not added on top. The backlash so far is almost entirely individuals. Enterprise is still silent, which is the tell: the real exposure hasn't hit a finance team yet.

Included AI allowance, per user / monthPromotional credits replaced the standard allowance, and ended 1 September
Business · Jun–Aug$30
Business · from Sep 1$19
Enterprise · Jun–Aug$70
Enterprise · from Sep 1$39

On 1 September, included usage falls by up to 44%: Business −37% (3,000 to 1,900 credits), Enterprise −44% (7,000 to 3,900 credits). Seat prices do not change.

The diagnosis

We didn't raise prices. We removed the ability to forecast them.

A cost increase

is absorbed negotiated at renewal stays inside engineering · Quiet.

A forecasting failure

is escalated reaches finance, triggers procurement review ends in a spend freeze · Loud.

We produced the second and are being criticised for the first. Every fix that adjusts price solves the wrong problem. Credits burn on tokens at each model's API rate, and the person choosing is a developer mid-task with no budget context.

The mechanism

The safety net came out in the same release as the meter.

Before

Allowance runs out Model falls back Work continues, degraded · Graceful. No decision required.

After

Allowance runs out No fallback exists Overage by default, or work stops · Binary. Overage unless an admin opts out.

The field is selling budget caps as the answer to unpredictability. The cap is also an off switch. We tell admins predictable spend is one setting away, without telling them that setting can stop their developers mid-task. Overage stays on unless an admin disables it, and a user budget can block a developer while the pool still has credits.
The sensitivity

What 1,000 Enterprise seats pay in September.

Monthly cost at 1,000 Enterprise seats, by average September usage3,900,000 pooled credits included ($39K) · overage at published rates · directional, not a forecast
3,500 credits per seat$35K · no overage
5,250 credits per seat$52.5K · $13.5K overage
7,000 credits per seat$70K · $31K overage

At full promotional usage: ~$31K of monthly overage, billed by default. Below 3,900 credits per seat September adds nothing; above it every credit is billed, and the customer can't see in advance which side of that line they land on.

Positioning

From predictable seat to governed platform.

Was

"One price per developer. Stop thinking about it."

→

Is

"Spend you can see, attribute, and govern before it happens."

For the platform lead who now owns a variable AI budget they're accountable for, Copilot meters agentic work against a pooled organisation allowance, with budgets at enterprise, cost centre and user level, so spend is attributable, can be capped, and holds up in a budget review.

What it deliberately does not claim: that the bill is predictable. It isn't, and claiming otherwise breaks trust a second time.

Messaging

One reposition. Three translations.

D

Developer · Sees the meter. Completions stay free; credit cost shows at the point you pick a model. · "See the cost before you commit."

P

Platform lead · Owns allocation. Pooled usage removes stranded capacity; budgets at enterprise, cost-centre, or user level. · "Allocate by cost centre, not by seat."

F

Finance · Sees the variance. On exhaustion the organisation decides: continue at published rates, or cap. · "You choose the ceiling in advance."

Competitive

Everyone has this problem. Not everyone shows the customer.

Agentic coding consumes frontier inference. That cost is real for every vendor. The only question is who absorbs the variance, and for how long.

Flat-rate seat · the easier sell

Predictable invoice, easy to buy Vendor absorbs variance, then rations quietly through throttles, fair-use limits and downgrades at peak Spend can't be attributed, because there's no spend to attribute

Metered & governed · Copilot, from 1 June

Spend is attributable and can be capped in advance The invoice moves The trust cost is paid up front, in public, which is where we're standing now

Speculation. Flat-rate agentic pricing doesn't survive current inference economics. Vendors still selling it will meter, and their customers will arrive with no allocation model at all.
Execution

Land the cliff before it lands on them.

19 Aug

Admin notification · Every admin sees their own June–August consumption beside their standard September allowance.

19 Aug

Field briefed first · AEs and CSMs get the cap trade-off before customers get the email.

25 Aug

Guided configuration · CSM-led budget setup, ranked by projected gap rather than by ARR.

1 Sep

Say it plainly, in public · Changelog and docs state that promotional credits have ended. Silence converts a billing change into a trust story.

Early Oct

First unsubsidised invoice · Outreach to every account above forecast before they open it.

The dependency

One ask. Marketing can't close this alone.

When the pool is exhausted and the organisation has chosen to cap, route to a low-cost model at reduced concurrency instead of stopping. The admin keeps a hard spend ceiling. The developer keeps a working tool.

Why this and not a discount. A taper postpones the conversation by one cycle and costs revenue in every cycle after. A floor is paid for once.

If it's declined. The claim weakens from governed to attributable. The fallback is alerting well ahead of the ceiling and a named approval path, which manages the stop rather than preventing it.

Measurement

Four numbers, and what would prove me wrong.

Budget configuration rate

Organisations with a budget set at any level, by 30 September.

Cap proximity in week two

Share of orgs whose usage approaches their own ceiling within 14 days. The only signal that arrives early enough to recalibrate.

Forecast gap at first invoice

Admin projection against actual October spend. The direct measure, and the number I'd be held to.

Billing cited in Q4 churn

Non-renewals naming predictability. Lagging and contaminated. Read alongside 03, never alone.

Falsification. If the October gap is wide and configuration is high, the diagnosis was wrong and this memo should be withdrawn, not iterated.

Naveen Raj Kanagaraj · M.S. Marketing Analysis, DePaul University · Independent analysis, not affiliated with the companies named.