Finance-first
Finance Foundation
Accounting, invoicing, approvals, and core controls.
Best for: finance-first rollouts.
Choose your Phase 1 ERP scope
Start with the business flows you need most.
Packages make it easier to define your MVP scope without turning the discovery conversation into a custom workshop. Choose the operational flows you want in Phase 1, then decide how much SSC should lead the implementation.
This page is about scope, not service depth. Packages define what is in scope. Service layers define how much SSC leads. Continuity defines what happens after go-live.
How buyers usually decide
01
Choose your Phase 1 scope
Select the business flows you need first.
02
Choose the service layer
Decide how much SSC should lead across discovery, setup, training, testing, and go-live.
03
Choose continuity after go-live
Decide whether you need no retainer, a bounded Success Pack, or a governed Sustain Pack.
Packages define scope, not service depth
Make the Phase 1 decision easier.
Start by choosing the business flows that matter most to your Phase 1 rollout. This helps define MVP scope more clearly, keeps discovery conversations sponsor-readable, and reduces the need to solve every future phase on Day 1.
Scope
What goes into Odoo first
Your package defines which business flows are included in the MVP or Phase 1 implementation.
Service depth
How much SSC should lead
Your service layer determines the level of delivery support, governance, training, and change enablement around that scope.
Continuity
What happens after go-live
Your continuity path defines whether support ends after launch or continues through bounded or managed follow-through.
Package grid
Choose the flows you want in scope.
Start with the business flows that matter most to your Phase 1 rollout. Then choose the right service layer and continuity path around that scope.
Inventory baseline
Warehouse + Finance
Warehouse control, stock movement visibility, and finance baseline.
Best for: operations that need warehouse visibility before broader trading scope.
Stock-led operations
Trading Essentials
Sales, purchasing, inventory, and finance.
Best for: distributors and trading businesses.
Production-led
Manufacturing Essentials
MRP, inventory, purchasing, and finance baseline.
Best for: teams with production and shop-floor coordination needs.
Service delivery
Services & Billing
Projects, timesheets, billing, and revenue tracking.
Best for: service teams connecting execution to invoicing.
Professional services
Professional Services Suite
CRM, project delivery, billing, and utilization visibility.
Best for: firms selling expertise, projects, and billable delivery.
Core HR operations
People Ops
Employees, attendance, time off, documents, and core HR.
Best for: organizations formalizing HR admin and employee processes.
Talent acquisition
Recruitment Implementation
Pipeline, hiring workflow, approvals, and onboarding handoff.
Best for: teams modernizing recruitment and hiring coordination.
Catalog bridge
Explore More
See additional packages, broader combinations, and future catalog-ready offer structures.
This is the best route for buyers who want to review more options before requesting discovery.
Explore the catalog →How packages fit with service layers
Scope first. Service depth second.
The same package can be delivered with different levels of our support. The right service layer depends on change complexity, internal ownership, and how much guidance the client needs.
Lean start
ERP Launch
Often paired with Finance Foundation, Trading Essentials, or Services & Billing where the client can self-drive more of the rollout.
Typical next step: Success Pack or Sustain when follow-through is needed after launch.
Recommended default
Guided ERP Implementation
Often paired with Trading Essentials, Manufacturing Essentials, and Professional Services Suite where the rollout needs stronger delivery support and safer execution.
Typical next step: Sustain Growth or a targeted next-phase Success Pack.
Premium path
Transformation-Led ERP
Best used with broader package combinations, multi-department rollouts, or environments where governance, stakeholder alignment, and staged adoption matter more.
Typical next step: Sustain Growth or Sustain Scale.
Continuity stays separate
After scope and service layer are agreed, continuity is its own decision: no retainer, a bounded Success Pack, or a managed Sustain Pack.
Common buyer examples
Examples that make scope easier to buy.
Buyers do not need to oversolve everything at once. Agree the Phase 1 scope first, then choose the right service layer and post-go-live path.
Path A — Finance-first start
A lower-friction operational launch
Scope: Finance Foundation
Service: ERP Launch
Continuity: Success Pack
Path B — Default SME
The practical recommended route
Scope: Trading Essentials
Service: Guided ERP Implementation
Continuity: Sustain Growth
Path C — Services firm
Delivery, billing, and utilization visibility
Scope: Professional Services Suite
Service: Guided ERP Implementation
Continuity: Training Burst + Sustain Growth
Path D — Talent ops
Hiring workflow modernization
Scope: Recruitment Implementation
Service: ERP Launch
Continuity: Sustain Scale
Ready to define your Phase 1 scope?
Start with the business flows that matter most.
We’ll help you choose the right package, match it to the right service layer, and shape a Phase 1 rollout that fits your priorities, readiness, and pace.