Phased Odoo implementation: native or tailored to your processes
We get Odoo into production with a phased methodology —diagnosis, configuration, data migration, training and go-live— either native (standard, fast and economical) or adapted to your operation. We are a software factory with documented processes that reduce go-live risk, and the configuration is 100% yours. No black box, no licenses you never use.
What is implementing Odoo?
Implementing Odoo means actually getting it to run: configuring the modules your company needs (CRM, Sales, Inventory, Accounting, Purchasing, Manufacturing), loading your data, training your team and supporting the go-live.
See in detail
We do it in phases, with verifiable deliverables in each one, so there are no surprises on launch day. You can start native —using standard Odoo as it ships, which is the fastest and most economical route— or adapted to your processes when your operation demands it. We are a software factory founded in 2018 (Monterrey, Guadalajara + Texas, 5.0★ on Clutch) with more than 100 projects delivered; we are Odoo Ready and our edge is not boasting years of Odoo, but a documented process discipline that lowers the risk of a failed go-live. The configuration and code are yours from the start.
Native vs adapted: standard Odoo as far as it goes
The differentiator that converts: we do not push development. Standard where it reaches; custom code only where it hurts. In both cases, code 100% yours.
Standard Odoo as it ships
- CRM, Sales, Purchasing and Inventory configured
- SAT chart of accounts and l10n_mx
- CFDI 4.0 stamping with your PAC
- Roles, permissions and approval flows
- Standard reports and dashboards
Development only where the standard falls short
- Retailer or automotive addendas
- Stamped payroll (add-on)
- Industry-specific logic
- Integrations with legacy systems
- Custom QWeb reports
- A connector to a PAC outside the integrated ones
The native route is fastest and cheapest; each adaptation is justified against a real process. The code and configuration are 100% yours, no vendor lock-in.
The phased method 00-06
2-week sprints with functional demos and verifiable deliverables at every phase. No surprises at go-live — and a single SLA: a 3-month warranty from launch, not a different term per package.
- 00Technical analysisFixed budget, creditedNot: no config yet
- 01RequirementsCatalog + roadmapNot: unvalidated promises
- 02Config + LocalizationInstance validated by areaNot: payroll (add-on)
- 03Conditional developmentModules, your codeNot: if standard already solves
- 04ETL migrationData reconciled 100%Not: re-stamp CFDI
- 05Training + UATSigned UAT + cutover planNot: training with no material
- 06Go-live + warrantyIn production, config 100% yoursNot: hourly AMS (separate plan)
100 · Technical analysisDeliverablea fixed budget in writing, credited to the projectNot includeddevelopment or configuration yet
The step zero: we review your operation, decide edition and tier, and close scope and budget.
201 · RequirementsDeliverablerequirements catalog and an agreed roadmapNot includedscope promises unvalidated against a real process
We capture AS-IS processes and Mexican tax requirements, and prioritize modules by phase.
302 · Configuration + LocalizationDeliverableinstance configured and validated by areaNot includedstamped payroll, an add-on in any edition
Modules, users, roles, SAT chart of accounts and l10n_mx / CFDI 4.0 on standard Odoo.
403 · Development (conditional)Deliverablemodules with code 100% yours and documentationNot includeddevelopment when standard configuration already solves it
Only what the standard does not cover: custom Python/OWL modules, by inheritance, without patching the core.
504 · Data migration (ETL)Deliverabledata reconciled 100% and a cutover with a rollback planNot includedre-stamping already-issued CFDI — the SAT prohibits it
Catalogs, balances and history with reconciliation reports and a parallel run before cutover.
605 · Training + UATDeliverablesigned UAT checklist and an agreed cutover planNot includedtraining with no onboarding manuals or videos
Per-role sessions with real cases and an acceptance cycle with your key users.
706 · Go-live + warrantyDeliverablesystem in production and documented configuration — 100% yoursNot includedAMS support with an hourly SLA, a separate plan by contract
Supported production launch with a 3-month warranty from go-live.
It all starts with the analysis (phase 00)
We do not quote an implementation off the cuff. Phase 00 is the technical analysis: we review your operation, decide what stays native and what needs adaptation, choose edition and tier, and hand you scope and a fixed budget in writing. It is yours even if you implement with someone else, and it is credited to the project if you move forward.
No free assessment that later quotes a fortune: we prefer to hand you a number you can defend to your board.
Request phase 00When you need it
What the implementation includes
Process analysis
We map how your business operates today and contrast it with the Odoo standard, to decide what stays native and what needs adaptation — minimizing unnecessary development.
Module configuration
We enable and parameterize the modules you need (CRM, Sales, Inventory, Purchasing, Accounting, MRP), with users, roles, permissions and workflows aligned to your real operation.
Data load & migration
We import customer, product and vendor catalogs, plus balances and history from your previous system, with reconciliation reports prior to launch.
Per-role training
Hands-on sessions per area —sales, warehouse, purchasing, accounting and management— with manuals and recorded videos to onboard new staff later.
Mexican localization (CFDI 4.0)
We configure l10n_mx and l10n_mx_edi_40 so the ERP stamps CFDI 4.0 in compliance with the SAT from day one —income, expense, payment and transfer— through an authorized PAC, with no parallel portals.
Supported go-live
We accompany the production launch with active monitoring, fine-tuning and incident resolution during the first critical weeks.
Initial support & QA
Functional and regression testing backed by our internal ARIA platform before each delivery, plus a post-go-live support window to stabilize the operation.
Handoff & documentation
We hand over the instance with the configuration, workflows and access documented, in a repository you own, so any competent team can keep it running with no vendor lock-in.
We run it, we do not just implement it
We run iTech on our own Odoo 19: sales, projects, timesheets and invoicing. We implement with the same phased method we used to get our own running — we do not sell an ERP we do not use.
erp.itechdev.com.mxProof of competence, not a client case.
Frequently asked questions
Can't find your question? Talk to an engineer — no sales script.
Contact us →Native or custom implementation? Which suits me?
We always start by evaluating the native version: standard Odoo as it ships covers most needs and is the fastest, most economical route. We only propose adaptations when a real business process does not fit the standard and the cost is justified. We make that decision together in the diagnosis, without pushing development you do not need.
How long does it take and how much does it cost?
It depends on scope and how many processes require adaptation. As a market reference, a native roll-out of a few modules is typically measured in weeks, while an implementation with adaptations and complex migration takes longer. We do not sell a blind fixed figure: after the diagnosis we deliver scope and a concrete estimate, with no ambiguous scope.
Odoo Community or Enterprise?
Community is open source with no license cost and covers most operational needs. Enterprise (paid) adds official accounting, e-signatures, a low-code studio, mobile apps and direct support from Odoo S.A. We advise without bias: the decision depends on your volume, the modules you need and your budget, not on a commission.
Which modules do you implement at launch?
Whatever your operation needs to run from day one: most commonly CRM, Sales, Inventory, Purchasing and Accounting, plus Manufacturing (MRP), Project, HR or E-commerce depending on your case. In the diagnosis we define the minimum viable scope to launch and what gets added in later phases.
Is iTechDev a certified Odoo partner?
We are an Odoo Ready software factory: we implement, configure and migrate on Odoo. We do not sell a partnership tier or years of Odoo seniority as an argument; our real edge is documented-process discipline that reduces go-live risk, a nearshore team in Monterrey, Guadalajara and Texas, and configuration that is 100% your property, with no vendor lock-in.
Does the implementation include SAT electronic invoicing?
Yes. Since you operate in Mexico, localization is part of the standard scope: we configure l10n_mx and l10n_mx_edi_40 so Odoo stamps CFDI 4.0 in compliance with the SAT —income, expense, payment and transfer— through an authorized PAC (Finkok or Factura.com), with DIOT, the payment complement and, if your business requires it, carta porte or comercio exterior. We finalize the exact fiscal scope in the diagnosis.
Request your analysis (phase 00)
Tell us where you are and we schedule the analysis: scope, edition and a fixed budget in writing.
What we do guarantee
- Phase 00 (the analysis) is yours, whether you implement with us or not.
- A single SLA: a 3-month warranty from go-live.
- Native first: we do not push development you do not need.
- Code and configuration 100% yours, no lock-in.
Get Odoo running, in phases and on a date
Phase 00 hands you scope, an edition decision and a fixed budget in writing.