Microsoft 365 and Copilot negotiation
Teams Phone and the add on stack
Teams Phone rarely arrives alone; it comes with a stack of add ons, calling plans, audio conferencing, premium meetings, and contact centre, each a separate line that grows the deal. Sizing every add on to the seats that genuinely need it, rather than the whole estate, is the move that keeps the stack honest.
Key takeaways
- The Teams Phone stack is several separate lines: the phone licence, a calling plan or direct routing, audio conferencing, and optional premium add ons.
- The cost depends on how many seats actually need each component, not on the total headcount.
- About 60 percent of vendors mask increases, often by bundling add ons into a single price, so value each line on its own (published market figure).
- The counter is per seat right sizing, a direct routing comparison, credit for bundled modules, and a SKU level price lock.
What is in the Teams Phone add on stack?
The Teams Phone stack typically includes the Teams Phone licence itself, a calling plan or direct routing for external calls, audio conferencing for dial in meetings, and sometimes premium meeting and contact centre add ons. Each of these is a separate line on the quote, so the total depends on how many seats genuinely need each component rather than on the size of your organisation. A stack priced for the whole estate when only a fraction will make external calls is the classic oversize.
The reason the stack matters is that it is easy to wave through as a single telephony number. Broken into its parts, it is a set of independent decisions, and most organisations need the full stack for only a subset of users. Reading the stack line by line is the same discipline we apply to any quote in the SaaS Negotiation Guide.
How do you size each add on to real use?
You size each add on by matching it to the seats that will actually use it, not the seats you have. Most organisations have a calling population that is far smaller than the total headcount: knowledge workers who rarely place external calls do not need a calling plan, while a customer facing team might need the full stack including contact centre. Pull the usage profile before you accept a quantity, the same way you would with any seat line.
This is where shelfware hides. A calling plan attached to every seat, when only a third place external calls, is pure margin for the vendor and waste for you. About 60 percent of vendors mask increases, and bundling add ons across the whole estate is one of the quieter ways it happens. Right sizing each line to real adoption is often a larger saving than any discount on the headline rate.
| Add on | What it covers | Sizing question |
|---|---|---|
| Teams Phone licence | Calling capability inside Teams | Which seats actually need to make calls? |
| Calling plan or direct routing | The external call path and minutes | Is direct routing cheaper at your call volume? |
| Audio conferencing | Dial in access to meetings | Is it already bundled in your suite tier? |
| Premium meetings | Webinars and advanced meeting tools | Who runs events, and how often? |
| Contact centre | Customer facing call handling | Limit to the customer facing team only. |
Calling plan or direct routing: which is cheaper?
The calling plan versus direct routing choice is one of the largest levers in the stack. A Microsoft calling plan is simple to buy but priced per seat with bundled minutes, while direct routing connects your own telephony carrier and can be far cheaper at higher call volumes. The right answer depends on your call profile, so model both against your actual minutes before you accept the default. Vendors lead with the calling plan because it is the easier sale, not because it is always the cheaper one.
Check too for audio conferencing that is already included in your suite tier. Some conferencing capability ships with higher tiers, so paying for it again as an add on is paying twice. Mapping that overlap is the same move we describe for E5 in the E5 upsell and what it is worth.
The stack feeds the renewal
An oversized add on stack does not just cost more today; it raises the base for every future renewal. AI driven renewal asks run 20 to 37 percent in 2026, against a historical 3 to 9 percent annual uplift, and an inflated stack means a larger absolute increase when that percentage is applied. Trimming the stack now lowers the base the uplift compounds on later, which is why right sizing pays twice.
Get the full negotiation method
The SaaS Negotiation Guide walks through sizing add ons, building leverage, and locking the terms, with the 2026 facts and the counter for each vendor tactic.
Download guide →How do you lock the stack so it does not drift?
You lock the stack by fixing the per unit price of each add on at the SKU level for the full term, so no single line can drift upward at the next renewal. Unbundle the stack on the quote, value each component on its own, and keep only what your sized population needs. A stack you cannot break apart is a stack you cannot benchmark, and a price you cannot benchmark is a price you cannot trust.
Bring the add on stack into the same conversation as your suite renewal and any Copilot decision, because Microsoft values the whole relationship. We cover the seat side in negotiating Copilot into the EA, and the full commercial deal runs through our Microsoft 365 and Copilot negotiation service. Start 6 or more months before the renewal so you have time to profile usage and model the calling options.
Frequently asked questions
What is in the Teams Phone add on stack?
The Teams Phone stack typically includes the Teams Phone licence itself, a calling plan or direct routing, audio conferencing, and sometimes premium meeting and contact centre add ons. Each is a separate line, so the cost depends on how many seats genuinely need each component.
How do you negotiate the Teams Phone add on stack?
Size each add on to the seats that actually need it rather than the whole estate, compare direct routing against a Microsoft calling plan, value any module already bundled into your suite, and lock the per unit prices at the SKU level so the stack cannot drift upward at renewal.
Related reading: the E5 upsell and what it is worth and negotiating Copilot into the EA.
Newsletter
The SaaS Spend Brief
One SaaS pricing development and one negotiation move you can make this week. Short, useful, buyer side.