Dynamics 365 ROI Calculator: Build a Quantified Business Case for Your ERP Investment

The ERP ROI Calculation Methodology

The Core ROI Formula

ROI is calculated as:

ROI (%) = (Total Benefits – Total Costs) / Total Costs × 100

For ERP projects with multi-year benefit horizons, the formula becomes:

3-Year ROI = (Cumulative Benefits, Years 1–3 – Implementation Costs) / Implementation Costs × 100

And for payback period:

Payback Period (months) = Implementation Costs / Average Monthly Benefit

Three-Year ROI Framework

Most organizations calculate ROI over a 3-year horizon. Here’s the typical cash flow pattern:

• Year 0 (Implementation Year): Costs exceed benefits. Negative cash flow of $500K–$3M (depending on product and scope).
• Year 1 (Stabilization): Partial benefits realization (40–60% of projected). Beginning to break even.
• Year 2 (Optimization): Full or near-full benefits realization. Positive cumulative cash flow.
• Year 3 (Maturity): Sustained benefits plus incremental gains from optimizations and expansions. Solidly ROI-positive.

A typical calculation structure:

Item	Year 0	Year 1	Year 2	Year 3	3-Year Total
Implementation Costs	($800,000)	($100,000)	$0	$0	($900,000)
Annual License & Hosting	($150,000)	($200,000)	($200,000)	($200,000)	($750,000)
Maintenance & Support	($50,000)	($75,000)	($75,000)	($75,000)	($275,000)
Total Costs	($1,000,000)	($375,000)	($275,000)	($275,000)	($1,925,000)
Labor Efficiency Savings	$100,000	$300,000	$400,000	$400,000	$1,200,000
Error Reduction & Rework	$50,000	$200,000	$250,000	$250,000	$750,000
Working Capital Improvement	$0	$150,000	$200,000	$200,000	$550,000
Total Benefits	$150,000	$650,000	$850,000	$850,000	$2,500,000
Net Benefit (Loss)	($850,000)	$275,000	$575,000	$575,000	$575,000
Cumulative	($850,000)	($575,000)	$0	$575,000	$575,000

From this structure:

• Payback Period: Month 25 (Year 2, Month 1)
• 3-Year ROI: ($575,000 / $1,925,000) × 100 = 29.8% (roughly 10% annualized)
• Net Present Value (at 10% discount rate): ~$150,000

Cost Categories: Direct, Indirect, and Opportunity

Implementation Costs (Year 0 and Year 1)

Implementation costs are the largest single cash outflow. Typical structure for a mid-market Dynamics 365 Business Central implementation:

• Consulting Services (Partner): $400K–$800K. Covers discovery, design, configuration, data migration, testing, training, and go-live support. Typically 40–50% of total implementation cost.
• Software (Microsoft Licenses): $100K–$300K (initial year 1 licenses + premium features). Discounted for multi-year commitments.
• Data Migration and Integration: $100K–$300K. Includes legacy system analysis, data extraction, cleansing, transformation, and integration middleware (e.g., Azure Data Factory, third-party iPaaS).
• Infrastructure and Hosting: $50K–$150K. Initial setup, databases, security, backup/disaster recovery. Hosted on Microsoft Azure or a CSP’s cloud.
• Hardware and Devices: $50K–$200K (if needed). Typically minimal for cloud deployments, but may include laptops, tablets, or on-premise infrastructure.
• Third-Party Apps and Integrations: $25K–$150K. AppSource apps (e.g., payroll, inventory management), integration platforms (e.g., RPA, middleware).
• Internal Staff (Opportunity Cost): $100K–$500K. Salaried staff diverted from normal operations for 8–12 months. Often excluded from ROI calculations because staff remain employed, but should be noted as a hidden cost.

Finance & Operations implementations are 2–4x more expensive: $1M–$5M+ due to greater complexity, customization requirements, and integration scope.

Annual Operating Costs (Year 1+)

• Software Licensing: $200K–$500K annually (F&O) or $50K–$150K (Business Central) for user licenses, premium features (e.g., Advanced Planning, Machine Learning). Typically 15–20% of implementation cost annually.
• Cloud Hosting and Infrastructure: $50K–$200K annually. Includes compute, storage, backup, disaster recovery, security. Usually 5–10% of implementation cost annually.
• Maintenance and Support: $75K–$250K annually. Microsoft Premier Support, partner support retainers. Typically 10–15% of implementation cost annually.
• Ongoing Optimization and Configuration: $50K–$150K annually. Post-go-live tuning, performance optimization, new feature adoption.

