한국어 English ✓

A Coworker That Moves First Instead of Waiting, with Only a $200 Personal Plan as Its Ticket — Perplexity Teammates, the Always-On Agent Launched as a Research Preview, and the Empty Enterprise Seat

As of Nov 12, 2026 · Checked directly against Perplexity's official announcement, help center, and pricing table, and Salesforce's official announcement and pricing page · Views -

Where AI work changes is not the quality of the answer, but whether it waits or moves first. The familiar pattern is a prompt in, an answer out. Teammates, which Perplexity unveiled in a blog post on November 4, sells the opposite: an always-on agent that plans assigned work itself, watches its connected tools, investigates first when something changes, and brings the result to a human only when it is ready for review. Its ticket structure, though, is unusual. Teammates opened only as a research preview for the $200/month personal Max plan — and it is not included by default even in the top enterprise tier at $325 per seat per month. Set beside Salesforce's expansion of its enterprise AI coworker at a flat $50 per user in the same week, this article separates what the official materials settle from what is still empty.

The short version

Work is delegated as responsibility, not prompts — multi-agent parallel orchestration, an isolated computer and browser per teammate, and Claude Opus 5.5 as the default model (official announcement and help center, checked directly)

The only ticket is personal Max at $200/month, and work then draws on a monthly 10,000-credit balance (100 credits = $1) — $200 is a floor, not a total

Even the top enterprise tier ($325/seat/month) excludes it by default and requires an admin request; no named customers or task success rates appear in the official materials yet

Perplexity Teammates structure summary panel reconstructed from the official announcement
A panel reconstructed from Perplexity's official announcement and help center: work split into tasks and run in parallel, connected tools watched so the agent moves first, and an isolated computer and browser per teammate. Content: Perplexity official announcement, "Teammates are agents for complex, ongoing work," and the official help center (the announcement's structural description, reconstructed here as a panel)

Delegating Responsibility, Not Prompts

The unit of Teammates is not a task but a responsibility. Hand it ongoing work — triaging bug reports, tracking metrics, researching a market — and the teammate breaks it into tasks, checks in along the way, and brings finished work back for review. The core sentence is that it does not wait for a new question: it watches connected tools, starts when something arrives, and follows through, answering review comments after opening a pull request. The operations example — tell a teammate once that a vendor needs two weeks' notice, and later schedules build in that slack — shows the difference from re-explaining everything each session.

The body is Perplexity Computer. A teammate inherits Computer's connectors, files, and code abilities, and adds what ongoing work needs: multiple agents spun up in parallel when a goal is large, scaling further as work grows; a separate desktop computer and browser per teammate, so it can operate websites with no connector and test a site end to end; shared context and files inside a Project while roles stay separate, with teammates messaging each other as new information arrives. Put a teammate in a Slack channel and colleagues can hand it work or ask for status right there.

Models are chosen per teammate, and a new teammate defaults to Claude Opus 5.5; the official guidance is to use a strong model for planning and hard judgment, and a faster, cheaper one for routine work. The isolation rules are written as specifications: credentials are encrypted on entry and never visible to the teammate, browsing sessions and cookies stay inside that teammate, and the user can take over the desktop or redirect a teammate mid-work at any time.

One separation matters here. All of this structure, and the work examples below, come from Perplexity's own announcement, product page, and help center; no confirmed adoption by a named customer outside the company was found in this round's official materials. The product page's apparel-store scenario — four teammate roles that prepare an offer when a regular goes quiet and draft dunning notes when invoices slip 15, 30, and 45 days — is a scenario the company constructed. The changelog's examples, a morning brief of drafts and meeting notes, a weekly digest of competitor pricing and hiring, and support drafts that must ask before any refund, sit in the same place: a concrete list of intended scenes, not evidence of real-world use.

The Price: A $200 Ticket, with Credits Riding on Top

For always-on coworker products alone, this week's price table splits like this.

Product (always-on coworker agent)Price (official pages, checked directly)Status
Perplexity Teammates (personal Max only)$200/month + Computer use inside Max's 10,000 monthly credits (100 credits = $1; task example ranges below)Research preview, web only, not included by default in enterprise plans
Salesforce Agentforce Coworker$50 per user/month, all Coworker search included, 30MB indexing per user/month includedEnterprise; Teams, iOS, and desktop apps GA during November 2026
Perplexity Pro (no Teammates)$20/month, weekly Computer usage included with no monthly credit balanceGenerally available; cannot create Teammates
Perplexity credit ledger panel reconstructed from official help-center figures
A panel reconstructed from the task example ranges in Perplexity's official credits help article. These ranges are examples for Computer tasks in general, not a Teammates rate card. Figures: Perplexity official help center, "How credits work on Perplexity"

