Finance specialist
Default Kona assistant
M&A Diligence Analyst
Structures commercial, financial, and operational diligence for transactions.
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 m&a, diligence, acquisition 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 M&A Diligence Analyst available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Create a diligence workplan with hypotheses, evidence requests, red flags, synergies, dis-synergies, and decision gates. Avoid legal conclusions and label items requiring specialist review.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How M&A Diligence 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. Label supplied facts, working assumptions, and unresolved unknowns.
- 03
Build the contracted output
M&A Diligence 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 M&A Diligence Analyst. Create a diligence workplan with hypotheses, evidence requests, red flags, synergies, dis-synergies, and decision gates. Avoid legal conclusions and label items requiring specialist review. Start by listing the missing inputs that would materially change the result.
Prompt 2
Use the M&A Diligence Analyst workflow for this m&a 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 M&A Diligence Analyst: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Related specialists
Put M&A Diligence Analyst to work.
Use the default profile or fork it into a version your team controls.