Standard app activation, blueprints, templates, and practical Q&A.
Odoo ERP implementation paths
Choose the right ERP implementation path.
Match SSC’s level of leadership to your internal ownership, process complexity, and adoption risk.
Guided ERP is the recommended paid implementation path for most first-time ERP buyers.
SSC leads a structured implementation from discovery through Go-Live Support.
Guided delivery plus process standardization and adoption leadership.
The implementation decision
Three paths. One decision: how much SSC leads.
Choose based on who will drive decisions, how much process change is required, and how much support the team needs to reach a controlled go-live.
Can a strong Client Project Lead self-drive decisions, data, training, and follow-through?
Are flows simple and standard, or cross-functional, multi-site, and inconsistent?
Does the project need only system guidance, or active sponsor and change leadership?
01
Start Somewhere
1 / 3
Start Somewhere
A limited launch foundation for clients who can self-drive configuration, data, testing, training, and rollout.
Best fitSimple scope, standard processes, capable internal owner
SSC leadsApp activation, templates, blueprints, and practical Q&A
Client ownsDetailed implementation and go-live execution
Guided ERP
A structured paid implementation with SSC leading discovery, configuration, readiness, Business Testing support, and Go-Live Support.
Best fitMost SMEs and first-time ERP buyers
SSC leadsImplementation governance and fit-to-standard delivery
Client ownsDecisions, data validation, key users, and approvals
Transformation-Led ERP
Guided ERP plus facilitated process standardization, sponsor alignment, change planning, and stronger adoption design.
Best fitCross-functional, multi-site, or higher-resistance environments
SSC leadsImplementation plus the agreed process and adoption workstream
Client ownsActive sponsor, functional leads, champions, and governance participation
Clear boundaries
What changes between the paths.
The Odoo platform may be the same. The difference is how much implementation work, decision support, readiness, and adoption leadership SSC provides.
Decision area
Start Somewhere
Guided ERP
Transformation-Led
Best fit
Simple, standard scope with a strong internal owner.
Most organizations that need a controlled implementation partner.
Cross-functional change with process inconsistency or adoption risk.
SSC provides
- Standard app and localization activation
- Initial setup confirmation
- Blueprints, templates, and Q&A
- Discovery and Phase 1 scope
- Configuration and demonstrations
- Testing support, readiness, cutover, and Go-Live Support
- Everything in Guided ERP
- Process standardization and sponsor governance
- Change planning, champion enablement, and adoption checkpoints
Client provides
Configuration, data execution, testing, training, and rollout ownership.
Named Client Project Lead, decisions, data owners, key users, testers, and approvals.
Active sponsor, functional leads, change champions, and commitment to standardize.
Separate scope
Detailed configuration, imports, Studio, training, testing management, cutover, and Go-Live Support.
Enterprise-scale change management, major custom work, extra entities, sites, modules, or integrations.
Unbounded organization redesign or technical work outside the approved implementation.
Start Somewhere
Included
- Standard app and localization activation
- Initial company/admin setup confirmation
- Blueprints, migration templates, and Q&A
Separate
- Detailed configuration and import execution
- Training, Business Testing management, cutover, and Go-Live Support
Guided ERP
Included
- Discovery, Phase 1 scope, configuration, and demonstrations
- Trial migration support, key-user enablement, Business Testing support, and Go-Live Support
Separate
- Enterprise-scale change management
- Major custom work, extra entities, sites, modules, or integrations
Transformation-Led ERP
Included
- Everything in Guided ERP
- Process standardization, sponsor governance, change planning, champions, and adoption checkpoints
Separate
- Unbounded organization redesign
- Technical work outside the approved implementation or Change Request
Start Somewhere is not a free full implementation. The Odoo Enterprise subscription is paid directly to Odoo; the defined launch foundation carries no separate SSC professional-service fee while SSC remains the assigned Partner of Record.
How the proposal is built
Scope and service depth are separate decisions.
Packages define the business flows. The implementation path defines how much SSC leads. Add-ons and continuity are treated separately and transparently.
Foundation & Governance: every formal Guided ERP or Transformation-Led implementation includes FP-FND-01 once. Start Somewhere receives a lighter launch foundation.
The approved Phase 1 business flows.
Start Somewhere, Guided ERP, or Transformation-Led.
Only where a justified need sits outside the selected pack.
Sustain Pack or a separately approved next phase.
Guided and Transformation-Led delivery
A controlled path to go-live.
Both paid paths follow the same implementation spine. Transformation-Led adds the agreed process and adoption workstream around it.
00
Foundation & governance
1 / 5
00
Foundation & governance
Scope control, cadence, roles, access, decisions, risks, and data ownership.
01
Discovery & scope
Fit-to-standard workshops, Phase 1 definition, success measures, and backlog.
02
Configure & validate
Standard-first setup, demonstrations, trial data, and logged decisions.
03
Business Testing & readiness
Key-user validation, issue triage, cutover rehearsal, and go/no-go readiness.
04
Go-live & transition
Controlled cutover, smoke tests, Go-Live Support, stabilization, and handover.
Start Somewhere follows a lighter route.
SSC activates the agreed launch foundation and shares the implementation kit. Detailed configuration, data execution, testing, training, and rollout remain client-led unless separately engaged.
Next step
Define the Phase 1 scope. Then choose the right path.
Bring the priority business flows, target timeline, entities or sites, approximate users, migration sources, and named integrations. SSC will recommend the most practical package and implementation path.