About Canzonia
Who you're actually hiring
We're an Odoo consultancy in Vancouver. Eleven years in Odoo, and nine implementations behind us. We take on full ERP programs, single integrations, and support on a system somebody else built.
The Record
Eleven years deep in Odoo
Canzonia started in 2018. The Odoo work goes back further than that, and one of the clients on our case studies page was a client before the firm existed.
Nine implementations have gone live since. Around forty projects and enhancements have come out of that work, across six industries.
Not all of it started as an implementation. Two of the case studies below picked up systems somebody else had already built.
Grocery retail. Food manufacturing. Custom glass tile. A precious-metals dealer whose CRM had stopped working.
Four of those are written up, with the numbers left in.
Read the case studies
Mark Robinson
Founder
The Founder
How the firm started
I'm Mark Robinson. I started Canzonia in 2018, after years of doing Odoo inside other people's firms.
Before that I was the embedded senior developer on a couple of multi-year programs. On one I led the development team inside an implementation partner. On the other I mentored the client's own developer, so the capability stayed in their building after I left.
I like this work. Odoo is a good system, and most of the value in it sits in the part nobody sells you, which is the weeks you spend understanding how a business already runs before you configure anything.
What I do on a project hasn't changed since then. I scope it, and I stay on it through go-live.
How We Staff
Senior on the work, sized to the program
That one thing doesn't flex. Everything else about how a project is staffed does.
On the larger programs that has meant running a development team as well as building. On the grocery rollout it was the implementation partner's developers, with code review on everything that went in. On the manufacturing program it was the client's own developer, mentored through it.
We staff to the size of the program, and we bring in senior Odoo developers we've worked with before when a program needs more hands.
If We're Not Around
Your system doesn't depend on us
Everything we build ships as standard Odoo addons, committed to your repository from the first week. Your team is trained on it, and the documentation describes what is actually running.
The reason we build that way is the question you're already asking.
If we went quiet tomorrow, another Odoo firm could pick your system up and carry on with it. There's nothing in there that only we understand, no fork, and no layer of ours sitting between you and Odoo.
That's the test we build against, and it's worth asking any firm you're talking to how they'd pass it.
How We Work
Four things we do on every project
We map how you work first
On the grocery rollout we mapped the existing inventory and procurement process before building anything, then rebuilt what already worked instead of replacing it.
We cut over in stages
Stores went live about two business days apart across a two-week window. At the manufacturer, Odoo ran alongside the plant's spreadsheets until the team was ready to retire them.
We hold scope
On two engagements the client's accounting system stayed exactly where it was, deliberately out of scope. Not everything has to move at once.
We prove the data moved
Migrated records get counted against the source, spot-checked, and signed off by you before anyone calls it done.
Let's Talk
If you want to know whether we're the right size for your project, ask.
An intro call runs about 30 minutes and costs nothing. Bring what you're running on now and whatever you're worried about.
Book a Free Intro Call