Opportunity Costs

Opportunity costs are often overlooked but significant:

• Deferred Projects: During ERP implementation, organizations typically defer non-critical projects. This foregone business value should be quantified if material.
• Staff Productivity Loss: Implementation and training reduce employee productivity for 3–6 months after go-live. Quantify as percentage of payroll.
• Market Opportunity Loss: If competitors are faster to market with new products or services due to systems limitations, quantify as lost revenue or market share.

Benefit Categories: Efficiency, Accuracy, Speed, and Acceleration

ERP benefits fall into four categories. Efficiency and accuracy benefits are easiest to quantify; speed and acceleration benefits are harder but often larger.

Efficiency Benefits (Labor Reduction)

Dynamics 365 automates manual, repetitive processes. Quantify as FTE reduction or cost avoidance.

• Accounts Payable/Receivable Automation: 20–40% reduction in AP/AR headcount. Invoice matching, payment processing, reconciliation. Typical benefit: $200K–$400K annually for a mid-market organization (5–10 FTE × $50K salary).
• Order-to-Cash Automation: 15–30% reduction in sales operations headcount through order automation, invoice generation, payment matching. Typical benefit: $150K–$300K annually.
• Procure-to-Pay Automation: 20–40% reduction in procurement and supplier management overhead. Typical benefit: $150K–$350K annually.
• Financial Reporting Automation: 30–50% reduction in month-end close time and manual consolidation. Typical benefit: $100K–$250K annually in staff time.
• Inventory and Warehouse Management: Reduced manual inventory counts, cycle counting, and write-offs. Typical benefit: $75K–$200K annually.
• Total Quantifiable Efficiency Benefit: $400K–$1.2M annually (varies by organization size and current-state inefficiency).

Accuracy Benefits (Error Reduction)

ERP systems reduce human error through automated validation, enforced business rules, and data integrity checks.

• Invoice and Payment Errors: Reduction from 3–5% error rate to <0.5%. Cost avoidance from re-invoicing, payment reversal, reconciliation rework. Typical benefit: $100K–$300K annually (1–2% of AP volume).
• Inventory Accuracy: Improvement from 85–95% accuracy to 98–99%+. Reduces write-offs, obsolescence, and stock-outs. Typical benefit: $100K–$400K annually (varies by inventory value).
• Sales Order Errors: Reduction in order-to-fulfillment errors, returns, and customer complaints. Typical benefit: $50K–$150K annually.
• Compliance and Audit Deficiencies: Reduced audit findings and compliance violations. Quantify as audit fee reduction or compliance penalty avoidance. Typical benefit: $50K–$200K annually.
• Total Quantifiable Accuracy Benefit: $300K–$1.0M annually.

Speed Benefits (Time Compression)

ERP systems reduce cycle times, enabling faster decision-making and cash conversion.

• Month-End Close Cycle: Reduction from 8–12 days to 2–4 days. Enables faster financial close, earlier reporting. Benefit: Improved cash flow visibility and earlier decision-making (difficult to quantify; often valued at $50K–$150K annually).
• Order-to-Fulfillment Cycle: Reduction from 5–10 days to 1–3 days. Improved customer satisfaction and reduced inventory carrying. Benefit: ~$100K–$300K annually (inventory carrying cost reduction).
• Procure-to-Pay Cycle: Reduction from 15–30 days to 5–10 days. Improved supplier relationships and cash flow. Benefit: ~$50K–$150K annually (reduced supplier payment terms and improved supply chain relationships).
• Total Quantifiable Speed Benefit: $200K–$600K annually.

Working Capital and Revenue Acceleration Benefits

These benefits stem from faster cycles, improved visibility, and operational improvements. They are highly dependent on industry and organization size.

• Days Inventory Outstanding (DIO) Reduction: Better inventory visibility, demand planning, and turns. Reduce from 60 days to 45 days (for a $20M inventory). Frees up $5M in cash. Quantified as cash × cost of capital (typically 5–10%). Benefit: $250K–$500K annually (one-time in Year 1 or 2).
• Days Sales Outstanding (DSO) Reduction: Better order management and invoice accuracy. Reduce from 45 days to 30 days (for a $100M annual revenue business). Frees up ~$4M in cash. Benefit: $200K–$400K annually (one-time).
• Days Payable Outstanding (DPO) Increase: Negotiated improvements in supplier payment terms due to improved supply chain relationships. Increase from 30 days to 45 days. Benefit: ~$2.5M in working capital improvement, or $125K–$250K annually.
• Subtotal Working Capital Improvement: $400K–$1.0M in one-time cash release (spread across Year 1–2).

