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.
Tonight's renewal turns a disputed research evaluation into a contractual promise.
The customer wants a firm acceptance date, while the available specialist review covers only a fraction of the work.
Who you’d be doing this for
“I opened the citations before our morning briefing and found six answers we'd have to rewrite. Procurement keeps asking whether we're ready.”
Dalal Celik · Financial Research Lead · a character in this brief
Her analysts will depend on the customer's Agent API application after production acceptance.
What is at stake
A financial research customer will renew $600,000 tonight only with a firm acceptance date, but its reviewers dispute readiness. You must weigh a binding success commitment against switching the customer to a supported workflow with a different path to value.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- renewal certainty vs contractual exposure
- successful requests vs accepted research
- embedded application value vs a guided alternative
- broad acceptance promises vs limited specialist evidence
Why Perplexity
Agent API consumption and successful requests do not establish whether financial analysts will accept the cited research.
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)
- Drive deployment and rollout across practice groups and legal departments, with real revenue responsibility alongside Sales
- Build and deliver compelling, workflow-specific demonstrations: legal research, contract review and analysis, due diligence, drafting, deposition and discovery summarization, regulatory monitoring
- Customer Success Lead (opens in a new tab)
- Build the playbooks the team runs on, including Sales-to-CS handoffs, onboarding, customer success plans, health scoring, executive business reviews, and escalations
- Own gross and net revenue retention for the customer base, including renewal forecasting, risk management, and expansion targets shared with Sales
- Technical Customer Success Manager, API (opens in a new tab)
- Lead customer-facing programs such as endpoint migrations, product rollouts, and enablement.
- 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 betting growth on an outside partner or launch.
An enterprise customer may remove two business units from its annual renewal today.
You must weigh preserving ten reporting workloads against committing to savings that a full monthly close has not tested.
A 4,000-seat business program may not renew because executives dispute what learner progress proves.
You have to weigh a fast commercial save against claims the evidence cannot support.
A payment outage left engineers without usable transaction evidence, and renewal closes in 10 days.
You must weigh a credible recovery plan against procurement’s demand for lower telemetry exposure.
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.
