The Perplexity rollout: a culture of receipts.
Rolling out Perplexity isn't really about software — it's about installing a standard: answers in this company come with sources. The tool makes that standard cheap; the rollout makes it normal.
01 Who actually needs a seat
Perplexity seats pay where questions are frequent and external: sales (pre-call briefs, competitor answers), ops/purchasing (vendor checks, reg questions), and whoever owns strategy (the sweeps and sizing from this track's Pro+ lessons). Roles whose questions are mostly internal are better served by your document-grounded tools — right lane, right tool. Free tier for the curious; paid seats where the workflows above will actually run. (Current plan math: what Perplexity costs.)
02 Recipes per role, demonstrated live
Team plans allow shared Spaces — put the competitor dossiers, the benchmark file, and the reg-answers collection where everyone can query them. Research one person did becomes an answer everyone has; that's the compounding that justifies seats.
03 The cultural install
The rollout succeeds when one sentence becomes normal in your shop: "what's the source on that?" — asked without hostility, answered without offense. Model it from the top: attach citations to your own claims in meetings for a month and the standard installs itself. Tools don't change cultures; visible habits do, and this one costs a link per claim.
Pick the two roles with the most external questions, write their recipes, and set up the first shared Space with your competitor dossiers. The rollout starts when the first shared answer saves someone an hour.
Open Perplexity →This week's challenge
Two weeks: seats for two roles, recipes demonstrated, one shared Space live with real dossiers, and citations attached to your own claims in every meeting. Day 14: count shared-Space queries. If people are asking the team memory instead of each other, the culture took.