TechNext
step 4 of 4

Support: the same team, after go-live.

Go-live is where questions start. We stay on for fixes, month-end help, upgrades and the small changes a growing business keeps needing — with the people who configured your system in the first place, not a call centre meeting it for the first time.

what's covered

The help a live system needs.

Fixes

Something doesn't post, a report is wrong, a user is stuck — a named channel and a response target agreed in your plan.

Month-end help

Reconciliations, tax returns and closing entries, worked alongside your finance team for the first cycles until it is routine.

Version upgrades

Odoo releases new major versions on a regular cadence. We test, migrate your customisations and upgrade on a schedule you choose.

Small changes

A new report, an extra field, an approval step, another warehouse — handled within the plan, not treated as a fresh project.

New requests

Larger additions — a new app, a new integration — scoped and quoted first, then built when you are ready.

Health checks

Periodic review of performance, access rights and housekeeping, so problems are caught before users feel them.

how a plan works

One channel, tracked, reviewed.

1

Setup review

Confirm the apps, users and customisations we support, and agree your response targets.

2

Single channel

One place to raise requests, each tracked as a ticket from open to done.

3

Triage & fix

We reproduce on a staging database, fix, and release once you have checked it.

4

Review & plan

A regular summary of what was done and what's pending, including the upgrade path.

what you get

A plan sized to your team.

Plans are based on the number of users and apps in use. Effort rolls into fixes, changes and upgrade work; anything larger gets its own scope and quotation first.

  • A named team who already know your setup
  • A single channel with tracked tickets
  • Response targets agreed in your plan
  • Bug fixes and issue investigation
  • Month-end and closing support
  • Version upgrade testing and migration
  • Small changes handled within the plan
  • New requests scoped and quoted before build
  • A staging database for testing before go-live
  • A regular summary of work done and pending
  • Support for systems we didn't implement, after a review
  • Resize or cancel with agreed notice
common questions

Support, answered.

Do you support Odoo you didn't build?

Yes. A short review of the current setup comes first, so we know what we are taking on before we commit to a plan.

What are your response times?

Response targets are agreed in your plan and tracked against every ticket. We keep them realistic to your setup rather than quoting a headline number that doesn't fit.

How do we raise requests?

Through a single channel, where each request becomes a tracked ticket from open to done — so nothing gets lost in an inbox.

Will an upgrade break our customisations?

We test on a staging database, migrate your customisations and upgrade on a schedule you choose — never a forced cut-over.

Where is the support team based?

At our Singapore HQ, serving clients globally.

How is support priced?

On quotation, based on the number of users and apps in use — request a quotation.

next step

Keep the system healthy after go-live.

Already on Odoo, or about to be? Tell us the apps and team size and we will size a support plan.