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.
Growing API use is not yet a case for another workflow.
Technical champions want credit for useful integrations, while sponsors want evidence that separates their contribution from other AI providers.
Who you’d be doing this for
“Our sponsor asked which part saved the analysts time, and all I had was a chart of API calls.”
Nnamdi Salami · Application Development Lead · a character in this brief
Runs a research application using multiple AI providers and needs sponsor approval to extend it to another business workflow.
What is at stake
Eight of twelve API champions cannot explain their integration's contribution to sponsors despite growing use. You must weigh a repeatable value programme against the customer-specific evidence that earns another investment.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- repeatable service vs customer-specific proof
- consumption growth vs attributable business value
- persuasive ROI vs defensible assumptions
- adjacent possibilities vs champion capacity
Why Perplexity
Search and Agent API customers combine providers, so consumption alone does not explain which integration deserves broader adoption.
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)
- 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)
- Help customers connect adoption and consumption to business outcomes, understand usage and cost trade-offs, and build a clear case for renewal and expansion
- Partner with Applied AI and Enablement to build onboarding, workshops, champion programs, and scaled education that help customers reach first value and sustain adoption
- Technical Customer Success Manager, API (opens in a new tab)
- Partner with Sales and account owners on renewals and expansion, using adoption, consumption, and business outcomes to demonstrate value and surface risks early.
- Investigate technical questions using API documentation, sample requests, and usage data.
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 figuring out which problem is actually worth solving.
Legal Operations Managers have usage data but no executive-ready evidence of AI efficiency.
You must weigh a credible value narrative against a programme customers can complete during activation.
Pilot customers have production workloads, but their renewal conversations lack agreed evidence of business value.
You have to weigh a repeatable programme against the different outcomes each customer expects.
Four of six apps have live wallets but no agreed measure of business value.
You must weigh a shared programme customers can sustain against the different outcomes each sponsor needs to justify investment.
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 turn a tangle of ecosystem partners into a buying decision a customer can confidently say yes to.
Buyers want AI-agent workflows, but partners cannot yet offer a repeatable path from messy knowledge to a build-ready project.
You have to weigh partner reach against the qualification standard sellers need.
Buyers are rebuilding approved product decisions after every handoff, and bundled suites are becoming the default alternative.
You must weigh a focused partner offer against the proof, approvals, and buyer commitments needed to make it repeatable.
Qualified enterprise opportunities are stalling when buyers cannot connect Marketplace purchasing to rollout support.
You must weigh a fast, focused partner motion against the coverage needed across complex enterprise accounts.
