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?
Frequently asked questions
What are the standard phases of an enterprise software rollout?
Five phases: diagnosis, design and budget, configuration and integrations, migration and validation, operation and evolution. Each phase with its own deliverable and closed budget before moving to the next.
How long does each phase take?
Depends on scope. In a standard custom software rollout, the full cycle is usually 6 to 10 months (source: Vertebra Gestión). In Own Vertical Software (SVP) the cycle drops to 6 to 12 weeks because the vertical body already exists.
Where do rollout projects usually break?
In integrations that turn out more expensive or impossible when actually touched, in legacy data that does not fit the new product's model, in open budgets creeping up during development, and in the absence of an exit plan when something changes.
What should I ask the vendor before signing?
Whether the budget is closed per phase or open by the hour, who owns the data, rules and configuration, whether everything can be exported and providers switched with no lock-in, and what happens if the vendor disappears or the model changes.
Can I leave the vendor with no lock-in?
Yes, if defined in the contract from the start. In SVP no-lock-in exit is part of the criterion: dedicated instance, exportable data, perpetual license of the core if agreed, and guaranteed continuity even without maintenance.
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.