Salesforce's $50 monthly Coworker license includes searches and an indexing allowance, but work delegated to other agents follows their own billing terms. Its reported user growth does not establish how many customers are paying for new standalone seats.
Salesforce reported more than 185,000 Agentforce Coworker users on November 4, 2026. Its pricing page lists a dedicated Coworker license at $50 per user per month. How much of an employee's subsequent workflow is covered by the included searches?
What the $50 seat includes
The Salesforce Agentforce pricing page includes all Coworker searches, Salesforce security and governance policies, and 30 MB of indexing per user per month.
The indexing allowance is pooled across an organization, and unused monthly capacity does not roll forward. Salesforce's billing guide says dedicated seats are for Enterprise or Unlimited Edition customers, with incompatible combinations where other licenses already include Coworker access. The $50 SKU is separately priced rather than a self-contained purchase for every buyer.
Salesforce's enablement FAQ describes a maximum of 30 LLM calls per user per minute and says the restriction was not technically enforced in the interface at publication. One search can involve multiple model calls.
How delegated work changes the bill
Salesforce lists Agentforce User at $5 per user per month with required Flex Credits, but that license provides different capabilities from Coworker.
Flex Credits cost $500 per 100,000, or $0.005 each. A standard production action consumes 20 credits, giving it a $0.10 list value. An action is a billing unit rather than a successfully completed business task.
The Coworker billing guide says execution delegated to another agent follows that agent's billing terms, even when the initiating Coworker search is included. Salesforce introduced Flex Credits in May 2025, so action billing predates the separately priced Coworker seat.
For illustration, 1,000 eligible Coworker seats cost $50,000 monthly at list price. If each seat also generates 100 separately billable delegated standard actions in a month, execution adds $10,000, making $60,000 before discounts, additional data processing or implementation.
This calculation illustrates the effect of separately billable actions. It does not describe observed activity or show that ordinary Coworker searches incur action charges.
The Salesforce pricing catalog also lists add-ons at $125 per user monthly, industry pricing at $150 and Max from $550.
The chart compares published prices for different entitlements, rather than equivalent costs per finished task. Published prices remain subject to change.
User counts leave paid adoption unclear
Salesforce says Coworker usage grew 21 times over three months, alongside its more than 185,000 user figure. The reported figures leave the number of newly purchased standalone $50 seats unidentified.
Its August 26, 2026 earnings release reported Agentforce annual recurring revenue above $1.5 billion, but expanded the metric to include Slackbot and Headless 360. That aggregate cannot establish Coworker seat revenue or margins.
Customer economics also depend on credit commitments. Salesforce offers upfront purchase, spending commitments and pay as you go billing, while unused purchased credits do not roll into subsequent subscription terms.
Forrester analyst Faram Medhora warned, "Every ungoverned pilot can become next year’s committed floor." His warning concerns enterprise software contracts generally, rather than observed Coworker renewals.
What future disclosures could establish
The most likely near-term outcome is continued coexistence of fixed Coworker seats and separately billed delegated execution, consistent with Salesforce's current billing documentation.
We expect, with moderate confidence, that Salesforce's fiscal 2028 second quarter earnings release and Form 10-Q, covering the quarter ending July 31, 2027, will still lack a separately identifiable realized revenue figure for standalone $50 Coworker seats. An explicitly defined revenue figure for that SKU in either document would falsify this call.