Soft Benefits (Difficult to Quantify)

Many ERP benefits are difficult to quantify but often significant:

• Revenue Acceleration: Faster new product launches, improved order accuracy, and better customer visibility enable revenue growth. Hard to isolate ERP contribution; often assumed at 1–3% incremental revenue growth. For a $100M business, 2% = $2M incremental revenue, or $400K–$600K annually in gross profit.
• Cost Reduction Beyond Direct Automation: Standardized processes, improved compliance, reduced rework. Often estimated at 2–4% of operating expense reduction.
• Improved Decision-Making: Better visibility, real-time reporting, and data quality enable better strategic decisions. Difficult to quantify, often valued subjectively.
• Employee Satisfaction and Retention: Modern systems reduce tedious manual work, improving morale and reducing turnover. Cost avoidance: 1–3% reduction in employee turnover × average replacement cost (~$50K per employee).
• Risk Mitigation: Improved audit trail, segregation of duties, and compliance controls reduce compliance risk. Difficult to quantify but often valued at 1–2% of governance/legal budget.

Conservative organizations include only soft benefits with strong supporting logic. Aggressive organizations include all soft benefits with risk-adjusted percentages. Most organizations include 30–50% of soft benefits in their "published" ROI but disclose the assumption.

Building Your Quantified Business Case

Step 1: Define the Scope and Baseline

Establish your current-state metrics (Year 0):

• Headcount by function (AP, AR, Operations, Finance, etc.)
• Current-state cycle times (order-to-fulfillment, month-end close, procure-to-pay)
• Current inventory levels, DIO, DSO, DPO
• Annual IT costs (legacy system maintenance, support staff)
• Error rates, rework costs, compliance issues
• Revenue and gross profit base (for revenue acceleration benefit)

Step 2: Identify Quantifiable Benefits

For each benefit category, estimate the improvement and convert to annual value:

Example: AP/AR Automation

• Current AP/AR team: 6 FTE at $60K average salary = $360K annual cost
• Projected improvement: 30% efficiency gain (1.8 FTE reduction in Year 2, 2.0 FTE in Year 3)
• Benefit: 1.8 FTE × $60K = $108K (Year 2), $120K (Year 3)

Example: Inventory Accuracy Improvement

• Current inventory: $15M (manufacturing organization)
• Current write-off rate: 1.5% annually = $225K loss
• Projected write-off rate post-ERP: 0.5% = $75K loss
• Benefit: $225K – $75K = $150K annual savings

Step 3: Estimate Implementation and Operating Costs

Obtain partner estimates for:

• Partner services (fixed or time-and-materials estimate)
• Microsoft licenses (Year 0 + ongoing)
• Infrastructure and hosting
• Data migration and integration
• Contingency (typically 10–20% of implementation cost)

Add ongoing costs for Years 1+: licenses, hosting, support, maintenance.

Step 4: Build a Three-Year Projection

Create a cash flow table (as shown in the methodology section above). Key assumptions to document:

• Benefit Realization Timeline: Benefits don’t accrue immediately. Typically 30–40% in Year 1, 70–80% in Year 2, 95–100% in Year 3.
• FTE Disposition: Will headcount reductions be through attrition, redeployment, or layoff? Affects timing and allows for gradual benefit realization.
• One-Time vs. Recurring Benefits: Working capital improvements (DIO, DSO) are typically one-time in Year 1–2. Labor savings are recurring.
• Inflation: Adjust salary and benefit costs for 2–3% annual inflation.

Step 5: Calculate Key Financial Metrics

Payback Period: The number of months until cumulative net benefit turns positive. Example: Month 25 means the ERP pays for itself in just over 2 years. Organizations typically require payback within 24–36 months for capital investments.

3-Year ROI: Total net benefit divided by total implementation cost. Example: 30% ROI = $0.30 returned for every dollar invested over 3 years, or about 10% annualized. Organizations typically expect 20–50% 3-year ROI for ERP investments.

