Complex day at Perplexity

Commit to research outcomes when reviewers dispute the time saved

Published Oct 30, 2026

You’re the customer success / solutions lead. Your team is in the room.

The setting

develops an AI answer engine that searches the web and gives answers with sources. is its AI agent that uses tools and applications to complete multi-step tasks for professionals and enterprises.

The renewal promises research capacity that the pilot's time records do not yet establish.

The customer wants a firm productivity commitment, while delivery leadership must protect capacity already promised to other customers.

Who you’d be doing this for

“My director took two hours out of next week's schedule, but yesterday I spent those hours checking the draft.”

Ishaan Kulkarni · Investment Research Associate · a character in this brief

Participated in the pilot and would coach colleagues during the expansion.

What is at stake

An investment firm's $480,000 renewal rests on savings that reviewers dispute. You must weigh a defensible outcome commitment against eight weeks of delivery capacity that signature locks in.

Why it isn’t already fixed

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

  • renewal certainty vs deliverable commitments
  • broad analyst adoption vs specialist-supported outputs
  • reported savings vs retained review work
  • customer capacity promises vs existing delivery obligations

Why Perplexity

Computer's research workflows must translate autonomous execution into accepted analyst work, not merely completed runs.

Written with these in mind

Technical customer success leadersConsultative solutions leadsEnterprise adoption specialists

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.

  • AI Strategist, Legal (opens in a new tab)
    • Build and deliver compelling, workflow-specific demonstrations: legal research, contract review and analysis, due diligence, drafting, deposition and discovery summarization, regulatory monitoring
    • Assess whether we have the right research, contract, docket, and document-management integrations to serve each legal segment—and drive the roadmap where we do not
  • Customer Success Lead (opens in a new tab)
    • Own gross and net revenue retention for the customer base, including renewal forecasting, risk management, and expansion targets shared with Sales
    • Engage executive sponsors at our largest accounts and step in personally on strategic adoption efforts, high-stakes renewals, and escalations while building the team’s ability to own day-to-day execution
  • Applied AI Architect, Perplexity Computer (opens in a new tab)
    • This role is ideal for technical, consultative professionals who have led complex software implementations and can move comfortably between customer discovery, solution design, hands-on delivery, and executive communication.
    • Convert repeated customer needs into reusable workflows, implementation patterns, demos, guidance, and product feedback.

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 betting growth on an outside partner or launch.

The same setting, from another role

Each is set around Perplexity’s Perplexity Computer, written for a different role. They’re separate briefs, not the same scenario.