Bringing AI in at Perplexity

Decide whether routes only propose or also hold incomplete matters

Published Oct 28, 2026

You’re a forward deployed engineer working with Perplexity’s legal and compliance team. The team is in the room.

The setting

develops an AI answer engine that searches the web and replies with cited sources. is the version for large organizations, including regulated industries, with administrator controls over access and use.

Fast agreement routing depends on context that arrives unevenly across the intake queue.

One path protects rapid movement for Enterprise Pro and Enterprise Max deals, while the other protects counsel from acting on an incomplete record.

Who you’d be doing this for

“My security team has the access plan ready, and procurement keeps asking why the agreement is still waiting.”

Arunee Rattanakorn · IT Administrator · a character in this brief

Manages governed AI access at a regulated enterprise whose rollout depends on completed commercial terms.

What is at stake

Regulated IT administrators wait while agreement requests arrive without key context. You must decide whether the system only proposes routes or also holds incomplete matters for counsel.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • complete intake requirements vs. deal submission speed
  • consistent routing rules vs. varied agreement context
  • security boundaries vs. evidence availability
  • shared taxonomy vs. counsel discretion

Why Perplexity

Enterprise Pro and Enterprise Max agreements carry the data-use and access commitments regulated customers need before deployment.

Written with these in mind

workflow systems builderenterprise AI deployment engineerhuman-in-the-loop product practitioner

Not your kind of problem? 44 more at Perplexity, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Perplexity. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Legal Response Specialist (opens in a new tab)
    • Monitor designated Support and Legal channels, assess urgency, and route requests for human review.
    • Judgment about when to involve Legal or GRC, and care with confidential and privileged information.
  • Senior Commercial Counsel, Enterprise (opens in a new tab)
    • Serve as a trusted legal partner to Enterprise Sales, Partnerships, Deal Desk, and Customer Success, providing fast, practical, business-aligned counsel that accelerates deal velocity, protects the terms that matter, and scales as the Sales organization grows.
    • Represent Perplexity Legal externally on customer negotiation calls with counterparty counsel at sophisticated enterprises.
  • Commercial Counsel/Senior Counsel (opens in a new tab)
    • Advise on AI-specific legal considerations in commercial agreements, including acceptable use, data retention and training restrictions, output liability, and evolving regulatory requirements (e.g., EU AI Act, CCPA/CPRA, GDPR).
    • Serve as a primary legal partner across the business, providing fast, practical, and business-aligned counsel that accelerates deal velocity without compromising on risk Management.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about people starting something and never quite finishing it.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make the background systems nobody sees behave dependably even under heavy, high-volume real-world load.