Net Present Value (NPV): Discounted cash flows to today’s dollars. Assumes a discount rate (often organization’s cost of capital, typically 8–12% for mid-market organizations). Example: $150,000 NPV at 10% discount rate means the investment is worth $150K above the cost of capital. This is a more sophisticated measure preferred by CFOs.

Financial Metrics: Payback Period, NPV, and IRR

Payback Period

Definition: The number of months required for cumulative benefits to exceed implementation costs.

Formula: Implementation Costs / Average Monthly Benefit

Example: If implementation costs are $900,000 and average monthly benefit is $35,000, payback = 900,000 / 35,000 = 25.7 months (roughly 2 years 2 months).

Interpretation: Payback period is intuitive for executives. A 24–30 month payback is typical for ERP investments. Anything over 36 months should raise questions about ROI. Anything under 18 months is excellent (or the benefits are underestimated).

Limitation: Payback period ignores benefits after payback and doesn’t account for time value of money. It’s a good first-pass metric but should be combined with NPV or IRR.

Net Present Value (NPV)

Definition: The present value of all future cash flows, discounted at the organization’s cost of capital. A positive NPV means the investment exceeds the required return rate.

Formula: NPV = Σ [CF_t / (1 + r)^t] where CF_t = net cash flow in year t, r = discount rate, t = year

Example: Using the 3-year cash flow table from earlier, with a 10% discount rate:

NPV = [($850,000) / 1.0] + [$275,000 / 1.1] + [$575,000 / 1.21] + [$575,000 / 1.331]
NPV = ($850,000) + $250,000 + $475,000 + $432,000 = $307,000

Interpretation: A positive NPV means the investment is worth more than its cost. A $307,000 NPV means the ERP investment delivers $307K more value than required by the organization’s cost of capital. NPV is the gold standard for capital investment decisions preferred by CFOs and investment committees.

Internal Rate of Return (IRR)

Definition: The discount rate at which NPV equals zero. It represents the annualized return on the investment.

Formula: Solve for r where NPV = 0

Example: The cash flows in the earlier table have an IRR of approximately 18–20% (can be calculated in Excel using the IRR function).

Interpretation: An IRR of 18–20% means the investment returns 18–20% annualized. If the organization’s cost of capital is 10%, an IRR of 18% means the project exceeds the required return. Organizations typically expect 15–30% IRR for ERP investments.

Limitation: IRR is less intuitive than ROI and can produce misleading results if cash flows are unconventional (e.g., positive cash in Year 0, then negative).

Which Metric Should You Use?

Different stakeholders prefer different metrics:

• CEO/Board: Prefer NPV (risk-adjusted, comparable across projects) or IRR (expressed as return percentage).
• CFO: Wants all three (NPV + IRR + Payback Period for decision-making context).
• Business Stakeholders: Prefer simple 3-year ROI or payback period (intuitive, no financial math required).

Recommendation: Present all three metrics in your business case, with the understanding that NPV is the most rigorous and should be the primary decision driver.

Industry Benchmarks and ROI Ranges

Manufacturing

Typical ROI: 3–5x over 3 years (200–400% cumulative ROI)

Payback Period: 18–24 months

Primary Benefit Drivers: Inventory optimization (20–30% DIO reduction), manufacturing planning automation, supply chain visibility, demand forecasting accuracy.

Why Higher ROI? Manufacturing organizations operate with high inventory values and long supply chain cycles, so small improvements in inventory turns and demand forecasting unlock large cash improvements. Additionally, production planning and shop floor integration deliver significant labor savings.

Distribution and Wholesale

Typical ROI: 2.5–4x over 3 years (200–300% cumulative ROI)

Payback Period: 20–28 months

Primary Benefit Drivers: Warehouse automation, order fulfillment efficiency, inventory turns, working capital optimization.

Why High ROI? Similar to manufacturing: high inventory values and fast inventory turns mean small cycle time improvements have large financial impact.

Financial Services and Professional Services

Typical ROI: 1.5–2.5x over 3 years (100–150% cumulative ROI)

Payback Period: 28–36 months

Primary Benefit Drivers: Labor efficiency (elimination of manual timekeeping, billing, reconciliation), month-end close acceleration, project accounting improvements.

Why Lower ROI? Professional services organizations don’t have inventory or significant working capital improvements. Benefits are primarily labor-based and harder to achieve without process standardization.

Retail (Omnichannel)

Typical ROI: 2.0–3.5x over 3 years (150–250% cumulative ROI)

