ERP Economics: 6 Conversions, $12M Capital, 18-Month ROI

The ERP Selection Problem: License Cost vs Total Cost

Most portfolio companies select ERP platforms based on license cost. This is a $5M+ mistake.

Over 15 years, I led 6 ERP conversions deploying $12M in capital. The pattern is consistent: license cost represents 25–30% of total cost of ownership. Migration, customization, training, and ongoing support represent 70–75%.

Understanding TCO enables better vendor negotiation, prevents scope creep, and ensures ROI models reflect reality. Here's how the math works.

Total Cost of Ownership: 5-Year Analysis

Typical $4M ERP Implementation (Mid-Market Company)

• User licenses, database, infrastructure, annual maintenance
• Consulting, customization, data migration, integration build
• User adoption, process redesign, documentation, support
• Project management, testing, business process owners
• Productivity loss, scope creep, post-go-live stabilization

Critical insight: Vendors quote $1.2M in licensing. Actual spend is $4M. Portfolio companies that budget for license cost alone face 200–300% budget overruns.

Platform Comparison: SAP vs Dynamics vs NetSuite

I've deployed all three major platforms plus industry-specific ERPs. Here's the cost/benefit reality:

SAP (S/4HANA)

Best for: $500M+ revenue, complex multi-entity, global operations

TCO: $6M–$12M (mid-market), $20M+ (enterprise)

Timeline: 18–24 months to full deployment

Verdict: Overkill for $100M–$300M companies. Licensing saves eliminated by consulting costs. Only justified at scale.

Microsoft Dynamics 365 F&O

Best for: $100M–$500M revenue, Microsoft ecosystem, manufacturing/distribution

TCO: $3M–$6M (mid-market), extensible to $10M+ at scale

Timeline: 12–18 months to full deployment

Verdict: Sweet spot for PE portfolio companies. Azure integration, Power Platform extensibility, strong vendor negotiation leverage. Saved $2M on recent deal.

Oracle NetSuite

Best for: $25M–$200M revenue, cloud-first, multi-subsidiary

TCO: $2M–$4M (mid-market)

Timeline: 9–12 months to full deployment

Verdict: Fast deployment, lower TCO than D365/SAP. Limited for complex manufacturing. Strong for services/wholesale. Vendor lock-in risk through customization.

Industry-Specific (e.g., S2K for Food Distribution)

Best for: Deep vertical requirements, established market position

TCO: $1M–$3M (lower than Tier 1)

Timeline: 6–9 months to deployment

Verdict: Lower cost, faster deployment, industry-specific functionality. Migration path to Tier 1 platforms when scale demands it. Currently migrating S2K to D365 at Julius Silvert.

Vendor Negotiation: How to Save $2M+

On the recent Dynamics 365 F&O deal, I saved $2M through structured negotiation. Here's the playbook:

1. Competitive RFP with 3+ Vendors

Never sole-source ERP. Run competitive RFP with Dynamics, NetSuite, and industry-specific. Use competitive tension for 20–30% price reduction before negotiation even starts.

2. Unbundle Implementation Services

Vendors bundle licensing + implementation at 60% gross margin on services. Separate them. License from vendor, implementation from independent partner. Saved $800K on D365 deal through this approach.

3. Multi-Year License Prepayment

Pay 3 years upfront for 25–35% discount. Improves vendor cash flow (their incentive), reduces your TCO, locks in pricing before annual increases. Saved $400K through 3-year prepay on D365.

4. Right-Size User Licensing

Vendors over-license by 30–40%. Most users need read-only access, not full licenses. Use tiered licensing (full, limited, read-only). Saved $300K annually through proper license tiering.

5. Negotiate Exit Terms Upfront

Lock-in kills future negotiation leverage. Negotiate data portability, integration standards, and termination clauses at signing. This preserves optionality and prevents vendor hostage situations.

Migration Risk: Prevent $5M+ Failures

ERP migration failures are common. Industry data shows 60–70% of implementations exceed budget and timeline. The financial cost: $5M+ in rework, business disruption, and opportunity cost.

Across 6 conversions deploying $12M, I've had zero failed migrations. Here's the risk framework:

Critical Risk Factors (Ranked by Impact)

1. Data quality: 60% of migration failures trace to dirty data. Invest $200K–$400K in data cleansing pre-migration. This prevents $2M+ in rework post-go-live.
2. Scope creep: "Let's add this feature" kills budgets. Lock scope at contract signing. Change orders require executive approval. Saved $800K by enforcing scope discipline on D365 deal.
3. Customization addiction: Every customization is technical debt. Challenge every "we've always done it this way" request. Standard functionality reduces TCO 40% vs heavy customization.
4. Parallel operations timeline: Running old and new systems in parallel costs $50K–$100K monthly. Plan for 30–60 day parallel max, not 6 months. Aggressive cutover saves $300K–$600K.
5. Change management failure: Users resist new systems. Without structured training and adoption plans, productivity drops 30–40% for 6–9 months post-go-live. This is $1M+ in lost efficiency for a $100M company.

Conclusion: ERP as Capital Deployment, Not IT Project

ERP selection and deployment is a capital allocation decision requiring PE-grade financial analysis. License cost is 25–30% of TCO. The real cost is implementation, customization, and ongoing support.

Across 6 conversions deploying $12M, the ROI timeline is consistent: 18–24 months through licensing savings, process automation, and support staff reduction. The $2M saved on the recent Dynamics 365 deal represents 50% of annual EBITDA improvement at Julius Silvert.

For PE Operating Partners: treat ERP selection as M&A diligence. Model TCO, not license cost. Negotiate aggressively. Prevent scope creep. Execute with urgency. The difference between good and great ERP deployment is $2M–$5M in value capture.