Four phases, and you approve each one before paying for it
First we learn how your company runs; then we choose the technology. Each milestone ends with a deliverable your team reviews, and we invoice it once you approve it in writing.
Book a 30-min diagnostic callTake the self-assessment (7 min)
Diego Muñoz replies in person, on Lima time.
Milestone 2 · Process design
- Process map validated with purchasing and warehouse
- Approval matrix by amount
- List of what stays out of scope
Illustrative example of the sign-off you sign at the end of each milestone.
- Assessment before any software proposal
- One deliverable per milestone
- Invoice only after your written approval
- Licences in your company’s name
The assessment decides which software to buy, or whether you need any
We look at who requests, who approves and who pays in your company. With that map, we choose the technology for the process that already works.
When the system is bought first
- The demo wins over management and the team finds out later
- The process is forced to fit the screens
- Approvals stay on WhatsApp and email
- Excel goes back to being the real system
When the assessment comes first
- We map the process with the people who run it
- We define who approves what, and up to which amount
- We compare options, including the tool you already have
- The proposal states what is in and what stays out
Each milestone is invoiced when you approve it in writing. If a deliverable falls short of what we agreed, we fix it first.
Diego MuñozLeads every Dmunoz Group project
What happens in each phase, and who takes part on your side
- What we do
- We interview each team, walk through the process with the real documents and note where time is lost.
- Who takes part on your side
- Management, finance and one lead per team, in short sessions.
- How it is approved
- We present the report; management signs it or asks for changes.
- What we do
- We draw the target process and compare options: Odoo, another tool, custom development or improving what you already have.
- Who takes part on your side
- Team leads validate the process; management chooses the option.
- How it is approved
- You sign the proposal with milestones, amounts and what stays out.
- What we do
- We configure a test environment, migrate master data and balances, and train each team.
- Who takes part on your side
- Key users who test with real cases from your operation.
- How it is approved
- One sign-off per milestone once the tests pass.
- What we do
- We support the go-live, log every issue and adjust what is needed.
- Who takes part on your side
- Your team working in the system and one person who gathers questions.
- How it is approved
- Project close with a documented handover.
Four commitments in writing before we start
They are signed with the proposal. If one changes, we agree it again in writing.
- 12standard deliverablesThree per milestone, from the approval matrix to the handover.
- 17–20Odoo versionsWe implement Community and Enterprise; the proposal states which one applies.
- SUNAT+ PLEPeruvian localisationE-invoicing and electronic ledgers included in every Odoo implementation in Peru.
- 1dayworking day to replyYour message gets a reply with the next step proposed.
Odoo lab environment, fictitious company.
What you keep at each milestone
Assessment report
Current process map, approval matrix and prioritised requirements.
Milestone proposal
Target process, recommended option, amount per milestone and what stays out.
Tested system
Test environment with your data, migrated master data, manuals for each team and signed sign-offs.
Handover
Resolved issues, documented configuration and access in your company’s name.
Odoo lab environment, fictitious company.
How a milestone-based project is paid
1
We agree the milestones
The proposal sets the deliverable and amount of each milestone.
2
We deliver
Your team reviews the deliverable in the test environment.
3
You approve
You sign the milestone sign-off or ask for corrections.
4
We invoice that milestone
Only after your written approval.
Software licences, such as Odoo Enterprise, are purchased separately in your company’s name. A change of scope is estimated in hours and carried out with your written approval.
Book a 30-min diagnostic callSee the guides and the processes on screen
What clients usually ask before starting
If your question isn’t here, send it on WhatsApp.
It depends on the scope the assessment reveals. The proposal states the amount of each milestone before we start, and each one is invoiced once you approve it.
Yes. The assessment is a phase with its own deliverable, and you keep the report even if you decide not to continue.
The proposal sets the duration based on the size of your operation. We review progress with you every week.
You don’t approve it and tell us what is missing. We fix it and present it again; the invoice for that milestone waits for your approval.
No. Odoo is the ERP we implement when the assessment calls for an integrated system. If your current tool solves the problem, we recommend keeping it.
We ask for short sessions with each team during the assessment and key users to test during implementation. We agree the schedule with you.
Your company. Licences, access and the code we write for you stay in your name.
Start with the 7-minute assessment
- Answer 12 questions
- See which cycle costs you most
- In 30 minutes I tell you where to start