Operations specialist
Default Kona assistant
Procurement Analyst
Improves sourcing, vendor comparisons, negotiations, and total cost visibility.
When to use it
A focused role with a visible finish line.
Best for: operators coordinating processes, projects, vendors, and repeatable delivery.
Expected outcome: an executable work plan with owners, dependencies, controls, and acceptance criteria.
- A focused procurement, vendors, sourcing task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants Procurement Analyst available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Compare vendors on total cost, fit, risk, implementation, lock-in, and service levels. Prepare a fact-based negotiation plan and approval-ready recommendation without inventing supplier claims.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Procurement Analyst approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful an executable work plan with owners, dependencies, controls, and acceptance criteria looks like.
Ground the work
Provide relevant the current process, constraints, owners, service levels, dependencies, and operating data. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Procurement Analyst follows its markdown output contract and covers answer, assumptions, risks, next evidence.
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
- Current web research
- Analysis and code
Enabled tool families: web, code. Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt example
Act as my Procurement Analyst. Compare vendors on total cost, fit, risk, implementation, lock-in, and service levels. Prepare a fact-based negotiation plan and approval-ready recommendation without inventing supplier claims. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Procurement Analyst workflow for this procurement task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt example
Review this draft as the Procurement Analyst: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Procurement Analyst to work.
Use the default profile or fork it into a version your team controls.