Your sales, warehouse and accounting are running on three different systems. They shouldn't be.

It's true that a large share of ERP projects fail — and we talk about it openly because we've seen firsthand what causes it. It's almost never the software. It's generic configurations that don't match real workflows, partners who disappear after go-live, and projects where no one is accountable for adoption.

Our model is structurally different: we map your actual processes before configuring anything, we stay through go-live and the first 90 days, and every project has a named consultant responsible from day one to closure. We can't promise perfection — no one honestly can. What we can promise is a documented method, fixed milestones, and a direct line to the person running your project.

In over 20 years, we've never walked away from a project.

We don't publish fixed prices because every implementation is different — a 20-person manufacturer has different needs from a 60-person distributor. What we can tell you is how our pricing works.

Projects are quoted as fixed-fee engagements with a detailed scope document. You know the total investment before signing anything. No hourly overruns, no surprise "customisation fees", no modules that suddenly cost extra.

What's not included by default: Odoo Enterprise licences (billed directly by Odoo itself if you choose Enterprise), third-party integrations outside our standard stack, and support beyond the 90-day hypercare period — available as a separate retainer.

The starting point is always the free process audit, which gives us enough context to send you a ballpark range before any formal proposal.

No — designing around your operational continuity is one of our core constraints, not an afterthought.

During the configuration phase (typically 4–8 weeks) your team keeps working in the current systems. The new Odoo environment is built and tested in parallel. Your people are involved only in scheduled sessions — typically 2–3 hours a week — planned around your operational calendar.

Go-live is planned for a low-traffic moment, and we run the first week with both systems active — so there's always a fallback.

This is the most honest question we get — and the one that tells us we're talking to someone who's actually thought this through.

Software resistance is almost never about the software. It's about people being asked to change how they work without understanding why, without being involved, and without training that matches how they actually use the system day to day.

Our training is role-specific and happens on your configured system, not a demo. Your warehouse team learns the warehouse; your sales team learns the sales flow. And we involve key users from each department during configuration — to give them ownership of the outcome.

People don't resist systems they helped build.

Deliberately, no — this is a design principle of every project we run, not a nice-to-have.

Everything we build is documented. Every custom module has commented code and a written specification; every configuration choice is logged with the reasoning behind it. At the end you receive a full technical handover package.

We also train at least one internal "Odoo owner" on your team — someone who can handle routine changes, user management and basic troubleshooting without calling us. For bigger developments you can work with us, another Odoo partner, or an internal developer.

Our business model is built on referrals, not on recurring dependency.

There's no perfect moment — but there are better and worse ones. The worst time is during your peak season, a major restructuring, or right after losing a key person in operations. Almost everything else is workable.

In our experience, companies that wait for the "right moment" usually wait two or three years — and spend them accumulating exactly the inefficiencies they wanted to fix. Every quarter without a unified system is data that's harder to migrate and habits that are harder to change.

The free process audit commits you to nothing — it just gives you a realistic picture (scope, timeline, investment range) to decide when to proceed.