Read the shape of the billing before the 4x headline. Salesforce's $50 sells predictability, with "all Coworker search included" attached; Perplexity's $200 is a ticket, and usage then rides on credits. Max's 10,000 monthly credits are $100 worth of work at 100 credits to the dollar, and the help center's typical ranges for Computer tasks make the picture concrete: a multi-step research report at 350–950 credits, a data dashboard at 2,400–9,800, and a full app or multi-day build at 15,000 or more. The arithmetic that follows is mine, applying those official example ranges to the monthly balance — not a company figure. On that arithmetic, one dashboard-grade project can take a large share of the month, one multi-day build can exceed it entirely, and the help center itself notes that parallel agents, large files and codebases, and frequent automations burn credits faster. An agent that watches continuously spends by watching. But the range table covers Computer tasks in general; no Teammates rate card exists, so nobody can yet tabulate what one teammate costs per month.

The spending ceiling is set: a Max account's credit spend cap defaults to $200/month and can be raised to $5,000, and when credits run out, work pauses rather than being cancelled, resuming automatically when credits return. The bill of an "autonomous coworker" is not unbounded — but $200 is the floor, not the total, and that is the accurate reading of this plan. The enterprise paradox sits in the same table: Enterprise Max costs more per seat ($325) and carries more credits (15,000), yet the Teammates preview is not included by default and must be requested from an organization admin. The most expensive enterprise seat is not first in line.

The performance side of the comparison is empty. Neither company attaches task success rates or benchmarks to these products. Salesforce's numbers are about usage — 21x growth in three months, more than 185,000 users, and the Adecco Group expanding to 40 countries — all company-announced figures. Perplexity offers no counterpart numbers and no named customers. So the performance axis that can be settled today is not a score but a scope: Salesforce is widening inside enterprises that already hold its records and permission system, toward Teams, mobile, and desktop; Perplexity can be created by an individual on the web today, but it is a preview whose behavior can change, and its enterprise path is still closed. Which one finishes work better cannot be said until third parties assign the same work to both, side by side.

Read With Care: The Word Preview, and the Empty Enterprise Seat

First, status. "Research preview" arrives in the help center with the sentence that the feature is still in development and its behavior can change. It is web-only, with iOS "soon" and desktop and mobile also written as "soon" on the product page. On Salesforce's side, scheduled tasks and the Daily Digest are pushed to December, so the promise of work that "carries on by itself" is not a finished form at either company. Read either as a product to wire into a whole team's workflow today and both are overstated — Perplexity more so.

Second, the weight of access. A teammate's value comes from watching Slack, GitHub, and Gmail and moving first — which means handing an agent real authority to act in those tools. Isolated computers, encrypted credentials, Project permissions, and desktop takeover are confirmed as official specifications, but the cost of a wrongly sent reply or a wrongly opened pull request from a misunderstood instruction stays with the user. That is why the changelog's own examples bake in conditions like "ask before refunding." Splitting delegated work small and fixing approval points first is this product's actual condition of use.

Third, the blanks in the price. The cap on how many teammates one account can run, a typical credit consumption per teammate, and the official annual price of Max were not settled in this round's official materials. In particular, a missing cap is not a feature — it is missing information. Switching on always-on monitoring without knowing how many parallel agents can spin up, or where their billing stops, leans entirely on the one safety device present: the $200 default spend cap.

The conclusion splits cleanly. Confirmed: a structure that takes work by responsibility and moves first, with multi-agent orchestration, isolation, and per-teammate model choice as written specifications; a ticket of personal Max at $200/month with a 10,000-credit monthly balance; exclusion by default from the top enterprise tier; and, in contrast, Salesforce widening a $50 enterprise coworker in the same week with named customers attached. Not yet confirmed: how reliably teammates finish real work, where a month's bill actually stops, and when enterprise and mobile access open. The test is to start small: hand it one reversible, repeatable job — reply drafts, whose output stays in front of you — for two weeks, and measure the share a human had to fix, the credits spent, and whether anything acted without approval. Only after those numbers exist can a $200-a-month coworker's worth be spoken of.

Sources

Puzz, in one line

Perplexity Teammates has the shape of a coworker that moves first, but its only ticket is a $200 personal plan and the enterprise seat is empty. It is a coworker whose worth can only be spoken of after a small two-week delegation produces its numbers, ribbit.