Enterprise software rollout: phases, risks and vendor.
Signing enterprise software is a 3 to 5 year decision. These are the standard phases, the moments where projects usually break, and the questions that prevent signing a contract you will regret.
The standard process and where it breaks in practice
Diagnosis
Understand how the company operates today. Who decides what, what data exists, which integrations are non-negotiable. Without diagnosis there is no real budget, only a guess.
Risk: vendor that skips this phase and jumps straight to product demo.
Design and quote
Map the product to the real process. Decide what is standard, what configures and what develops. Close the budget by phases, not as a lump sum.
Risk: open budget that starts creeping up during development with no control.
Configuration and integrations
Instance live, master data loaded, permissions defined, integrations plugged in. This is where the particularities nobody mentioned at diagnosis time show up.
Risk: integrations that turn out more expensive or impossible when actually touched.
Migration and validation
Real data inside the system. Validation on concrete cases. Phased rollout if the sector is regulated. Nobody goes live without tested real data.
Risk: legacy data that does not fit the new product's model.
Operation and evolution
Your team runs day to day. The vendor evolves the system under agreement. Emerging changes are scoped separately. No invoice surprises.
Risk: total vendor dependency with no documented exit plan.
- Closed budget per phase or open by the hour?
- Who owns my data, my rules and my configuration?
- Can I export everything and switch providers with no lock-in?
- What happens if the vendor disappears or the model changes?
A single point of contact for all five phases
In SVP the same team runs all five phases, with a closed budget per phase and no surprises. Typical timeline: 6 to 12 weeks for the full cycle.