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 briefing skill's general narrative clashes with the manager's required structure.
A shared configuration removes repeated input work, while guided inputs preserve flexibility across projects.
Who you’d be doing this for
“My manager liked the content, then I spent the last ten minutes moving it into our three sections.”
Thierry Bos · Consulting Associate · a character in this brief
Prepares the recurring internal project briefing and participated in the first onboarding session.
What is at stake
Eight of twelve consulting analysts rebuild their generated briefings despite acceptable content. You must weigh a tailored skill against teaching flexible inputs in the only working session available.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer-specific convenience vs reusable education
- shared defaults vs flexibility across projects
- visible completion vs attendance-based health
- configuration upkeep vs repeated user effort
Why Perplexity
Computer adoption depends on briefings fitting the customer's actual review process, not merely generating acceptable content.
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)
- This is a commercial and sales engineering role: you will own strategic customer engagements end to end—leading discovery, defining what to build, demonstrating frontier capabilities against real legal workflows, and driving deployments from first conversation through production and expansion.
- Drive deployment and rollout across practice groups and legal departments, with real revenue responsibility alongside Sales
- 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
- 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)
- Establish scope, customer commitments, milestones, success criteria, working cadence, and exit criteria, then lead the work through closure.
- 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 people starting something and never quite finishing it.
Three finance departments still run reports manually after completing dbt training.
You weigh customer ownership through a workshop against specialist configuration in the only available session.
Only six of eighteen designer-developer pairs finished an asset handoff independently.
You must weigh keeping the intended workflow against giving everyone enough time to practice a narrower one.
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.
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.