In June 2026, Grey Space Computing moved from Odoo Learning Partner to official Odoo Ready Partner status. It's a milestone we'd been working toward since April 2026, and it landed alongside something just as significant: going live on a 170-user Odoo rollout for a client in Saudi Arabia — one of the larger multi-site implementations we've taken on to date.
We wanted to write this down properly rather than just drop a badge in the footer, because the two things — the partner status and the KSA go-live — aren't really separate stories. One is the reason the other happened.
Learning Partner
users onboarded in KSA
Ready Partner
What "Ready Partner" actually means
Odoo's partner tiers aren't just badges you apply for — each one reflects a combination of certified implementations, delivered projects, and outcomes Odoo can verify directly with the client. Moving from Learning to Ready isn't automatic; it means enough real, successful go-lives that Odoo is comfortable putting its name next to ours in front of new customers.
For us, that meant treating every implementation in between as if it were the one that mattered most — because in a very literal sense, each one was building toward this.
The rollout that got us here
Ready Partner status isn't awarded for potential — it's awarded for delivery. The project that tipped the scales was a 170-user implementation across multiple business units in Saudi Arabia, run on a timeline that didn't leave much room for a rocky go-live.
Multi-site rollouts fail in fairly predictable ways: data migration that looks clean in staging and isn't, modules that behave differently once real transaction volume hits them, and training that happens too early or too late relative to go-live. We planned around all three — staged data migration with reconciliation checkpoints, a training cadence tied to each site's go-live date rather than a single company-wide session, and every release run through our in-house QA engine before it reached a single end user.
Ready Partner isn't the finish line — it's proof the fundamentals hold up under a rollout that size.
That last part is worth calling out on its own. The automated regression testing we run internally — the same approach we've since written up on how we test — caught a number of issues before go-live day that would otherwise have surfaced as support tickets from real users. That's exactly the outcome it's built for.
What changes for clients
Practically, three things: official recognition Odoo will confirm if you ask them directly, access to Odoo's partner resources and escalation paths when we need them, and continued investment in the process that got us here rather than a reason to relax it. The QA engine stays on every implementation, not just the large ones.
What's next
Ready Partner was the milestone for the first half of 2026. The next one on our roadmap is Silver Partner — you can follow where that stands on our partner journey timeline on the homepage. We'll write about that one too, when it's real and not just a plan.
