FOR ODOO PARTNERS
Extend your Odoo delivery team without adding permanent headcount.
RNX gives established Odoo partners extra functional, technical and delivery capacity when the work needs it. You keep the customer, the brand and the process. We do agreed work behind the scenes, to your standards.
Discuss Delivery CapacitySee What We Can Support
We work behind the scenes, inside your process. Not in front of your customer.
THE CAPACITY QUESTION
You win the project. Then the capacity question starts.
Most Odoo partners know this moment. The deal is signed, and the plan meets the team you already have.
- Your functional consultants are committed to other projects.
- Your developers are stretched across builds and fixes.
- Testing gets squeezed towards the end, and the customer's testers are busy with month-end.
- Documentation turns into a backlog.
- Hypercare runs longer than the plan allowed for.
- Support tickets compete with implementation work.
- The need is real, but too short or uneven to justify another permanent hire.
You don't always need another permanent employee. Sometimes you need the right delivery capacity, at the right time, for a defined piece of work.
WHERE WE ADD CAPACITY
Where we add capacity.
We focus on the parts of delivery that most often run short, and where our experience is deepest: testing, upgrades, go-live and support. We would rather do a few things well than claim to do everything.
Testing & UAT
- Test plans with a named functional and technical owner for every test area
- UAT packs your customer's users can complete, planned around their calendar, including month-end
- Defect logging and tracking in your tool
- UAT sign-off documents
Upgrade readiness
- Regression testing for version upgrades, including V17 to V19
- Feature-parity checks, so nothing the customer used yesterday disappears
- A register of entity-specific configuration in multi-company setups
- Lessons from past migrations turned into go-live gates
Go-live & hypercare
- Readiness sign-off per team and per entity
- Go-live verification checklists
- First-occurrence monitoring of each live transaction type
- Hypercare that ends on exit criteria, not a fixed date
Support capacity, under your brand
- Tier-1 and tier-2 support in your ticketing system
- Triage before a ticket reaches a developer: configuration, data, training or a real defect
- Incident and problem handling, with root-cause analysis that proposes prevention
- Help with priority and SLA rules and backlog clean-up
Documentation & knowledge
- SOPs, user guides, UAT handover packs and training material
- Resolution notes and knowledge-base articles, labelled with how confident we are in the cause
- All in your templates and under your brand
Functional & technical tasks
Configuration support, workflow validation and defined development tasks, delivered by RNX's functional and technical specialists into your repository and review process. Scoped one assignment at a time. We confirm who will do the work, and their experience, before you commit.
HOW THE PARTNERSHIP WORKS
How it works.
You win the work
The customer relationship and the contract are yours.
You define the scope
You decide which pieces RNX takes on and how they are handed over.
RNX provides capacity
Named roles, agreed hours, agreed outputs.
Inside your tools
Your project tool, ticketing system, repository and templates.
You face the customer
The customer sees one team: yours.
RNX sits inside your delivery team. Never between you and your customer.
OUR MOST IMPORTANT PROMISE
Your customer. Your brand. Your process. Your delivery standards.
RNX supports the work behind the scenes.
You have spent years building your customer relationships. We understand that, and we are not here to compete for them. RNX is designed to work as an extension of your delivery team. We work within your processes, tools, documentation standards and communication model. You keep ownership of the customer relationship.
✓ No direct customer solicitation
We do not approach your customers, during an engagement and for 12 months after it ends.
✓ Your communication channels
We speak to your customer only if you ask us to, and only in the way you set up.
✓ NDA before work starts
We are happy to sign your NDA, or provide ours.
✓ Partner-defined access
We use only the systems and data you give us access to.
✓ Partner-defined scope
We do the work you agree with us. Nothing is added without you.
✓ Partner-defined standards
Your templates, your naming, your quality checks.
WORKING MODELS
Three ways to engage.
Defined assignment
One specific piece of work with a clear output. For example: a UAT pack, a regression test cycle for an upgrade, a go-live readiness checklist, a documentation set, a support backlog clean-up or a defined development task.
Project capacity
RNX supports one of your projects for an agreed period, in agreed roles. Useful when a project needs more hands than your team has free, for a few weeks or months.
Ongoing delivery capacity
A recurring monthly block of capacity, used as your pipeline needs it: testing, documentation, functional and technical tasks, or white-label tier-1 and tier-2 support for your customers. Agreed hours, one named contact, a weekly update.
Every engagement is scoped before it starts. We agree roles, hours and outputs together. We don't promise headcount we haven't agreed with you.
YOUR TOOLS, OUR DELIVERY
Your brand. Your process. Your tools.
We don't ask you to change how you run projects. We adapt to the way your team already works.
- Your project management tool, for tasks, plans and status.
- Your ticketing system, for support queues and defects.
- Your documentation platform and templates, so every document looks like yours.
- Your communication channels, including your internal chat and email.
- Your code repository and review process, for any development work.
We agree the tools, access and handover points before work starts, so your team knows exactly where RNX work will appear.
WORKING ACROSS TIME ZONES
An India-based team, working to your day.
RNX is based in India. For UK and US partners, that means part of the delivery day happens while your team is offline. Used well, that is extra working time on your project, not a gap.
- Real overlap with the UK. Our afternoon is your morning, so we share several working hours every day.
- Planned overlap with the US. Overlap is short, so we agree a fixed daily or weekly window, usually early in your morning.
- Structured handovers. Every working day ends with a written note: what was done, what is blocked, what needs your decision.
- Documented work. Decisions, test results and changes are written down in your tools.
- Remote by design. We are used to working with teams we don't sit next to.
We don't offer 24/7 cover. We offer a predictable working pattern that we agree with you in advance.
WHY RNX
ERP delivery is not just configuration or code.
Successful ERP delivery is business process, people, technology and execution working together. Our background is in running Odoo for the business every day, through upgrades, go-lives and thousands of support tickets. That shows in how we test, document and support.
- We know what happens after go-live. We run day-to-day Odoo support across several business entities on V17 and V19, from triage to root cause.
- We test from experience of what breaks. Version upgrades change standard behaviour you never customised. Multi-company setups hide entity-specific configuration. We plan tests for both.
- We have seen partner-led delivery from the customer's side. We know what customers notice: missed features after an upgrade, testers pulled into month-end, a go-live with no one available to fix things.
- Operational discipline. Clear priority and SLA rules, incident and problem handling, change control and configuration tracking.
- We work well with finance teams. ERP changes that affect the books get checked before they are built.
- Standard Odoo first. Customisation only where frequency and value justify it, and never where the next upgrade will replace it.
START SMALL
Start with a defined piece of work.
A new partner relationship doesn't need a big commitment. Give us one well-defined piece of work, see how we work, and decide from there.
- A UAT pack for an upcoming go-live
- A regression test cycle for a version upgrade
- A feature-parity check before an upgrade
- A go-live readiness and first-occurrence checklist
- A documentation set: SOPs, user guides or a UAT handover pack
- A support backlog clean-up
- Tier-1 and tier-2 support cover for a busy month
- One defined development task
PARTNER FAQ
Questions partners ask us.
Do you work directly with our customers?
Only if you want us to. Our preferred model is to work as part of your delivery team, with you as the customer-facing partner. If a task needs customer contact, such as a UAT session, we agree beforehand how it happens, who leads it and how we are introduced.
Can you work under our brand?
Yes. We are comfortable working behind the scenes. Documents, test packs and reports can be produced in your templates and under your name. How RNX is presented to your customer is your decision, and we agree it in writing before work starts.
Can you use our tools and processes?
Yes, where it is technically and commercially practical. We work in your project tool, ticketing system, documentation platform, communication channels and code repository. We agree access and handover points at the start.
Can we start with a small assignment?
Yes, and we recommend it. A defined piece of work, such as a UAT pack, a regression test cycle or a documentation set, is the easiest way to see how we work before committing to more.
Do you provide both functional and technical capability?
Yes, and we are clear about where our depth is. Our strongest experience is in testing, upgrades, go-live readiness, documentation and support operations. Configuration work and development are done by RNX's functional and technical specialists. Before you commit, we tell you who would do your work and share their relevant experience under NDA.
Can you support UK and US working hours?
Partly, and we are clear about how. We are based in India (IST, UTC+5:30). We share several working hours each day with the UK. Overlap with US teams is shorter, so we agree a fixed window, usually early in your morning. We don't offer 24/7 cover.
Are you an official Odoo partner?
No. RNX Business Systems is an independent consultancy. We are not an Odoo partner and are not affiliated with Odoo S.A. That is part of why we work well behind partners: we are not competing for Odoo's partner channel or your customers.
How do you handle confidentiality?
We sign an NDA before any work starts, yours or ours. We only access the systems and data you give us. Customer data stays in your environment wherever possible, and we agree data-handling terms with you before the engagement begins.
How are engagements structured?
Three ways: a defined assignment with a clear output, project capacity for an agreed period, or an ongoing monthly block of capacity. Every engagement is scoped first: roles, hours, outputs, tools and reporting. You get one named contact and a weekly update.
Will you approach our customers later?
No. We do not solicit your customers during an engagement or for 12 months after it ends. We are happy to put that in writing as part of the agreement.
Have a delivery gap coming up?
Tell us what you need help with. It could be a short-term functional requirement, a testing backlog, a development task or extra project capacity. We'll start with the requirement and work out together whether RNX is a fit.
Discuss Delivery CapacityEmail info@r-nx.com
RNX Business Systems is an independent consultancy. We are not an Odoo partner and are not affiliated with Odoo S.A. Odoo is a trademark of Odoo S.A.