GitHub's published billing documentation sets no minimum seat count for Copilot Business. It states that organizations are billed for the number of assigned seats and that you can assign additional seats at any time. The 10-license minimum that buyers keep hearing comes from GitHub Sales conversations, appears nowhere in the docs, and does not apply when you enable the plan yourself through self-service billing. At $19 a seat, buying 10 when you need 5 costs an extra $1,140 a year.
This is one of the few purchasing questions in this market where the vendor is saying two different things in two different places, and where the difference is real money for a small team. It is worth being precise about which is which.
Is there a minimum number of GitHub Copilot Business licenses?
Not according to GitHub's documentation. The billing concepts page for Copilot licenses lists Copilot Business at $19 per user per month and then describes seat behaviour without a floor: a seat is a license for one user, organizations and enterprises are billed for the number of assigned seats at the end of each monthly billing cycle, and you can assign additional Copilot seats at any time. The seats and billing cycles page repeats it. Neither page contains the word minimum in relation to a purchase quantity.
What exists alongside that is a well-documented pattern of buyers being told otherwise. In a GitHub community discussion opened in July 2026, an organization reported being told by GitHub Sales that "Copilot Business is available for teams purchasing 10 or more licenses". Several other organizations replied describing the same experience. No GitHub employee responded to the thread to confirm, deny or clarify it, and the original poster noted they could find no reference to the rule in the official documentation. That is still the position today.
So the practical answer has two halves. If a salesperson is quoting you, a 10-license floor may well be part of that quote. If you set Copilot up yourself on an organization through the billing settings, you assign the number of seats you actually need and the documented per-seat billing applies.
How much does GitHub Copilot Business cost per seat?
Copilot Business is $19 per user per month, billed monthly, and each license contributes 1,900 AI credits to a pool shared across the enterprise. Copilot Enterprise is $39 per user per month with 3,900 credits per seat and requires GitHub Enterprise Cloud. Usage beyond the pooled credits bills at $0.01 per AI credit. One detail worth holding on to when you size a plan: code completions and next edit suggestions are not billed in AI credits at all and stay unlimited on every paid plan, so the credits only matter for agent work, chat and the premium models.
| Plan | Price | Included AI credits | Requires |
|---|---|---|---|
| Copilot Pro | $10 per calendar month | Individual allowance | A personal account |
| Copilot Pro+ | $39 per calendar month | Individual allowance | A personal account |
| Copilot Business | $19 per user per month | 1,900 per seat, pooled | An organization |
| Copilot Enterprise | $39 per user per month | 3,900 per seat, pooled | GitHub Enterprise Cloud |
| Overage on either business plan | $0.01 per AI credit | Drawn after the pool empties | An admin who has allowed it |
The pooling is the part that makes a business plan behave differently from a pile of individual plans. Credits land in one enterprise pool rather than a per-person bucket, so the two engineers who live inside the agent draw headroom from the six who mostly accept completions. We worked through how that pool behaves under real usage in what GitHub AI credits actually cost.
What does a 10-seat minimum actually cost you?
This is the number that matters, and it is easy to underestimate because $19 sounds small. A floor of 10 seats is $190 a month or $2,280 a year regardless of how many developers you have. Below ten people, every seat you are forced to buy is pure waste.
| Developers who need Copilot | Cost at true headcount | Cost at a 10-seat floor | Wasted per year |
|---|---|---|---|
| 3 | $57/mo | $190/mo | $1,596 |
| 5 | $95/mo | $190/mo | $1,140 |
| 8 | $152/mo | $190/mo | $456 |
| 10 | $190/mo | $190/mo | $0 |
| 25 | $475/mo | $475/mo | $0, the floor stops applying |
There is a softer argument for buying the ten anyway, and it is worth stating honestly rather than dismissing: those unused seats still contribute credits to the shared pool. Ten seats give the pool 19,000 credits a month, which a five-person team using agent mode heavily might genuinely consume. If you were going to overspend on credits at $0.01 each, the extra five seats are 9,500 credits for $95, which is cheaper than the $95 of overage they replace. That arithmetic only works if you are actually a heavy agent shop. For a team that mostly uses completions, which are not credit-billed at all, it is $1,140 a year for nothing.
How do I avoid the 10-seat minimum?
Set the plan up yourself. If your team is on a GitHub organization, an owner can enable Copilot from the organization's billing settings and assign seats one at a time, which is the path the documented per-seat billing describes. The reported minimum attaches to sales-assisted purchases and reseller arrangements, where volume tiers and contract minimums are ordinary commercial practice. Going through a reseller is also where volume discounts start, which is the trade: a floor in exchange for a rate.
If you do end up with a quote, remember it still has to become a purchase order before anyone is paying for anything, and a quote for ten seats commits you to ten seats for the contract term. Getting the count right before the paperwork moves is cheaper than getting it right afterwards, whatever system you raise the purchase order in. Ask for the exact seat count in writing, and ask whether the minimum applies at renewal too.
When are Copilot seats billed, and what happens if I remove one?
Billed users are calculated at the end of each billing cycle based on assigned seats, and the proration is asymmetric in GitHub's favour. Adding seats bills pro rata immediately for the rest of the cycle, and if you pay by card or PayPal you pay that prorated amount up front; the included AI credits for those seats may also be prorated. Removing seats does not stop the billing, which continues to the end of the current cycle. Downgrades take effect at the start of the next cycle and are generally not prorated, while upgrades take effect immediately with proration.
The practical consequence is that seat churn costs you. Adding a contractor for three weeks and removing them bills close to two full months across the two cycles it touches. If you rotate people in and out, size the plan for the steady-state team and accept a short queue rather than adding and removing seats every sprint.
Do unused GitHub Copilot seats still cost money?
Yes. Billing follows assigned seats, not active ones. A seat assigned to someone who has not opened their editor in four months bills $19 the same as a seat belonging to your busiest engineer. GitHub gives organization owners a license usage view and downloadable usage reports, and running that report once a month is the single highest-return administrative habit on this plan. On a 50-seat org, a 20% idle rate is $2,280 a year.
What happens to my personal Copilot Pro plan if I get a company seat?
It cancels automatically and you get money back. GitHub's documentation is explicit: if you have an active Copilot Pro, Copilot Pro+ or Copilot Max plan and are then assigned a seat under a Copilot Business or Copilot Enterprise plan, the personal plan is automatically canceled and you receive a prorated refund for the remaining portion of the current billing cycle. You then use Copilot under your company's policies. Nobody needs to double-pay during a rollout, and nobody needs to remember to cancel.
Should I buy Copilot Business or Copilot Enterprise?
Business at $19 covers what most teams are buying Copilot for: the agent, chat, policy controls, seat management, audit logs and exclusion of your code from training. Enterprise at $39 doubles the seat price and doubles the pooled credits to 3,900, adds priority access to new models and features, and requires GitHub Enterprise Cloud, which is itself a separate and much larger purchase. If you are not already on Enterprise Cloud, Enterprise is not a $20 upgrade, it is a platform migration. We put the two side by side, feature by feature, in Copilot Business vs Enterprise, and priced the agent specifically on the Copilot coding agent.
The question underneath the seat count
Every version of this decision is really the same question: how do you pay for engineering work that does not divide neatly by headcount? Per-seat licensing assumes each developer gets roughly equal value, which is why a ten-seat floor feels unfair to a five-person team and why idle seats feel like a tax. It is a reasonable model for a tool that sits in the editor all day. It fits less well for work you want done in batches.
That is the gap we build for. AgentCode connects to a GitHub or GitLab repository, takes a described task, plans it, edits the code, runs your tests and opens a pull request for a person to review. It never merges on its own. The price is flat at $29 a month billed yearly, with no seat count to negotiate, no credit pool to watch and no overage rate. It does not replace an in-editor assistant, and if your team wants completions while they type, Copilot is the better purchase. It replaces the part of the week where somebody has to sit down and grind through a well-specified change.
If you are sizing a Copilot order right now, the honest sequence is: check what your org actually needs, enable it through self-service if that count is under ten, pull the license usage report monthly, and only take a sales quote if the volume discount beats the floor it comes with. And if the reason you are buying is that tickets are piling up rather than that people want faster autocomplete, see how the agent runs a task end to end and compare that against ten seats before the purchase order goes out.