Perplexity Teammates Launch for Ongoing Work

Perplexity introduced Teammates in a launch post dated November 4 in its blog index. The company describes persistent agents that coordinate ongoing projects, retain context, monitor changes, and return work for review. These are vendor descriptions, not independently verified performance findings.

Its November 6 changelog confirms availability for Max subscribers on the web. The launch post says iOS will follow. This article analyzes the announcements; it is not a hands-on review.

Test a small recurring report first

For U.S. business teams considering ongoing AI assistance, a useful first experiment is a weekly briefing on changes to three public product documentation pages. That creates a contained task with sources a person can check, without immediately connecting private customer or employee information.

Define the deliverable before starting: a short summary of changes, the relevant links, the date each page was checked, and a separate section for anything uncertain. Ask for a clear distinction between a documented change and an interpretation of what it might mean.

Set a review window. Run a small number of reporting cycles alongside your current process. Keep a copy of each input and output so you can compare later reports with what was actually available at the time.

Make approval boundaries explicit

Specify that the pilot may research and prepare a report, but may not send messages, publish content, make purchases, or edit business records. Grant only the access the experiment needs and review any requested expansion before approving it.

Decide what should interrupt a person. A missing source, conflicting dates, or a request for new access should appear as a question or limitation, rather than being hidden behind a confident summary. These are proposed evaluation rules, not claims about built-in enforcement.

Measure the work you still need to do

Track incorrect claims, missed changes, working source links, and minutes spent reviewing each report. Include time spent correcting instructions and investigating errors. A polished response alone is not enough to establish whether the process is useful.

Expand the assignment only after the small test meets your standards. If it does not, narrow the scope or keep the task manual. Whether an ongoing agent fits a particular team will depend on evidence from that team’s workflow, not the breadth of the launch examples.