Buy Salesforce Agentforce or Microsoft Copilot Studio when the task is generic and your data already lives in that platform: list prices start around $2 per Agentforce conversation and $200 for 25,000 Copilot Studio credits a month. Build a custom AI agent when the workflow is your advantage, touches regulated data, or runs at a volume where per-action fees outgrow a one-time build.
Updated 13 November 2026: we re-checked Agentforce and Copilot Studio pricing on salesforce.com and microsoft.com and added a worked cost comparison. Since Microsoft shipped Agent Framework 1.0 in April 2026 and every major SaaS vendor now bundles an "agent builder", the question has flipped. It is no longer "should we use AI agents?" but "should we buy one off the shelf or build our own?". Below is how a senior engineering team actually makes that call, with the cost math and the breaking points that vendor demos usually skip.
Looking for AI coding agents that write your software, such as Cursor, Claude Code or the GitHub Copilot cloud agent? That is a different decision, covered in our AI dev agent platforms comparison. This post is about agents you deploy inside your business.
Buying means you rent an agent that runs inside a platform you don't own: Salesforce Agentforce for CRM workflows, Microsoft Copilot Studio for Microsoft 365 and Teams, or a range of vertical agents (support, sales, coding). You configure prompts, connect the permitted data sources, and go live in a few days.
The trade-off you accept: the agent can only reason over the data the platform exposes, its actions are limited by the vendor's connectors, and you pay per seat, per conversation or per action. When the platform already holds your system of record, that is a reasonable trade. When important data or logic lives outside it, the gaps show up fast.
Building means you own the orchestration: the model choice, the retrieval layer, the tool/function calls, memory and, most importantly, authorization and audit logging for every action. In 2026 you rarely build from zero; you assemble on frameworks like Microsoft Agent Framework, Claude Agent SDK, CrewAI or LangGraph (compared in our AI agent frameworks guide). The engineering value isn't in the prompt. It's in the integrations, the safety guardrails, and the evaluation harness around it.
That is also where the real cost sits. On real projects, writing the "agent" is only 25–35% of the work. Integrating with your systems, plus QA and safety testing, makes up the remaining 40–60%. Any comparison that ignores this is comparing a subscription fee with a proof of concept, not with a production system.
Build when the workflow is a competitive advantage, touches sensitive data (HIPAA, PCI), needs integrations the platform can't reach, or runs at a volume where per-conversation fees exceed the cost of owning it. Buy when the workflow is generic, low-risk, and lives in a platform you already pay for. Use the table below as a first-pass filter.
| Criterion | Leans "Buy" | Leans "Build" |
|---|---|---|
| Workflow | Generic, horizontal | Core / differentiating |
| Where the data lives | Already in the vendor's cloud | Spread across your own systems |
| Compliance | Standard, little PHI/PII | HIPAA / PCI / proprietary data |
| Time to value | Days, the top priority | Weeks, acceptable in exchange for control |
| Volume | Low or unpredictable | High and steady (thousands of conversations a month) |
| Ownership & lock-in | Vendor dependency is acceptable | The agent itself is IP you must own |
| Cost shape | Per seat/conversation/action, forever | High upfront investment, low marginal cost |
On Salesforce's Agentforce pricing page (checked 13 November 2026), customer-facing conversations cost $2 each, and Flex Credits cost $500 per 100,000 credits, with a standard agent action using 20 credits, which works out to $0.10 per action. Per-user add-ons for Sales, Service, Field Service and Operations cost $125 per user per month.
| Agentforce option (USD, list) | Price | Notes |
|---|---|---|
| Conversations | $2 per conversation | Customer-facing agents |
| Flex Credits | $500 per 100,000 credits | Standard action 20 credits ($0.10); Agentforce Voice action 30 credits ($0.15) |
| Agentforce User License | $5 per user per month | Requires Flex Credits; limited CRM objects |
| Agentforce add-ons (Sales, Service, Field Service, Operations) | $125 per user per month | Unmetered employee usage |
| Agentforce Industries add-ons | $150 per user per month | Unmetered employee usage |
| Max Edition | From $550 per user per month | Includes the add-on and 2.75M Flex Credits per org per year |
| Salesforce Foundations | $0 | Agentforce Builder and Prompt Builder included |
Salesforce offers three buying models: pre-purchase, pre-commit (billed monthly in arrears with a true-up) and pay-as-you-go. Unused Flex Credits do not roll over, and Salesforce's own cost examples exclude Data 360 credits and other consumption services. The page says prices are for information only and subject to change, so confirm them in your quote.
Copilot Studio costs $200 per month for a tenant-wide pack of 25,000 Copilot Credits (billed annually), or $0.01 per credit pay-as-you-go. A generative answer uses 2 credits, an agent action 5, and tenant graph grounding 10. Employee-facing use by people with a Microsoft 365 Copilot licence ($30 per user per month) is included, within fair-use limits.
| Copilot Studio item | Rate | At $0.01 per credit |
|---|---|---|
| Classic (authored) answer | 1 credit | $0.01 |
| Generative answer | 2 credits | $0.02 |
| Agent action (trigger, reasoning step, topic transition) | 5 credits | $0.05 |
| Tenant graph grounding | 10 credits | $0.10 |
| Reasoning model orchestration (premium) | 10 credits per 1,000 tokens | $0.10 per 1,000 tokens |
| Agent flow actions | 13 credits per 100 actions | $0.13 per 100 |
Sources: Microsoft's Copilot Studio billing rates (updated 3 November 2026) and Copilot Studio licensing guidance. A Copilot Credit Pre-Purchase Plan gives 5–20% off for one-year upfront commitments, and unused pack credits don't roll over. Customer-facing agents (your website, your customers) are not covered by employee Microsoft 365 Copilot licences, so they always consume credits.
Platform agents are billed per seat, per conversation or per action: cheap at first, but they compound with usage and never stop. A custom production agent is typically a five- to six-figure (USD) investment, followed by low marginal running costs (model tokens and hosting). The honest comparison is 3-year total cost of ownership, not the first month.
Our arithmetic on the list prices above, before discounts, for a customer-facing support agent:
The pattern: platform pricing is efficient at low volume and for employees already licensed, and becomes the largest line item at high, steady customer-facing volume. That is where a custom build, whose running cost is mostly model tokens, usually wins over three years.
See the line-by-line breakdown in our post on how much it costs to build an AI agent.
Comparing specific off-the-shelf agents? Our OpenAI Dots vs Meta Muse vs custom AI agent comparison prices each option at 5 and 50 users and at 100K tasks. If the agent sits inside a larger product, see AI app development cost in 2026 for build and token costs by architecture.
The biggest hidden costs are usage meters that grow with conversation length and model choice, data platform charges outside the agent price, and the integration work for systems the vendor's connectors don't reach. Licences are the visible part; these are what blow up the budget.
Yes, and it is often the right sequence: use a platform agent to prove the workflow and measure real volume, then build once the numbers justify it. Plan the exit from day one, because prompts, flows and conversation logs built in a vendor's studio do not port to another stack automatically.
What makes the move cheap later:
They break exactly in the 40–60% that platforms and demos skip: reliable integrations, error handling, authorization for every action, and evaluation. A no-code agent that answers questions is easy; an agent that takes actions on customer accounts, correctly, every time, is a systems-engineering problem. That gap is why so many pilots never reach production; see why AI agent projects fail.
Before an agent gets write access to customer accounts, check it against our AI agent security checklist (24 controls). If it has to expose tools to Claude, ChatGPT or other assistants, MCP server development covers the cost, architecture and security of doing that properly.
If the agent touches PHI or cardholder data, the "buy" options narrow sharply: you need a BAA, minimum-necessary limits on what the agent can retrieve, encryption, and logs for every access decision, and not every platform or plan will sign or support that. Regulated workflows are usually where building wins, because the controls have to live in code you own. We cover this in depth in HIPAA-compliant AI agents.
For the evaluation side, meaning how to test an agent so the results hold up in an audit, see LLM testing for regulated industries.
If you've scrutinized the workflow and the answer is "build", that's what we do: senior engineers who own the integrations, compliance and evaluation, not just the prompt, at a fixed price per phase (from $10K) with you owning the code, as described in fixed-price AI agent development. See how we approach AI agent development, or tell us about your workflow and we'll give you a straight assessment of whether to build or buy.