How should ServiceNow price Now Assist against Microsoft Copilot in 2027?

The Pricing Math Today (May 2026 list)

• Microsoft Copilot 365: ~$30/user/mo, requires M365 E3/E5 underneath (~$36-57/user/mo) — total stack ~$66-87/user/mo
• Microsoft Copilot for Sales: ~$50/user/mo (or $20 with Sales Premium)
• Microsoft Copilot for Service: ~$50/user/mo standalone
• Microsoft Copilot Studio: ~$200/tenant/mo + message-pack consumption (~$0.01/message)
• ServiceNow Now Assist: bundled in Pro Plus tier — ~30% uplift over Pro, which on a per-employee basis maps to roughly $80-200/employee/yr, or ~$7-17/user/mo equivalent when normalized
• ServiceNow AI Agent Studio: rolling out with consumption-style pricing on agent executions (token + run metering)

Why ServiceNow CAN'T Match Microsoft On Per-User Price

• Microsoft has ~400M paid M365 seats — Copilot is incremental ARPU on installed base; their *marginal* cost to add a Copilot seat is near-zero on the distribution side
• Copilot inference is subsidized by Microsoft's own Azure capacity — ServiceNow is a *renter* of compute (NVIDIA H100s, partner clouds), not a hyperscaler
• Microsoft sells Copilot through the existing E3/E5 EA — no new procurement cycle, no new vendor onboarding, no new SOC2 review
• IT-buyer scenarios where Copilot wins on price: knowledge worker productivity, email/Teams summarization, SharePoint search, generic doc generation — anywhere the *system of engagement* matters more than the *system of record*
• ServiceNow per-employee pricing (vs. per-named-user) means racing Copilot to $30/user actually *raises* ServiceNow's effective bill at large enterprises (10k employees × $30 = $3.6M/yr, vs. current Pro Plus uplift math of ~$1-2M)
• A standalone Now Assist SKU would also cannibalize the Pro Plus uplift that Bill McDermott has explicitly told the Street is the FY26-27 growth lever

The 3 Pricing Moves For 2027

• Move 1 — Keep Now Assist bundled in Pro Plus: never break it out as a per-user SKU. The ~30% uplift over Pro is the right vehicle because it sells to the *workflow buyer* (CIO, head of IT Service Management), not the *seat buyer* (CFO benchmarking against Copilot)
• Move 2 — AI Agent Studio on consumption pricing: per-execution and per-token meter, similar to Copilot Studio's message-pack model but priced on *agent runs* (an agent that opens an incident, gathers context across CMDB + HR + Finance, and resolves it = 1 high-value run worth $0.50-2.00, not $0.01/message)
• Move 3 — Workflow-outcome SKUs: "Now Assist for Customer Service" priced per-resolved-ticket (~$1-3/ticket), "Now Assist for HR" priced per-onboarded-employee (~$50-150/onboarding), "Now Assist for ITSM" priced per-incident-resolved. This is the moat — Microsoft has no equivalent because Copilot doesn't own the workflow record

The 1 Anti-Pattern To Avoid

• Do NOT ship a $30/user/mo Now Assist standalone SKU. This is the single highest-risk pricing move ServiceNow could make in FY27
• It invites apples-to-apples comparison with Copilot 365 — and Copilot wins on bundling math every time (because the customer already pays for M365)
• It cannibalizes the Pro Plus uplift, which is currently doing the heavy lifting on platform ARPU expansion
• Named precedent: Salesforce shipped Einstein 1 as a standalone $50/user/mo SKU in 2024 — attach rates were below 5% by mid-2025, and Salesforce quietly pivoted to Agentforce per-conversation pricing because the standalone SKU was getting CFO-shelved against Copilot
• Microsoft will price-match or undercut any per-user SKU within one quarter using EA discounting they can absorb and ServiceNow cannot

The Outcome-Pricing Pivot

• Per-resolved-ticket pricing: $1-3/ticket for ITSM/CSM, with a floor commitment — aligns ServiceNow margin with customer value, makes Copilot comparison nonsensical ("Copilot doesn't resolve your tickets")
• Per-onboarded-employee pricing: $50-150 per HR onboarding workflow completed end-to-end (laptop provisioned, accounts created, training assigned, manager notified) — this is a 6-12 hour manual process today
• Per-incident-resolved pricing: similar to ticket but for IR/SecOps workflows where the value-per-event is $500-5,000
• Named precedent — Intercom Fin AI: launched at $0.99 per resolution in 2023, hit ~$100M ARR by 2025 specifically because the pricing made AI ROI legible to buyers
• Named precedent — Salesforce Agentforce: $2/conversation pricing announced Sept 2024, explicitly modeled on Fin's per-resolution success after Einstein 1 standalone failed
• Named precedent — Zendesk AI agents: per-automated-resolution pricing launched 2024, similar trajectory — outcome pricing is now table stakes for the workflow-AI category

Sales Talk Tracks vs. Copilot

• Workflow context Microsoft can't match: "Copilot can summarize the email about the outage. Now Assist can read the email, open the P1 incident, page the on-call, pull the CMDB topology, and post the war-room link — all before the rep finishes reading the summary"
• Enterprise governance: Now Assist runs inside the customer's ServiceNow instance with existing RBAC, audit trail, and data-residency — Copilot for Service requires Dataverse + Power Platform governance setup separately
• Bundle math: "You're already paying for Pro. The Pro Plus uplift is ~30% — that's $7-17/user/mo equivalent for Now Assist *plus* AI Agent Studio access. Copilot 365 alone is $30/user, and it doesn't touch your CMDB"
• Named-customer reference patterns: lead with NVIDIA, Adobe, Deloitte Now Assist case studies — all Pro Plus customers running production workflows, not pilot/POC seats
• The CFO close: "Copilot is a productivity tax on every seat. Now Assist is a workflow tax on every *outcome*. One scales with headcount, one scales with value delivered"

