The first month is a review of the system you already run. Nothing changes until you have approved the written risk list and the order of the fixes.
Most plans start with a system someone else built. The review is included in the first month, and it runs in four steps.
Odoo.sh or your server, the repository, the integrations and the third-party apps.
The code, the customizations, the data model and what looks fragile.
What is broken, what is risky and what to fix first, in plain language.
We start on the highest-cost problem in your first month.
Email or Slack what is broken, what is missing and what your team keeps working around.
You get a written answer on what is a fix, what is a change and what needs its own quote, within your plan response time.
Changes go to staging first, are tested on your data, and go live only when you approve.
What changed, how to use it and what is next. Partner and Embedded plans include a call.
Every request gets a written answer inside the plan response time, so you always know which of these it is before the work starts.
Something broken on the live system. It goes to the front of the queue and comes out of the plan hours.
A new field, screen or report. It is scoped in writing first, then built inside the plan hours if it fits.
Work larger than the plan can carry. It gets its own written fixed price, for plan clients only.
Every change is tested on a staging copy of your system, with your data. You see what changed before it reaches the live system. Nothing goes live until you approve it.
The code is committed to your repository, with notes for every change. If you ever leave, you leave with the code, the notes and the history.
One request list holds the work. Hours are logged against it, and your monthly summary shows what was done, what is open and what is next.
Partner and Embedded plans include a call: monthly on Partner, weekly on Embedded. Care keeps to a monthly written summary.
Pick a plan, or book a call and we will size it together.