The setting
builds an AI answer engine that pairs web search with generative AI. The lets developers use its search and agent technology in their own software, to build answer engines based on real-time search.
An onboarding note can describe a proposal without authorizing a promise.
Developers need a concrete next step, while CSMs need to preserve the difference between approved guidance and an account agreement.
Who you’d be doing this for
“I booked two engineers for Thursday, then found out that date was only a suggestion in our last call.”
Manuel Santos · Application Developer · a character in this brief
Coordinates an API evaluation and needs an accurate next step before scheduling colleagues for production readiness work.
What is at stake
CSMs checked multiple records for 18 of 30 onboarding replies about next steps. You decide when AI may draft a next step from Salesforce notes and when the CSM must settle whether a proposal became an agreement.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- concrete next steps vs provisional account plans
- current guidance vs historical agreements
- richer account context vs narrower data access
- flexible drafting vs structured milestone records
Why Perplexity
API customers moving from evaluation to production depend on account-specific readiness guidance, not documentation alone.
Written with these in mind
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)
- Prototype workflows, skills, and connector configurations hands-on in Perplexity Computer and the API Platform to prove value in the customer's own use cases
- 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)
- As Customer Success Lead at Perplexity, you’ll lead the team responsible for helping enterprises adopt Perplexity Computer and our API products, turning adoption into measurable business value.
- Hire, coach, and develop CSMs across customer segments, establishing a regular cadence of 1:1s, account and renewal reviews, and a clear bar for performance and product expertise
- Technical Customer Success Manager, API (opens in a new tab)
- Manage customer communications for product changes, deprecations, and outages, partnering with technical teams to provide accurate updates and clear guidance.
- Use account and product usage data to identify declining adoption, technical risks, and growth opportunities, then work with customers on specific next steps.
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.
Where similar work appears
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.
Enterprise CSMs must reconcile conflicting records in 17 of 40 onboarding questions.
You decide whether AI may infer a remaining step from conflicting notes, or must leave that part of the reply for the CSM.
Enterprise support leaders are waiting on launch answers while account evidence sits across several records.
You must decide whether the AI drafts only from approved guidance or also surfaces tentative working-session details for review.
Enterprise CSMs reopen Salesforce notes and Google Sheets the night before renewal calls to rebuild what each customer was promised.
You have to decide where the drafted brief hands off to the CSM when a recorded warning sign has no clear source behind it.
The same setting, from another role
Each is set around Perplexity’s Perplexity API Platform, written for a different role. They’re separate briefs, not the same scenario.
Connector failures are taking about 90 minutes to diagnose because engineers reconstruct agent traces by hand.
You have to decide how far the AI's failure narrative and replay inputs travel before an engineer must confirm them against the connector events and choose what enters an incident or evaluation.
Deep research calls can produce useful answers before developers discover the cost was outside their budget.
You must weigh a firm spend boundary against the retrieval depth that makes the answer useful.
Two developers received project names from another organization after credential refreshes.
You must weigh a hard credential cutover against disruption to active agent workflows.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make a machine-driven decision dependable and fair at the exact real-world moment a customer is counting on it.
Agents are retrieving older interaction summaries after a customer updates a preference.
You must weigh a ranking correction against retrieval latency and safe rollout coverage.
Fourteen percent of Qwen requests now exceed three seconds after the container build.
You must weigh faster batching against the context available to each answer.
Clinicians are rejecting exercise-progression recommendations because the agent retrieves outdated protocol content.
You must weigh a fast retrieval correction against regression risk across shared deployments.
