When an integrator answers your RFP, one sentence almost always shows up: “we follow the vendor’s methodology.” It is reassuring, it is vague, and it tells you almost nothing about what the next eighteen months will look like. SAP Activate, Microsoft’s Success by Design, Oracle’s OUM, Odoo’s method, the approaches used across the Sage partner network: these frameworks differ in ambition, in precision, and in the space they leave for the customer.
This article compares them on criteria you can verify: phases, quality gates, client role, tooling and agile compatibility. It closes with a recommendation by project profile and the questions to put to your integrator. Phase names come from the official documentation cited; where an official source is not freely accessible, we say so.
Why the Vendor Methodology Matters (and What It Does Not Replace)
A vendor methodology brings three useful things. First, a shared vocabulary: when everyone talks about “fit-to-standard” or a “blueprint review”, you can compare bids on a like-for-like basis. Second, product-specific good practice: what the vendor knows about the projects that fail on its platform (performance, integrations, data). Third, checkpoints that allow someone to say “stop, we are not moving to the next phase.”
What it does not do is govern your project. Microsoft says as much: Success by Design is designed to complement the methodology chosen by the project team, and the documentation states that the framework does not guarantee the outcome (Microsoft Learn, Success by Design). In other words, a vendor methodology is a framework, not a plan. It does not decide scope for you, the trade-off between budget and schedule, the availability of your key users, or the quality of the migrated data. That remains customer governance: steering committee, PMO, sponsor.
One Profile per Methodology
SAP Activate
Phases. SAP Activate has six phases: Discover, Prepare, Explore, Realize, Deploy, Run. According to the official SAP Learning course, the core of delivery plays out between Prepare and Deploy (the “four core phases”), with Discover being a no-commitment exploration phase and Run covering operations after go-live (SAP Learning, methodology structure).
Deliverables and logic. The Explore phase rests on “fit-to-standard” workshops: standard SAP processes are demonstrated on a ready-to-run system, and only the gaps get specific treatment. The Realize phase proceeds in iterations (sprints) and ends with integration testing and user acceptance. The method is organised in workstreams (project management, design and configuration, testing, data, adoption, technical architecture, operations and support, among others), per the same course.
Quality gates and tooling. SAP Activate roadmaps include quality gates and checkpoints per phase, supported by SAP Cloud ALM (SAP Learning page).
Strength. It is the most formalised method on the market, with a detailed roadmap, accelerators and associated tooling. It gives you a precise yardstick for reading a project plan.
Weakness. Its very richness. An integrator can display the vocabulary without applying the spirit: a “rushed” fit-to-standard squeezed into two workshops produces hidden custom developments later. It also assumes a client able to sustain intensive workshops with business decision-makers.
Microsoft Success by Design (Dynamics 365)
Phases. A caution on secondary sources: Microsoft’s current documentation describes five phases, not four: Discover, Initiate, Implement, Prepare, Operate. Microsoft describes them as “methodology agnostic” (Microsoft Learn).
Quality gates. Success by Design is above all a system of reviews. The Solution Blueprint Review, which is mandatory, opens the process; it leads to thematic Implementation Reviews (data model, security, integrations, testing, ALM); the Go-live Readiness Review, also mandatory, closes the loop before cutover. Findings are classified as assertions, risks and issues, then tracked with red, yellow and green health indicators.
Client role. The customer and its steering committee are the recipients of the conclusions: the documentation gives the example of an architect recommending that the steering committee add performance testing to the test plan.
Strength. A genuine independent audit of technical risk, backed by platform telemetry, and compatible with any delivery method.
Weakness. It is not a complete delivery method. Success by Design does not tell you how to run your design workshops or plan your sprints; the integrator brings its own method, of variable quality, and the review framework is only worth what its actual activation is worth.
Oracle Unified Method (OUM)
Phases. OUM builds on the Unified Process and describes five phases: Inception, Elaboration, Construction, Transition, Production, according to the Oracle white paper that circulates publicly (Oracle white paper on OUM). To verify: the official OUM documentation is not freely accessible, which is in itself a piece of information (see below).
Logic. OUM is described as driven by business processes and use cases, with a planned approach that is nonetheless tailorable: it includes guidance on selecting the minimal subset of tasks, planning iteratively and applying agile techniques (Wikipedia, Oracle Unified Method). Version 6.4.0 covers application implementation, cloud services, version upgrades and BI, among others.
Access. OUM is restricted to Oracle employees, to Oracle PartnerNetwork partners at the Diamond, Platinum and Gold levels, and to customers in the OUM Customer Program (same source). A customer outside that program cannot read the method its integrator is promising: ask for the relevant extracts.
Strength. A very complete, proven method that also covers non-ERP projects and migrations.
Weakness. Opacity for the customer, and a “plan-driven” heritage that takes real adaptation work to deliver iteratively on Oracle Fusion Cloud.
Odoo
Philosophy. Odoo does not publish a lifecycle of named phases comparable to SAP Activate. Its “QuickStart” methodology is a charter of principles: an implementation in several coherent phases with regular go-lives, standard-first adoption, and the “80-20” rule: focus on 80% of the stated needs and set aside the 20% of objectives with the least favourable cost/benefit ratio (Odoo documentation, QuickStart methodology). That page belongs to an older version of the documentation; to verify with your partner for the version currently in force.
Client role. The method explicitly names a SPoC (Single Point of Contact) on the client side, responsible for transferring business knowledge, and an Odoo consultant applying a “Train the Trainer” logic.
Strength. Lightness, a strong adoption focus, and a very good fit for SMBs wanting fast go-lives.
Weakness. Few formal quality gates: control rests on the partner’s discipline and on your SPoC. Practices vary from one partner to another.
Sage
To my knowledge, Sage does not offer a single method that applies to all its products: the portfolio covers very different solutions (Sage 50, Sage 200, Sage X3, Sage Intacct) and delivery runs through a partner network. Methods do exist on the partner or programme side (STREAM, Xpedite, “Fast Start” offers), for example Net at Work’s Xpedite for Sage X3. To verify product by product with Sage and the integrator: absent a formal vendor framework, the quality of the method is the quality of your partner.
Strength. Flexibility, the proximity of the local network, packs suited to small organisations.
Weakness. No common reference to cite in a contract: you must require that the method be described and appended.
Comparison Table
| Criterion | SAP Activate | Success by Design | Oracle OUM | Odoo | Sage |
|---|---|---|---|---|---|
| Nature | Complete delivery method | Risk review framework | Complete delivery method, tailorable | Charter of principles | Varies (partner) |
| Formality | Very high | High on reviews | High | Light | Varies |
| Phases | Discover, Prepare, Explore, Realize, Deploy, Run | Discover, Initiate, Implement, Prepare, Operate | Inception, Elaboration, Construction, Transition, Production (to verify) | Coherent phases, regular go-lives | Depends on partner |
| Quality gates | Quality gates per phase | Blueprint, implementation and go-live reviews | Checkpoints per phase | Lightly formalised | Lightly formalised |
| Client role | Workshops, testing, adoption | Recipient of findings, arbiter | Depends on access to the method | Named SPoC | Depends on contract |
| Tooling | SAP Cloud ALM | FastTrack tools and telemetry | OUM documentation (restricted access) | Shared tracking documents | Depends on partner |
| Agile fit | Sprints in Realize | Agnostic | Possible, needs tailoring | Natural | Depends on partner |
| Best fit | Mid-market and large enterprise | Mid-market and Microsoft-centric groups | Large Oracle accounts | SMBs and light mid-market | SMBs |
What These Methods Say (and Don’t Say) About Agile
All the methods cited now claim some form of iteration, but the word means different things. At SAP, iteration is localised: sprints live inside the Realize phase, between a fit-to-standard scoping stage and a final acceptance phase that both remain highly structured. At Microsoft, the framework is neutral: agility belongs to the integrator’s method, and Success by Design merely grafts reviews onto it. At Oracle, agility is a “tailoring” option on a method that was originally plan-driven. At Odoo, the spirit of regular delivery is native, at the price of less formal controls.
The practical consequence: don’t ask “are you agile?” Ask when the client first sees configured software, and when it can reject a deliverable. The answer reveals the real method, whatever name is printed on the cover page.
Recommendation by Profile
- Industrial mid-market company on SAP. Require SAP Activate in the contract, with the quality gates and the calendar of fit-to-standard workshops. Your main risk is the rushed fit-to-standard: fix the number of custom developments you will accept before the Realize phase.
- Group already in the Microsoft ecosystem. Have the contract state that the Solution Blueprint Review and the Go-live Readiness Review will be held (both are mandatory within the Microsoft framework), along with the reporting of findings to the steering committee. In parallel, check the integrator’s own delivery method.
- Large account on Oracle. Ask the integrator to show the OUM deliverables applicable to your project, since you cannot read them directly, and to explain how it adapts the method to iterative delivery.
- SMB on Odoo. Name an available SPoC (this is not a spare-time role) and negotiate a split into work packages with successive go-lives. See also our comparison of vendor-direct, integrator or SI delivery.
- SMB on Sage. Have the partner’s method appended to the contract, with phases, deliverables and exit criteria. Otherwise you will have nothing to hold them to if the project drifts.
How the Integrator Applies (or Bends) the Method: 6 Questions for the RFP
- Which version of the method and which exact deliverables will be produced at each phase? Ask for the list, not the logo.
- Who on your side is certified on the method and will actually be assigned to my project?
- Which quality gates are planned, who runs them, and who can decide not to pass a gate?
- What role for my teams: how many key-user days per phase, and which workshops are mandatory?
- How do you adapt the method to my context (agile, work packages, multi-country)? See our article on adapting Scrum to ERP deployments.
- What happens when a gate is red? What impact on the schedule, and who bears the extra cost?
An integrator who answers these six questions with generalities is using the method as a sales argument, not as a commitment.
Combining the Vendor Methodology with Internal Governance
The right architecture has three tiers. The vendor methodology supplies the phases, deliverables and reviews. The integrator’s method defines how work is organised day to day. Your internal governance (PMO, steering committee, sponsor) arbitrates.
Quality gates are your control levers. A gate is only worth something if someone on your side is authorised to say no. So put a written rule in the steering committee charter: exit criteria for each phase, the role of acceptance testing, the right to suspend payment of a milestone. The slicing logic (big bang or work packages) is prepared upstream: read our analysis of big bang versus phased deployment strategy.
On the agile side, the more recent methods (sprints in Realize at SAP, the agnosticism of Success by Design, the work-package logic at Odoo) leave room for iteration, but none of them removes the need for a budget frame and a prioritised scope.
Checklist for Reading an Integrator’s Project Plan
- Do the phases carry the names of the announced method, with the same outputs?
- Does each phase have a gate with written criteria and a named decision-maker?
- Is the workload on your teams quantified by phase and by role?
- Do the design workshops (fit-to-standard or equivalent) have enough duration, and a cap on custom developments?
- Are all the tests (integration, performance, acceptance) in the plan, performance included?
- Does data migration have its own test cycles and its own criteria?
- Are change management and training scheduled before acceptance, not after?
- Does the cutover plan specify go/no-go criteria and dress rehearsals?
- Is the post-go-live stabilisation period contractually defined?
Going Further
A method is only as good as the people applying it: to assess your candidates on 10 weighted criteria, use our ERP integrator scoring framework. And to receive our weekly analysis of ERP project management, join the newsletter and download our resources.