How our go-live guarantee works

What we promise

Foundation and Growth implementations have a go-live date written into the project plan you sign at kickoff. If we miss that date for reasons on our side, two things happen automatically: we continue working at no additional charge until the scope in the plan is live, and we extend the hypercare period that follows go-live by the number of weeks we were late.

Enterprise projects are delivered in phases, each with its own dated plan; the same remedy applies to each phase. The Launch package and hourly engagements are not covered.

When the timeline starts

The timeline starts on the kickoff date in the plan. Kickoff follows three things: the signed proposal, receipt of the deposit, and delivery of the access and data listed in the plan's before-kickoff checklist (administrator access to your current systems, the data exports named in the plan, and the names of your decision-maker and process owners).

Discovery work before kickoff does not count toward the timeline. If the checklist is delivered late, the kickoff date and the go-live date move by the same number of business days.

Which projects qualify for 8 to 12 weeks

Foundation: one legal entity, one source system for data migration, standard Odoo modules configured without custom code, up to 25 users. Growth: one legal entity (multi-currency is fine), up to five light customisations, one integration from the plan (Shopify, Stripe, Avalara or one EDI partner), migration from more than one source, up to 75 users.

On both, a client team that meets with us weekly and signs off each milestone within five business days of receiving it. Projects outside these limits still get a written, dated plan and the same remedy; the timeline is simply longer, and the plan says so.

What "go live" means

Your team is processing real transactions in Odoo for every process in the plan's scope; the migrated master data and opening balances have been reconciled against your source system and signed off by your decision-maker; and the previous system is no longer the system of record for those processes.

Go-live does not require that every user has completed every training session, or that optional reports outside the scope are built. Those belong to hypercare and to change orders.

What we need from you

A named decision-maker with authority to approve scope and sign off milestones. Data exports from your current systems in the agreed format by the dates in the plan. Users available for the two testing rounds and the training sessions. Answers to open questions within two business days.

When one of these slips, we say so in that week's written report, with the effect on the date. The go-live date moves by the number of business days lost, and the guarantee applies to the moved date.

Data migration assumptions

We migrate master data (customers, vendors, products, chart of accounts, employees where scoped), open items (open invoices, bills, orders, stock on hand) and opening balances from the source systems named in the plan. Historical transactions from the current and the previous fiscal year are included; older history is migrated only when the plan scopes it.

We run two rehearsal loads before cutover and report data-quality issues after the first one. Cleaning source data is your responsibility unless the plan includes a data-cleansing block; where cleaning is late, the date moves as described above.

Integrations and custom development

Integrations are limited to those named in the plan. Each third-party system must provide the documented API access, sandbox and credentials by the date in the plan. Custom development is limited to the specifications signed off in scope; a new requirement is a change order, never a silent addition.

Scope changes and third-party delays

A change order states its price and its effect on the go-live date before the work starts. The guarantee then applies to the revised date. Delays caused by a third party (a payment processor, an EDI network, a hosting provider, a previous vendor withholding data, or Odoo itself) pause the clock for the duration of the delay, and the weekly report records the pause.

If we miss the date

You will know before it happens. The weekly written report flags a date at risk as soon as we see the risk, together with the recovery plan. If go-live still slips for reasons on our side, the two remedies in the first section apply automatically. You do not need to claim them, and there is no cap on the additional weeks we work to reach the agreed scope.

What hypercare includes

Hypercare starts on the go-live date and runs 30 days on Foundation, 90 days on Growth and 180 days on Enterprise. It covers defects in configured scope, user questions on in-scope processes, month-end support for the first close, and stabilisation fixes. It does not cover new features, new integrations, additional users beyond the plan or training beyond the sessions in the plan; those are quoted separately or covered by a support plan.

Exclusions

Delays caused by late data or access, an unavailable decision-maker, scope added without a change order, third-party outages or changes, force majeure, or a change to Odoo's own release schedule. Projects paused at the client's request for more than ten business days restart with a re-baselined plan. The Launch package ($4,950) and hourly engagements are not covered.