The MUNSAQ Method
No surprises: every stage ends with a signature.
ERP projects usually stall for three reasons: unclear scope, unchecked customization, and weak adoption after go-live. The method is designed to address all three.
- 01
Diagnose
2 weeks
We map how you operate today and measure the KPIs before any talk of modules.
- Deliverables
- Process map
- Outcome Sheet with baselines
- Fixed quote for phase one
- Your team's role
- One workshop per department, sample documents
- Acceptance gate
- Scope and KPIs approved
- 02
Blueprint
2–3 weeks
We describe how every process will run in Odoo, step by step, before configuring.
- Deliverables
- Blueprint document
- Justified customization list
- Migration plan
- Your team's role
- Review and approve the document
- Acceptance gate
- Blueprint signed
- 03
Build
3–6 weeks
We configure in short iterations and demo each one to your team.
- Deliverables
- Configured environment
- Iteration demos
- First migration rehearsal
- Your team's role
- Attend demos, provide data
- Acceptance gate
- Configuration complete
- 04
Prove
1–2 weeks
Your team tests real scenarios, and we reconcile a second migration rehearsal.
- Deliverables
- UAT results
- Reconciliation report
- Role-based training
- Your team's role
- Run and sign off tests
- Acceptance gate
- UAT sign-off
- 05
Go live
1 week + 30 days hypercare
Final migration, real operation, and our team with you daily through the first month.
- Deliverables
- Cut-over plan
- Approved opening balances
- Hypercare
- Your team's role
- Run the system and report issues
- Acceptance gate
- First successful month-end
- 06
Measure & improve
Day 90, then quarterly
We re-measure the Outcome Sheet KPIs, show what moved and what didn't, and plan the gap.
- Deliverables
- Day-90 review
- Improvement plan
- Your team's role
- Review session with management
- Acceptance gate
- Next phase approved
The standard-first rule
Every customization request faces two questions: what problem does it solve, and what is it worth? If configuration or a process change solves it, that's what we recommend.
Change requests
Anything outside the Blueprint is written up, priced and approved by the decision-maker before it is built. No surprise invoices.
The Outcome Sheet
KPIs we measure in the Diagnostic and re-measure at day 90. If a target isn't met, we explain why and how we'll close the gap.
Next step
Have a question? The smart assistant in the corner answers now.
It answers instantly about our services, integrations and indicative pricing. When you're ready, our team is on WhatsApp or the contact form for a free discovery call.