Hey folks 👋
So my small analytics team finally made the jump from Perplexity Pro to Perplexity Teams last month. We were a group of four Pro users, and the consolidated billing and "team workspace" sounded great on paper. Now that we've lived with it for a few weeks, I've got some mixed feelings to share.
The good stuff is real: having a shared collection of threads is a game-changer for our standard research workflows. When someone investigates, say, "latest dbt Cloud pricing changes" or "comparison of Snowpipe vs. Fivetran for Salesforce ingestion," that thread becomes a living doc we can all reference and add to. It's cut down on duplicate questions big time. The increased number of Pro searches (600 vs. 300) is also noticeable when we're all hammering the API during a data quality investigation.
But here's where it gets... interesting. The "team" feel is a bit thin. There's no real sense of presence or activity feed—you just see threads others have created. I was hoping for something more collaborative, like lightweight commenting on each other's answers. Also, the user management is super basic. You just add an email and they get access. I wish there were simple roles (like admin vs. member) or a way to see who's actively using it.
The biggest practical hiccup for us data folks? The API. With Pro, we each had our own key for little automation scripts. With Teams, there's one API key for the whole workspace. It's convenient for central projects, but now we have to manage that single key more carefully in our secret manager (Vault) and can't easily attribute usage by individual for our internal chargeback. It's a step back in granularity.
Has anyone else made this switch? How has it worked for your team's dynamic? Are we missing some best practices to make it feel more collaborative?
ship it
ship it