Pricing Model Comparison

Pricing Strategy Decision Tree

Related on PULSE

• [How should Datadog price Bits AI against Microsoft Copilot in 2027?](/knowledge/q1724)
• [What is the difference between ChatGPT Enterprise and Microsoft Copilot for business?](/knowledge/q14493)
• [What is Microsoft Copilot for Sales and what does it mean for RevOps in 2027?](/knowledge/q12967)
• [How does Microsoft Sales Copilot compare to Salesforce Einstein in 2027?](/knowledge/q12003)
• [How does ServiceNow price Now Assist without cannibalizing core?](/knowledge/q1631)
• [Why did ServiceNow's stock drop after Now Assist launch?](/knowledge/q1630)

The Bundling Trap and How to Avoid It

Microsoft’s ability to bundle Copilot into existing E3/E5 contracts means they can effectively give away seats for free during renewal negotiations. ServiceNow must resist the temptation to match this with aggressive Now Assist bundling into ITSM/CSM Pro. Instead, ServiceNow should keep Now Assist as an opt-in premium within Pro Plus, priced at roughly 30–40% uplift per seat, but crucially offer a consumption-based safety valve for organizations that want to test AI on a single workflow before committing to per-seat pricing. This hybrid model—base seat + metered overage—prevents the “shelfware” problem that plagues per-user AI add-ons.

Outcome-Based Pricing: The Real Differentiator

The single most effective pricing move for 2027 is shifting from per-user to per-outcome pricing for specific workflows. ServiceNow should launch three outcome SKUs by mid-2026:

• Now Assist for Incident Resolution: priced per closed incident (target $2–$8 per resolution, depending on complexity)
• Now Assist for Employee Onboarding: priced per completed onboarding workflow ($15–$40 per employee)
• Now Assist for CMDB Health: priced per CI record reconciled or corrected ($0.05–$0.25 per CI)

This aligns cost directly with value delivered—something Microsoft cannot easily replicate because Copilot lacks workflow ownership. For customers with low ticket volumes but high seat counts, outcome pricing can be 40–60% cheaper than per-user Copilot, making it a compelling entry point.

The Consumption Layer: AI Agent Studio Metering

Beyond outcomes, ServiceNow should introduce AI Agent Studio as a developer platform with pure consumption pricing. Charge $0.003–$0.008 per AI agent execution (a single turn of conversation or action), with a free tier of 1,000 executions/month per instance. This allows enterprises to build custom AI agents for niche workflows—facilities requests, compliance checks, vendor management—without committing to per-seat costs. The metered model also captures value from high-volume automation (e.g., password resets) that would be unprofitable under per-user pricing. By 2027, this consumption revenue could represent 15–25% of total Now Assist revenue, providing a growth engine independent of seat count.

Sources

• Gartner — market analysis and forecasts for AI copilot pricing in enterprise software
• Forrester Research — total cost of ownership comparisons for AI assistants in ITSM platforms
• IDC — market share and pricing trends for ServiceNow and Microsoft in the AI software market
• ServiceNow official investor relations — pricing strategy disclosures and earnings call transcripts
• Microsoft official pricing page — current and historical pricing tiers for Microsoft Copilot
• Harvard Business Review — case studies and strategic analysis of enterprise AI pricing models

FAQ

What is the main pricing risk for ServiceNow Now Assist against Microsoft Copilot in 2027? The biggest risk is competing directly on per-user-per-month pricing. Microsoft can bundle Copilot into existing M365 subscriptions at near-zero marginal cost, while ServiceNow bears real infrastructure costs per execution. A standalone $30/user Now Assist SKU would invite an unwinnable price comparison.

Should ServiceNow offer a standalone per-user Now Assist license? No. Unbundling Now Assist into a standalone per-user SKU is an anti-pattern — Salesforce’s Einstein 1 standalone experiment already proved this fails. ServiceNow should keep Now Assist bundled within platform tiers and price based on outcomes, not seats.

How can ServiceNow differentiate Now Assist from Microsoft Copilot on value? By focusing on workflow context and outcomes. Copilot summarizes emails or drafts documents; Now Assist resolves incidents, provisions laptops, and closes CMDB tickets. ServiceNow should price on resolved tickets or onboarded employees, not per-user access.

What pricing model should ServiceNow use for AI Agent Studio? Consumption-based pricing — per-execution or per-token — is the right approach for AI Agent Studio. This aligns costs with actual usage and avoids the per-user comparison trap, letting customers pay only for the automation value they consume.

Will bundling Now Assist inside Pro Plus uplift work? Yes, keeping Now Assist bundled within a ~30% Pro Plus uplift over standard Pro pricing is a strong move. It avoids direct price anchoring against Copilot while capturing value from the platform’s deeper workflow integration.

What outcome-based SKUs should ServiceNow introduce? Workflow-specific outcome SKUs like “Now Assist for Customer Service” priced per-resolved-ticket and “Now Assist for HR” priced per-onboarded-employee. This shifts the conversation from seat cost to business results, where ServiceNow’s execution advantage shines.

Bottom Line

Don't fight Microsoft on per-user price — you'll lose. Win on workflow context and outcome pricing, where Copilot has no equivalent. Keep Now Assist inside Pro Plus, layer Agent Studio consumption on top, and lead the category into per-resolved-ticket / per-onboarded-employee SKUs before Microsoft figures out workflow-AI is a different game than productivity-AI. The standalone $30/user Now Assist SKU is the trap — Salesforce already walked into it with Einstein 1. (see also: q1616, q1620, q1631)