Payback Period: 22–32 months

Primary Benefit Drivers: Omnichannel inventory synchronization, labor scheduling optimization, markdown and promotional automation, working capital improvement.

Why Variable ROI? Retail ROI varies significantly based on omnichannel complexity. Pure e-commerce or pure brick-and-mortar are simpler; omnichannel (web, mobile, physical stores) drives more significant benefits but also greater implementation complexity.

Public Sector

Typical ROI: 0.5–1.5x over 3 years (50–150% cumulative ROI)

Payback Period: 30–48 months

Primary Benefit Drivers: Compliance and audit efficiency, budget tracking, grant accounting, labor cost control.

Why Lower ROI? Public sector organizations prioritize compliance and transparency over profit, so financial benefits are limited. Additionally, budget constraints limit the scope of optimization initiatives that drive private-sector ROI.

Soft Benefits Quantification and Risk Adjustment

Approach 1: Conservative (Include Only Hard Benefits)

Quantify only direct, measurable benefits: headcount reduction, error cost avoidance, working capital improvement. Ignore soft benefits entirely.

Result: Typically 1.5–2.5x 3-year ROI, 28–36 month payback period. Conservative, defensible, but potentially underrepresents total value.

Approach 2: Moderate (Include Validated Soft Benefits)

Include soft benefits with strong supporting logic and benchmarks:

• Month-End Close Acceleration: Valued at "soft dollars" = cost to continue with legacy system (staff overtime, consulting, rework). Example: Reduce close from 12 days to 4 days = save 2 weeks of labor (finance staff overtime). Benefit: ~$50K–$100K annually.
• Revenue Acceleration (Modest): Assume 1% incremental gross profit from improved order accuracy and faster fulfillment (for a $100M business = $1M incremental revenue, 40% gross margin = $400K). Conservative organizations discount this by 50%, valuing at $200K.
• Employee Morale and Retention: Assume 1–2% reduction in turnover (from eliminating manual, tedious work). Cost avoidance: 2 FTE × $50K replacement cost = $100K.

Result: Typically 2.5–3.5x 3-year ROI, 22–28 month payback period. Balanced, supported by benchmarks.

Approach 3: Aggressive (Include All Soft Benefits)

Quantify all potential benefits, including speculative ones:

• Full revenue acceleration: 2–3% incremental gross profit growth attributed to ERP
• Operating cost reduction: 2–4% across all functions
• Improved decision-making: Soft valuation of improved real-time insights
• Risk mitigation: Quantified as governance/legal budget reduction

Result: Typically 4.0–6.0x 3-year ROI, 15–20 month payback period. Optimistic, but requires significant assumptions and risk adjustment.

Risk-Adjusted ROI

All ERP projects carry implementation risk: timeline delays, benefit realization slippage, cost overruns. Risk-adjusted ROI discounts for these factors.

Example Risk Adjustment:

• Baseline ROI: 3.0x (300% 3-year ROI)
• Implementation Risk (10% probability of 6-month delay): Reduces benefits by $200K. Adjusted ROI: 2.8x.
• Benefit Realization Risk (20% probability of 30% lower-than-expected benefits): Reduces benefits by $300K. Adjusted ROI: 2.5x.
• Cost Overrun Risk (15% probability of 20% cost overrun): Increases costs by $200K. Adjusted ROI: 2.3x.
• Risk-Adjusted ROI: 2.3x (23% annually over 3 years)

Risk-adjusted ROI is more realistic and defensible to the board, though typically lower than baseline ROI.

Executive Presentation Framework

The One-Page Executive Summary

Most executives won’t read a 50-page business case. Distill to one page:

Investment Amount	$1.2M (implementation) + $750K (3-year licenses & hosting)
Payback Period	26 months (Q3 Year 2)
3-Year ROI	32% (2.3x return on implementation cost)
Net Benefit (3-Year)	$800K net positive cash flow after all costs
Payback Confidence	High. Based on conservative assumptions and industry benchmarks. 80% of benefits from hard cost savings (labor, errors).
Key Risks	Implementation delay (reduce benefits by 4%), data migration complexity (reduce benefits by 6%), business process adoption (reduce benefits by 8%)
Recommendation	Approve. Requires executive sponsorship, dedicated resources, and phased deployment. Estimated go-live: Q2 Year 1.

The Multi-Slide Presentation

Slide 1: Executive Summary (one-pager above)

