Enterprise Risk Management
Enterprise Risk Management Consulting: Costs and How to Choose a Firm
What ERM consulting costs, what a consultant should do, and how to compare firms. Includes a proposal worksheet and acceptance criteria.
By Eric Kennedy · Originally published Tue Apr 07 2026 · Updated Mon Nov 09 2026 · 9 min read
ERM consulting costs depend on the assignment. At Kennedy Risk Group, published fees run from $4,500 to $6,500 for a program diagnostic to $52,000 to $70,000 for an ERM Foundation Build. These are KRG prices for defined engagements, not market averages. The ERM consulting cost guide explains the fees, scope and costs to include in your budget.
Before you ask an ERM consulting firm for a price, write down what your team needs to be able to do when the engagement ends.
That might be agreeing on the risks that deserve executive attention, giving the board a useful view of exposure, or getting risk owners to follow through between reporting cycles. Those are different assignments. Each calls for different work.
Enterprise risk management consulting helps leadership assess risks to business objectives, evaluate responses, and establish the ownership and reporting needed to manage them. A consultant can bring expertise, facilitation, and capacity. Management still has to make decisions and run the business.
For a CFO or chief audit executive comparing firms, the useful question is specific: What will this team help us do, and what evidence will show that the work is complete?
What does an ERM consultant actually do?
Start by separating the services that can sit under the ERM label.
A program diagnostic reviews the existing approach and identifies what needs attention. It should explain the evidence behind each finding, the consequence of leaving it unresolved, and the recommended sequence of improvements.
An enterprise risk assessment connects leadership's objectives with potential sources of uncertainty. It brings together interviews, existing information, and structured challenge to prioritize risks. The output should show why a risk matters, who owns it, what is already being done, and what remains uncertain.
A program build or refresh establishes the way ERM will operate: roles, assessment criteria, escalation rules, reporting, and recurring reviews. Useful existing practices should carry forward. Ask the consultant to explain what needs replacing and why.
A reporting engagement improves the information reaching executives or the board. The work may include agreeing on the audience's questions, establishing reliable inputs, and building a repeatable executive risk reporting process.
Ongoing support provides capacity to coordinate updates, facilitate challenge, or maintain reporting. The scope should state which tasks remain external and which decisions stay with management.
You may need one of these services. Buying all five before identifying the problem makes the proposal harder to evaluate and the program harder to maintain.
When outside help is worth considering
Look for a specific gap in expertise, capacity, or the ability to get work completed.
- Leadership cannot agree on priorities. Functions describe exposure differently, and the executive team needs a common basis for comparison.
- A major business change has outgrown the current process. An acquisition, new operating model, or expansion requires a fresh view of dependencies and accountability.
- The board's questions remain unanswered. Reporting names risks but cannot explain changes in exposure, management's response, or decisions requiring attention.
- The internal team knows what to do but cannot get it done. A defined project needs temporary capacity or specialist help.
- ERM and internal audit work from disconnected information. Risk discussions, audit findings, and assurance coverage need to inform one another without blurring responsibilities.
An internal team with relevant experience, executive support, and available time may be able to address the issue itself. A targeted review may be enough. Before commissioning a full build, identify the executive sponsor and the person who will coordinate the work internally.
Keep frameworks and responsibilities straight
Ask which guidance the firm proposes to use and how it affects the work.
COSO's ERM framework connects risk with strategy and performance. Its five components cover governance and culture; strategy and objective-setting; performance; review and revision; and information, communication, and reporting.
ISO 31000 provides principles, a framework, and a process for managing risk across organizations of any size or sector. It is guidance, not a certifiable management-system standard. COSO and ISO use different structures. A proposal should explain its chosen approach rather than blend their terminology into a supposedly universal checklist.
Responsibility deserves equal attention. Under The IIA's Three Lines Model, management owns and manages risk. Internal audit provides independent, objective assurance and advice. A CAE's involvement in ERM requires clarity about the role and safeguards where responsibilities overlap.
For an engagement involving internal audit, document who recommends responses, who approves them, who operates the process, and who will later provide assurance. Discuss potential self-review risks before assigning the work.
How to compare ERM consulting firms
Evaluate the proposed delivery team and the assignment together.
A large multidisciplinary firm may offer geographic coverage and specialists across several fields. A boutique may offer direct access to a senior practitioner and a focused delivery model. An industry specialist may bring relevant regulatory or operating knowledge. Check these capabilities in the actual proposal. Firm size alone tells you little about who will attend your working sessions or review your reports.
Ask the delivery lead to walk through a piece of work. A sanitized sample, a permitted prior-employer example, or a clearly identified synthetic example can all help. Confidentiality restrictions are legitimate. A synthetic sample demonstrates how someone thinks and communicates; it does not establish a client track record.
For experience claims, ask what the person actually did. Running an established program, building one, conducting assessments, and advising its leadership are different experiences. Each can be valuable. Match the experience to the assignment.
A proposal comparison worksheet
Use the same questions for every bidder. Record the evidence and the unresolved points beside each answer.
| What to compare | Evidence to request | What to settle before signing |
|---|---|---|
| Understanding of the assignment | A concise description of your problem, intended users, and decisions | The specific outcome and what is outside scope |
| Delivery team | Names, relevant roles, and expected involvement | Who leads interviews, facilitates challenge, drafts outputs, and reviews quality |
| Assessment method | A worked sample showing criteria, evidence, assumptions, and uncertainty | How disagreements and weak data will be handled |
| Deliverables | Sanitized or clearly labeled synthetic samples | Format, review rounds, acceptance criteria, and rights to use and edit the files |
| Internal workload | An interview plan, data request, and approval calendar | Required staff time, executive availability, and dependencies |
| Commercial terms | Scope, assumptions, exclusions, expenses, and change process | What triggers additional fees and who can approve them |
| Handover or ongoing support | A runbook, training approach, and responsibility map | Who runs the next cycle and what continued support includes |
Treat an unanswered question as a follow-up item. A polished presentation should not outweigh a missing delivery commitment.
Two questions are particularly revealing: “What would you leave out of our scope?” and “What could our team realistically maintain after you leave?” Listen for an answer tied to your staff, information, and decisions.
Turn a broad scope into something you can accept
ILLUSTRATIVE SCENARIO. The following is a constructed proposal example, not a KRG client engagement or a service commitment.
A CFO wants a clearer enterprise risk discussion at the next board meeting. Departmental assessments already exist, but they use inconsistent criteria and ownership is unclear.
Weak scope: “Develop a comprehensive ERM framework, conduct stakeholder interviews, and deliver a board-ready risk assessment.”
That wording leaves the buyer to discover what “comprehensive” and “board-ready” mean after work begins.
Better scope: “Review existing assessments and interview eight agreed leaders. Facilitate one executive workshop to calibrate assessment criteria and confirm priority risks. Deliver an editable risk register with assessment rationale, named management owners, current responses, and unresolved information gaps. Prepare a board discussion pack covering changes in exposure, response status, and decisions requested. Include two review rounds and one rehearsal with the internal coordinator. Management approves owners and responses. Detailed control testing, software implementation, and regulatory opinions are excluded.”
The better scope is still incomplete until the parties agree on dates, dependencies, fees, and acceptance. It gives them something concrete to discuss.
Define “done” before the kickoff
For a program build or substantial refresh, agree on acceptance criteria alongside the deliverables. Adjust these to the assignment:
- Priority risks can be explained. The register connects risks to objectives and records assessment criteria, supporting information, assumptions, and significant disagreements.
- Ownership is accepted. Named management owners understand their responsibilities, actions, and escalation routes. Open ownership disputes are visible to the sponsor.
- Reporting supports a discussion. Readers can see exposure, changes, response status, and the decisions or attention requested.
- The process has been tested. The internal coordinator has run a supported update cycle, with any remaining gaps documented.
- The team has the materials. Editable files, definitions, source information, instructions, and future meeting dates are available to the people responsible.
A short diagnostic will have narrower acceptance criteria. Do not ask it to prove that a redesigned program works when implementation was never included.
Measure progress against the agreed baseline. Useful evidence includes owners submitting updates on time, escalations reaching the right person, and documented decisions drawing on risk information. Avoid attributing an avoided loss to the project when you cannot establish what would otherwise have happened.
Compare fees and timelines on the same basis
A fee comparison needs comparable scope. Normalize the number of entities, interviews, workshops, deliverables, review rounds, and supported reporting cycles. Separate advisory fees from software, travel, implementation, and ongoing support.
Ask for a schedule showing both consultant work and your team's approval windows. A proposed finish date depends on access to information and decision-makers, including the resolution of ownership disputes.
The ERM consulting cost guide covers pricing and scope drivers in more detail. If the larger question is who should run the program, start with in-house versus outsourced risk management.
Start with the problem you need to solve
Before requesting proposals, put five things on one page: the problem, the intended audience, the decision or capability you need, your internal capacity, and any hard deadline.
If those are difficult to pin down, review KRG's ERM Program Diagnostic. It is a starting point for examining the current program and deciding which gaps deserve attention before defining a larger engagement.
Explore the ERM Program Diagnostic
Frequently Asked Questions
What should an ERM consultant deliver?
Deliverables depend on the scope. An assessment should explain priority risks and its supporting rationale. A program build should also establish ownership, reporting, review routines, and handover materials. Agree on how each output will be used and accepted before work starts.
Do we need a full ERM program build?
Not necessarily. Review what already works. If the main issue is reporting, inconsistent assessments, or limited capacity, a focused engagement may address it. A build is more appropriate when several connected elements of the operating approach need to be established or redesigned.
Can internal audit lead the ERM engagement?
A CAE may help coordinate, facilitate, or advise on the work. Define the role explicitly. The executive sponsor in management and the relevant risk owners retain risk decisions, subject to board oversight. Any additional CAE responsibilities require appropriate safeguards for internal audit's independence and objectivity, including future assurance work.
Should we choose a boutique or a large firm?
Choose against the assignment: relevant experience, named delivery staff, specialist coverage, capacity, and commercial terms. Ask both how they handle continuity and access to expertise. Neither firm size nor a senior title guarantees the right delivery team.
How do we evaluate a firm that cannot share client work?
Respect confidentiality. Request sanitized materials where permitted or a clearly labeled synthetic walkthrough. Assess the quality of the reasoning and output, then examine the team's claimed experience separately. A sample and evidence of past delivery answer different questions.
How much does enterprise risk management consulting cost?
The scope determines the fee. Kennedy Risk Group publishes $4,500 to $6,500 for a program diagnostic and $52,000 to $70,000 for an ERM Foundation Build, with focused assessment and reporting engagements between those figures. These are KRG prices, not market averages. Compare deliverables, internal workload, exclusions and support before comparing proposals.