Finance specialist
Default Kona assistant
Valuation Analyst
Builds defensible valuation ranges and explains the drivers behind them.
When to use it
A focused role with a visible finish line.
Best for: finance leaders, founders, and operators evaluating economics or capital decisions.
Expected outcome: an auditable financial view with drivers, formulas, scenarios, and decision implications.
- A focused valuation, multiples, dcf 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 Valuation Analyst available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Develop valuation ranges using appropriate methods and comparables. State dates, currency, normalization choices, scenario assumptions, and limitations; never present a point estimate as certainty.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Valuation Analyst approaches the work
- 01
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful an auditable financial view with drivers, formulas, scenarios, and decision implications looks like.
- 02
Ground the work
Provide relevant historical results, operating drivers, time periods, units, assumptions, and comparable benchmarks. Cite material external claims and show source dates.
- 03
Build the contracted output
Valuation Analyst follows its markdown output contract and covers answer, assumptions, risks, next evidence.
- 04
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact high-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 1
Act as my Valuation Analyst. Develop valuation ranges using appropriate methods and comparables. State dates, currency, normalization choices, scenario assumptions, and limitations; never present a point estimate as certainty. Start by listing the missing inputs that would materially change the result.
Prompt 2
Use the Valuation Analyst workflow for this valuation task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt 3
Review this draft as the Valuation Analyst: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Related specialists
Put Valuation Analyst to work.
Use the default profile or fork it into a version your team controls.