What you get
Included in every customization engagement
- Custom models, fields, and computed values
- Automated server actions and scheduled crons
- QWeb PDF reports and xlsx exports tailored to your data
- Portal, website, and shop extensions
- Unit tests for every server-side change
- Code review, documentation, and knowledge transfer
Process
How the work runs
1
Requirements
We watch you use your current process, then write down what Odoo needs to do.
2
Technical spec
Model diagram, field list, workflow states, edge cases. Signed off before code.
3
Sprint build
Weekly demos on staging. Your team catches issues while they're cheap to fix.
4
QA on staging
Your data, our tests, your users trying to break it.
5
Deploy
Migration script, feature flag rollout, monitoring.
6
Handover
Docs, code walkthrough, README in your repo. You could hire an in-house dev tomorrow.
Common questions
About customization
Do we own the code?
Yes. Every custom module ships to a git repo you control. We don't retain rights or add licensing hooks.
Will upgrades break our customizations?
Not silently. We follow Odoo's OCA-style conventions so upgrades are testable. Support contracts include annual upgrade compatibility passes.
Can we hire an in-house dev later?
Yes, that's part of the plan. Our modules are documented and follow Odoo conventions — a new hire ramps in days, not months.
How do you handle testing?
Unit tests for every server-side change. Integration tests for workflows. CI runs on your repo. No 'works on my machine' handoffs.
Ready to talk customization?
A short call to understand your context, and an honest answer on whether we're a fit.
Book a discovery call