Run the Ten-Seat Copilot Business Decision Before the Discount Ends
Use one checklist to decide who gets Copilot Business, budget the renewal, and avoid buying seats before the promo ends.
Treat the discount as a test budget
You have a short list of seats and a decision to make before the promo window closes. The $18 Copilot Business add-on price is a first-year incentive that requires a one-year commitment, and the listed promo ends September 30, 2026.
For annual-billing subscriptions placed from July 1 through September 30, 2026, the Microsoft 365 Copilot Business add-on costs $18 per user per month instead of $21.
Monthly billing changes the price to $25.20 per user per month, but the purchase still requires a one-year commitment.
The $3 monthly gap between the $18 and $21 prices equals $36 per user per year.
The discount is a lower-cost window to test a small number of seats, not a signal to roll out. If the use case is a demo, the discount only makes the demo cheaper. The seat needs a use case, an owner, a renewal budget, and a confirmed annual commitment before the purchase is made.
Price the seat before you name the person
Copilot Business can be purchased directly on top of Microsoft 365 Business Basic, Standard, or Premium when the organization has fewer than 300 users.
Organizations above 300 users are outside the promo and fall under an enterprise Copilot add-on priced at $30 per user per month.
The Business Standard bundle with Microsoft 365 Copilot is $23.50 per user per month, and the Business Premium bundle is $32 per user per month, each on an annual commitment.
Use those bundle prices when the base plan is already in place, because the add-on decision should sit in the same review as the base subscription. If the team is already reviewing its base plan, the add-on belongs on the same agenda. Otherwise, the purchase is likely a side quest.
The owner should already own the recurring task, not be the person who is curious about the tool. Name a task the team would do anyway: drafting a summary, pulling together a document, or preparing a follow-up. When the task only exists because the tool exists, the seat will not survive the review.
Run the checklist in a single meeting
Keep the decision visible on one page for the team, not in a thread or a side conversation. Each field is testable in a short meeting, and the same checklist can be used for each seat, so the team does not need a separate memo for every purchase.
- Use case: a recurring task, not a demo, with a named owner.
- Base plan: the current base tier already in place.
- Annual cost: the price for the seat on annual billing, not monthly billing.
- Renewal: the year-two price, budgeted before purchase.
- Owner: the person who will use it regularly and report back.
- Review date: the date before renewal when the seat is kept or removed.
Run the review like a document, not a brainstorm. Put the checklist in the shared meeting doc, read each seat aloud in the order of the recurring task, and stop when a field is blank. A blank field is a no until the team can fill it from the work, not from enthusiasm.
Fill the fields before the purchase, not after. The renewal field is the budget line: use the $21 price as the year-two number, and put that renewal in the ops budget the same week.
Say no when the only reason is the discount, the owner is a placeholder, the review date is after renewal, or the base plan would have to change just to make the add-on look cheaper. A discount can make a bad seat cheaper, but it cannot make the seat useful.
Buy only when every field is filled. The purchase should be easy to reverse at renewal. If the seat did not change a recurring task, the budget should already know the cost of keeping it.