Copilot, Gemini, Amazon Q. Priced side by side for 2026.

Microsoft 365 Copilot and Gemini for Workspace both anchor near 30 dollars per user per month while Amazon Q undercuts them at 20, so the real decision is suite fit, data exposure, and how hard you push the pilot math.

How do Copilot, Gemini, and Amazon Q price per user in 2026?

Microsoft 365 Copilot and Gemini for Workspace both anchor near 30 dollars per user per month on annual commitment, while Amazon Q Business lists near 20 dollars with a lighter lite tier below it.

Microsoft 365 Copilot requires a qualifying Microsoft 365 base license. Gemini for Workspace has folded into Workspace editions with AI included at higher per seat rates.

The sticker is only the anchor. Every proposal we benchmarked opened at list, and every committed deal closed below it.

Why does the base license requirement matter?

Because it reprices the assistant. A Copilot seat on top of E3 is a different total cost than the same seat on top of E5 under the Microsoft 365 enterprise plans, and Microsoft uses Copilot interest to pull E5 upgrades through. Price the stack, not the add on.

Where does each assistant actually win?

Suite gravity decides most deals: Copilot wins Microsoft estates, Gemini wins Google estates, and Amazon Q wins developer and AWS operations workloads. Cross suite bets underperform because adoption depends on the assistant living where people already work.

• Copilot: strongest in Teams meeting summaries, Outlook drafting, and Excel analysis on M365 data.
• Gemini: strongest in Gmail, Docs collaboration, and Meet, with simpler packaging after the 2025 edition changes.
• Amazon Q: strongest for developers, AWS operations, and Q in Connect contact centers, weakest as a general office assistant.

Should you run two assistants side by side?

Usually no. Split estates double the data governance work and halve the negotiation leverage. The exception is a developer population on Amazon Q while the office runs Copilot or Gemini, because the workloads barely overlap.

What are the lock in and data exposure risks?

Each assistant inherits the permission sprawl of its own suite, and oversharing surfaces on day one. Copilot reads everything a user can touch in SharePoint and OneDrive, Gemini reads Drive, and Q reads the connectors you grant.

• Permission debt: years of open shares become visible the week the assistant ships.
• Renewal lock: assistant seats deepen suite dependence, which compounds at the next EA or Workspace renewal.
• Usage data asymmetry: the vendor sees your adoption telemetry; demand the same dashboards in the contract.

What contract terms limit the damage?

Three clauses matter most: a mid term seat reduction right tied to measured usage, a price hold covering at least one renewal, and a commitment that your prompts and grounding data never train shared models.

How should you run the pilot and the negotiation?

Run a 90 day pilot on 5 to 10 percent of the target population, measure weekly active use, and let that number size the order. Buying for everyone and hoping for adoption is the single most expensive pattern in our file.

1. Pick pilot users from the teams with the heaviest document and meeting load.
2. Define weekly active use as the success metric before the pilot starts.
3. Fix permission sprawl in SharePoint or Drive before seat one ships.
4. Take the measured active rate into the seat negotiation as your volume case.
5. Stage the ramp: quarterly seat tranches priced at the committed discount.

What does a good first order look like?

Seats for measured adopters plus 20 percent headroom, a locked unit price for the term, and a written option to add tranches at the same rate. That structure paid for itself within two quarters in every engagement where it landed.

Where the common advice on enterprise GenAI assistants is wrong

The standard advice is to standardize early on one assistant for the whole company so nobody falls behind. We disagree. In roughly 18 to 25 GenAI seat negotiations Morten Andersen advised in 2024 to 2025, enterprise wide day one rollouts produced weekly active rates of 25 to 45 percent, which means most seats were pure waste at 30 dollars per user per month. The buyer side move is to pilot narrow, measure weekly active use, and buy in staged tranches at a committed discount. The vendors price on fear of missing out. Your usage data is the antidote.

What the engagement data shows

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

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Map which productivity suite dominates each user population before shortlisting.
2. Audit SharePoint or Drive permission sprawl before any assistant pilot.
3. Run a 90 day pilot on 5 to 10 percent of users with weekly active use as the metric.
4. Price the full stack including base license upgrades, not the add on alone.
5. Negotiate staged seat tranches with a locked unit price and a reduction right.
6. Demand adoption dashboards and a no training commitment in the order form.

White Paper · Microsoft

Copilot vs Gemini vs Amazon Q. The negotiation framework

Microsoft 365 Copilot vs Google Gemini vs Amazon Q in 2026: the per user metric, the prerequisite stack, and the EA, EDP, and CUD bundle math. Read it free.

Read the white paper

Frequently asked questions

Is Microsoft 365 Copilot or Gemini for Workspace cheaper in 2026?

They anchor at similar levels, near 30 dollars per user per month on annual commitment, so the real cost difference comes from the required base licenses and the discount you negotiate. Copilot needs a qualifying Microsoft 365 plan, while Gemini now ships inside Workspace AI editions.

How much cheaper is Amazon Q than Copilot or Gemini?

Amazon Q Business lists near 20 dollars per user per month, roughly a third below the other two. It is strongest for developer and AWS operations use, and weakest as a general office assistant inside documents and email.

Can you negotiate Copilot, Gemini, or Amazon Q pricing?

Yes. Committed seat deals closed 20 to 30 percent below list across all three vendors in our 2024 to 2025 engagement file. Volume, multi year terms, and staged tranches at a locked unit price are the levers that move the number.

What adoption rate should we expect from a GenAI assistant rollout?

Plan for 25 to 45 percent weekly active use after the novelty quarter, with a median near 38 percent in our engagements. Size the order on measured pilot adoption, not on headcount.

Do these assistants train on our company data?

All three vendors state that enterprise customer content is not used to train shared models under business terms, but the commitment belongs in your contract. Put a no training clause in the order form rather than relying on policy pages.

Should we wait for prices to fall before buying?

Waiting has a real option value because per seat list prices are under pressure from bundling. If you buy now, lock a price hold through renewal and a seat reduction right so a falling market cannot strand you above it.