Slide 2: Strategic Rationale

• Current state pain points (legacy system obsolescence, manual processes, reporting delays)
• Competitive threats (competitors have faster order fulfillment, better customer data)
• Dynamics 365 capability fit (address top 3 pain points)

Slide 3: Quantified Benefits Summary

Stacked bar chart showing benefit categories (labor, errors, working capital, revenue acceleration) and timing (Year 1, 2, 3).

Slide 4: Cost Summary

Pie chart or table breaking down implementation costs (partner services, software, integration, contingency) and annual operating costs.

Slide 5: Financial Metrics

Display payback period timeline (cumulative cash flow turns positive in Month X), NPV, IRR, and comparison to hurdle rate (cost of capital).

Slide 6: Risk Assessment and Mitigation

Top 5–10 risks, probability, impact, and mitigation strategies. This demonstrates rigor and reduces uncertainty perception.

Slide 7: Implementation Roadmap

High-level timeline: Discovery (Months 1–2), Design (Months 3–4), Build (Months 5–8), Test (Months 9–10), Go-live (Month 11).

Frequently Asked Questions

How do we quantify soft benefits like improved decision-making?

Soft benefits are subjective and context-dependent. The most defensible approach: quantify only soft benefits with clear causal links and benchmarking data. For instance, "improved decision-making from real-time reporting" can be valued as equivalent to the cost of business intelligence consultants or analysts who would otherwise be hired to provide similar insights. Or, value it as a percentage of management time saved from reporting prep (e.g., 10% of CFO + controller time × salary). Conservative organizations exclude soft benefits entirely or discount them by 50–75%.

Should we include one-time working capital improvements in ROI?

Yes, but separately. Working capital improvements (DIO, DSO reduction) are one-time cash releases, not recurring benefits. Include them in Year 1–2 cash flows. A typical $500K one-time working capital improvement can be valued as $25K–$50K annually in carrying cost avoidance (working capital × cost of capital). Or, value the full $500K as a one-time benefit in the year it’s realized.

What if implementation costs exceed our estimate by 20%?

It happens frequently (15–20% of implementations experience 15–30% cost overruns). Mitigate by: (1) building 15–20% contingency into the estimate, (2) including cost overrun risk in your risk-adjusted ROI, (3) committing to a fixed-price or time-and-materials cap with the implementation partner. A 20% cost overrun reduces 3-year ROI by roughly 5–8 percentage points but typically doesn’t eliminate ROI if baseline ROI is 25–35%.

How does benefit timing affect ROI?

Significantly. If benefits realization is delayed (e.g., from Year 1 to Year 2), payback period extends by 6–12 months, and NPV decreases by 5–15% (due to time value of money). The most common delays: (1) data migration taking longer than expected (2–6 months), (2) business adoption slower than planned (3–6 months), (3) custom development extending implementation (2–4 months). Mitigate with realistic timeline assumptions and phased deployment (partial go-live enables partial benefit realization).

Should we compare Dynamics 365 ROI to other vendors (SAP, Oracle)?

Not directly. ROI is highly dependent on organization size, industry, implementation approach, and partner capability—not just software choice. A poorly-scoped Dynamics 365 implementation will have lower ROI than a well-executed Oracle implementation, and vice versa. Dynamics 365 is competitive on ROI for small-to-mid-market organizations (Business Central for <$100M revenue, F&O for $500M+) because of lower license costs and faster time-to-value compared to SAP/Oracle.

What happens if we don’t achieve projected headcount reduction from automation?

A common gap: organizations automate processes but retain headcount (redeploying staff to higher-value work like strategy, customer relationship building, or new products). This reduces quantifiable ROI but doesn’t eliminate it. Redeployed labor can drive incremental revenue growth or new-product development, which may exceed the baseline ROI calculation. In your business case, quantify both scenarios: (1) headcount reduction ROI (conservative), (2) headcount redeployment + revenue growth ROI (optimistic). Communicate to leadership which outcome you expect and why.

How often should we update the ROI calculation during implementation?

Quarterly, at minimum. As the project progresses, you’ll refine: (1) implementation costs (actual vs. estimate), (2) benefit assumptions (based on design decisions), (3) timeline (based on actual progress). Update the business case quarterly and communicate adjustments to the board. If ROI declines below acceptable thresholds, assess whether to: (a) continue with adjusted timelines/costs, (b) reduce scope, or (c) pause/cancel the project.