GitHub Enterprise and Copilot, two SKUs, one negotiation.

GitHub Enterprise and Copilot are two per seat meters sold as one inevitability, and the seat counts, not the unit rates, decide what the combined bill really costs.

How are GitHub Enterprise and Copilot priced?

GitHub Enterprise bills per user per month and Copilot adds a second per seat meter on top, with rates published on the GitHub pricing page. The two SKUs are licensed separately, which is why the combined cost per developer surprises finance teams that approved them in different quarters.

Enterprise agreements negotiate both meters together. Volume, term, and the Microsoft relationship set the discount range.

• GitHub Enterprise seat: the platform license covering repos, actions entitlements, and enterprise controls.
• Copilot seat: the AI pair programmer, tiered Business versus Enterprise, documented on the Copilot features page.
• Consumption extras: Actions minutes, storage, and runners bill on top of seats when included quotas are exceeded.

How do you audit GitHub seats before renewal?

Pull the enterprise billing and members views at least 90 days before renewal; GitHub's own billing documentation shows exactly which identities consume a licensed seat. The gap between licensed and active is your first discount.

What to count

• Dormant users: accounts with no commit, review, or login activity in 90 days.
• Machine and service accounts: automation identities that may not need full enterprise seats.
• Departed contractors: outside collaborators whose engagements ended but whose seats did not.
• Copilot non adopters: licensed Copilot seats with no completion acceptance in the last month.

In our reviews this audit alone cut billable counts 15 to 30 percent. No negotiation skill required, just the export.

What levers move a GitHub and Copilot deal?

The levers that move GitHub pricing are cleaned seat counts, Copilot tier discipline, the Microsoft EA channel, and term traded for true down rights. The customer terms are the baseline; enterprise paper can improve every commercial clause in them.

The Microsoft angle most buyers miss

GitHub is a Microsoft business, and large GitHub spend strengthens your hand in the wider Microsoft negotiation. Run the renewals together where calendars allow; separately, both sellers anchor high.

How do you keep Copilot spend honest after rollout?

Copilot spend stays honest when seats follow measured adoption, reviewed quarterly. Acceptance rate and active user telemetry in the admin console tell you exactly who uses the tool.

• Quarterly reclaim: harvest seats with no activity for 30 days and reassign on request.
• Tier review: confirm Enterprise tier features are actually used before renewing the premium.
• Pilot honestly: measure productivity claims against your own cycle data, not vendor case studies.

Where the common advice on GitHub Copilot negotiation is wrong

The standard advice says license Copilot for every developer because the productivity gain dwarfs the seat price. We disagree. In roughly 20 to 25 GitHub agreements Morten Andersen reviewed in 2024 to 2025, active weekly Copilot usage settled at 40 to 60 percent of licensed seats once the pilot glow faded, and the unused seats funded no productivity at all. The buyer side move is to license to measured adoption, harvest idle seats quarterly, and let teams request seats against a live pool. Blanket licensing is a vendor convenience dressed up as a productivity strategy.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

How to use these numbers

Treat the ranges as negotiation benchmarks, not promises. Your estate sets the baseline; the engagement file tells you what disciplined buyers achieved against the same vendor playbook.

Every dormant seat renews at full rate. The export that finds them takes an afternoon.

What to do next

The moves below turn this analysis into a lower invoice at the next renewal.

A sequence you can run this quarter

1. Export 90 days of member activity from the enterprise admin console.
2. Remove dormant users, departed contractors, and unneeded machine accounts from billing.
3. Map Copilot seats against acceptance telemetry and harvest idle licenses.
4. Right tier Copilot: Enterprise features only where they are demonstrably used.
5. Align the GitHub renewal with the broader Microsoft negotiation calendar.
6. Trade term length for contractual annual true down rights on both meters.

White Paper · GenAI

GitHub Enterprise Copilot Negotiation 2026. The buyer side framework

Read it free.

Read the white paper

Frequently asked questions

How much do GitHub Enterprise and Copilot cost together?

List pricing for both meters is published on GitHub's pricing page, and the combined per developer cost is roughly the sum of the two seats. Enterprise agreements discount both; cleaned seat counts discount them further.

Can GitHub spend go through a Microsoft EA?

Yes. GitHub is a Microsoft business and large agreements can ride the Microsoft enterprise relationship, which unlocks EA style discounts and concessions standalone GitHub renewals rarely match.

How many Copilot seats do enterprises actually use?

In our 2024 to 2025 reviews active weekly usage settled at 40 to 60 percent of licensed seats after initial rollout. Licensing to measured adoption with a quarterly reclaim cycle fits reality better than blanket coverage.

What is the difference between Copilot Business and Enterprise?

Enterprise adds organization tuned features on top of Business at a higher seat rate. Most estates we benchmarked needed the Enterprise tier for a minority of developers, not the whole population.

What seat reductions can we negotiate?

Contractual true down rights allowing annual seat reductions at renewal anniversaries. Without the clause, reductions depend on seller goodwill in the quarter you ask.

Do GitHub Actions and storage cost extra?

Yes, beyond included quotas. Actions minutes, storage, and hosted runners bill as consumption, so estates with heavy CI pipelines should review usage before committing seat counts.