If you’re evaluating ERP or enterprise software proposals as part of a digital transformation, I can almost guarantee the numbers in front of you are off. Not because vendors are incompetent, or even necessarily dishonest, but because proposals are built on best-case assumptions, a narrow scope, and sales incentives that don’t align with your risk. The good news: you can correct for this and build a realistic plan before you sign anything.
Below I’ll break down the most common failure points we see in proposals and the practical steps to de-risk them.
The Three Big Reasons Proposals Miss Reality
1) Best-case assumptions (that aren’t yours)
Most proposals quietly assume:
- Instant decisions from your team
- Clean, well-mapped data ready to migrate
- A finished integration architecture
- “Train the trainer” actually scales to the masses
- Minimal process change and limited resistance
These assumptions aren’t evil; they’re just vendor-centric. Unless you replace them with your actual constraints, decision cadence, data quality, integration unknowns, and change appetite, you’ll buy a plan for a company that isn’t yours.
2) An incomplete program (masquerading as a complete plan)
A proposal usually covers one work stream well: design, build, test, and deploy the software. Your transformation also includes:
- Process design & standardization
- Organize design and role clarity
- Change management & communications
- End-user training and enablement
- Data cleansing, governance, and migration
- Non-ERP integrations and reporting
- Cutover rehearsal and hypercare
If these aren’t explicitly scoped, with owners, timelines, and dollars, your budget and schedule are already wrong. And because business work streams gate technology progress, the vendor’s dates will slip even if they execute perfectly.
3) Sales incentives and timing pressure
Sales teams are rewarded to:
- Close quickly (this quarter, ideally)
- Avoid scaring buyers with full risk and cost
- Position the smallest number that passes procurement
That doesn’t make them bad actors; it means you must insert realism. If a representative is unusually candid about risk, deals can and do die, which is exactly why most proposals understate it.
What To Do Instead: A Playbook for Realistic Planning
A) Run a true Phase 0 before signing big SOWs
In 6–10 weeks, you can replace hope with evidence:
- Current-state benchmark: decision velocity, data condition, integration map, custom/report inventory, change readiness
- Future-state design at Level 1–2: what will actually change and why
- Operating model decisions: standardization vs. local variance, data ownership, governance
- Program architecture: all workstreams, dependencies, and critical path
- Integrated plan & budget: software + SI + internal backfill + change + data + integrations + contingency (10–25%)
Output: a single, integrated plan vendors must align to, not the other way around.
B) Scrub the vendor assumptions, line by line
Take the proposal and ask:
- What must be true in our business for this line item to hold?
- What lead/lag time do our processes, data, and people require?
- Where do we need parallel work (e.g., data cleanup) to start now?
Update hours, sequence, and milestones accordingly. If the vendor won’t re-baseline to your reality, that’s your signal.
C) Plan for business adoption, not just go-live
Design a change program that goes beyond “click paths”:
- Role-based impacts and RACI changes
- New KPI and incentive alignment (people do what you measure)
- Hands-on enablement with production-like data
- Manager coaching and floor support through hypercare
- Adoption metrics tied to money & time (cycle time, rework, cash, inventory, close time)
D) Treat data as a first-class work stream
- Profile, cleanse, and govern now, not after building
- Freeze mapping rules early; pilot migration end-to-end
- Budget for multiple mock loads and defect rework
- Clarify data ownership (who decides golden sources and fixes)
E) Own your integration and reporting blueprint
- Define target architecture and canonical data early
- Decide build vs. buy for connectors and middleware
- Inventory and rationalize reports (don’t just “recreate everything”)
- Validate performance and security requirements with real volumes
F) Build commercial guardrails into contracts
- Milestone acceptance tied to quality criteria, not just dates
- Change-order discipline with transparent rate cards
- Named resources for key roles; replacement approval rights
- Earn-back/fee at risk tied to agreed outcomes (e.g., data load pass rates, cutover readiness)
Red Flags to Watch For (Quick Checklist)
- “Train the trainer” as the primary adoption strategy
- No dedicated data scope beyond “customer to provide”
- A single go-live date with no contingency or waves
- Vague “light change management” language
- No internal backfill budget for SMEs seconded to the program
- Integrations listed as “TBD” or “assumes standard connectors”
- Testing limited to unit/SIT with superficial UAT and no cutover rehearsal
- A budget that omits hypercare and post-go-live stabilization
If you see three or more, your plan is almost certainly under-scoped.
Final Thoughts
Proposals aren’t destiny, they’re starting points. Your job is to convert a vendor work stream into a business transformation program with realistic assumptions, a complete scope, and contracts that protect value. Do that, and you’ll avoid the overruns and missed outcomes that give ERP a bad name.
If you want a neutral set of eyes on your proposals, or a fast, evidence-based Phase 0, we’re happy to help. We’re 100% independent and vendor-agnostic, and our goal is simple: help you deliver results in money and time, not slideware.
Resources:
- Software Buyer’s Guide: Practical steps for evaluating software and integrators (free download).
- Phase 0 Checklist: The decisions to lock before you sign (free download).
Have questions or want us to sanity-check a proposal? Send it over, we’ll give you straight talk before you commit.
Eric is recognized globally as a leading voice in digital transformation and ERP strategy. Over the past two decades, he has helped hundreds of organizations – including Nucor Steel, Fisher & Paykel Healthcare, Kodak, Coors, Boeing, and Duke Energy – define their technology roadmaps, modernize complex operations, and deliver real business value from large-scale transformation initiatives.
As Founder and CEO of Third Stage Consulting, Eric leads an independent, technology-agnostic advisory firm focused on helping clients navigate the shift from traditional ERP to more flexible, AI-enabled Digital Enterprise Operations (DEO) models. His work spans ERP selection, implementation quality assurance, organizational change, and operating model design across a wide range of industries and geographies.
Eric is also a prolific thought leader, known for his pragmatic takes on AI, cloud, and enterprise software trends, as well as his firm’s benchmark research and frameworks for de-risking transformation. He is dedicated to helping executive teams cut through vendor hype, make confident investment decisions, and successfully reach the “third stage” of their digital evolution.
