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.
A successful pilot does not establish that another practice can work independently.
Reusing a proven workflow preserves delivery capacity, while fresh discovery protects relevance to a different practice.
Who you’d be doing this for
“Yesterday I asked someone in another practice to run it again. My own team still doesn't know where to start.”
Jeroen Wagner · Consulting Practice Manager · a character in this brief
Leads a receiving practice group whose staff attended the initial workshop but still depend on another group's champion.
What is at stake
Five of six consulting customers still depend on their original champion after introductory workshops. You weigh a repeatable programme against the discovery each receiving practice needs to work independently.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- repeatable education vs practice-specific discovery
- cohort reach vs technical consultation depth
- early expansion signals vs sustained independent use
- workflow reuse vs fresh permission validation
Why Perplexity
Computer workflows combine customer data, permissions, and approvals, so transferring a demonstration is not the same as transferring a working practice.
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)
- At the center of this is our Applied AI / Forward Deployed motion: we work closely with law firms and in-house legal teams to distill their core legal processes and embed them into bespoke solutions built on our platform.
- High agency and low ego, with the ability to run multiple complex customer workstreams in parallel and make progress before the playbook exists
- Customer Success Lead (opens in a new tab)
- Partner with Applied AI and Enablement to build onboarding, workshops, champion programs, and scaled education that help customers reach first value and sustain adoption
- You can show how your team helped customers move from initial onboarding to sustained adoption and measurable business outcomes
- Applied AI Architect, Perplexity Computer (opens in a new tab)
- Identify high-value, repeatable workflows; define the expected business outcomes and usage patterns; and partner with Sales and Customer Success to move customers from technical validation to sustained production use and expansion.
- Provide second-level technical consultation to customer success managers and deliver bounded technical work when customer needs exceed standard Customer Success coverage.
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.
One practice group at a plaintiff firm is live, but leaders can't see if demand preparation is changing across offices.
You must decide how far a repeatable adoption path can go before attorney source review has to prove expansion is safe.
Product managers rebuild approved planning decisions in separate tools once delivery begins.
You must weigh a focused adoption path against the governance standards needed for wider rollout.
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 Computer, written for a different role. They’re separate briefs, not the same scenario.
Connector onboarding takes 10 business days, and repeated review defects delay enterprise workflows.
You must decide where the draft packet ends and the engineers' approval of each schema, fixture and evaluation suite begins.
Scheduled research workflows stop after spending credits, leaving coordinators with incomplete briefings.
You must weigh useful visibility against protected connector details and uncertain agent plans.
Removed access sometimes still reaches workspace records through resumed sessions.
You must weigh rollout timing against proof that every connector fails closed.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn a person's earliest brush with a product into a habit they keep coming back to.
Sixty-two percent of newly activated workspaces do not return for a second production session within 21 days.
You must weigh a scalable configuration-and-enablement path against a simpler setup change that uses the same capacity.
New enterprise accounts are starting tables but not returning to run a second workflow.
You have to weigh a fast activation path against a promise that still feels safe for RevOps.
New desktop users are skipping iOS setup and staying in a single-device inbox habit.
You need to decide how prominently mobile setup belongs before users reach their first inbox.
