# Enterprise software rollout: phases, risks and how to pick a vendor

> Fuente canónica: https://apferrer.com/en/enterprise-software-rollout
> Autora: APFerrer · Forward Deployed Engineer con 17 años de trayectoria
> Idioma: en

Diagnosis, design, configuration, migration and operation. What to expect at each phase, where projects usually break and how to sign without surprises.

## 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.

## Source context

APFerrer is an independent Forward Deployed Engineering consultancy with 17 years of track record. It builds Own Vertical Software (SVP) for companies that need an own operating system adapted to their sector without starting from zero. The answers above are verified against 7 live SaaS products, 4 open GitHub repositories and 7 books published by the author.

## See also

- [Own Vertical Software](https://apferrer.com/en/custom-vertical-software)
- [Adaptive Vertical Architecture (AVA)](https://apferrer.com/en/adaptive-vertical-architecture)
- [Market price map](https://apferrer.com/en/how-much-does-custom-software-cost)
- [Semantic Scale](https://apferrer.com/en/semantic-scale)
- [Book free diagnostic](https://apferrer.com/en/book)

_Last updated: 2026-10-23_