The questions we actually get asked.

It depends on module count and how much of your process is standard, which is why we scope in writing before quoting. What we can tell you early is the shape: a phase-one implementation for a mid-market team is typically five modules, and we will give you an indicative range in the discovery call rather than making you wait for a proposal.

Because a number without a scope is a guess, and you would be comparing our guess against someone else's. Every Success Pack and every project is quoted against a written scope, so the figure you get is one we can hold to.

That is what the Success Packs are for — blocks of consultant hours with a named consultant, starting at a four-hour First Look. No project wrapper around a day's work.

Two to four months for a mid-market phase one, from signed scope to go-live. Migrations carrying three years of history run twelve to eighteen weeks. Anyone quoting four weeks is quoting a data copy, not an implementation.

The next stage does not start, and you hear about it in the week it happens rather than at go-live. A problem raised in week two is a decision; the same problem at cutover is a crisis.

Yes. The consultant in the discovery call is the consultant at go-live, and the migration engineer stays on the account through ninety days of hypercare.

Colombo is GMT+5:30 and never shifts for daylight saving. Every project has one named consultant working inside your overlap window and a written escalation path with a four-hour first response. The exact daily overlap for your market is on the global delivery page.

You do. Custom modules go into your repository, version-tagged, with the tests that prove they work. The runbook, the mapping document and the SOPs are deliverables, not internal notes.

Then the handover pack is what makes that possible, which is why it is written as we go rather than assembled at the end. Standard Odoo and documented configuration are the things that keep you free to leave.

A named consultant, a response SLA and an hour bank — not a ticket queue and not a handover to a team who never built it.

Yes, twelve months from purchase, with a reminder at nine. We would rather you spent them than lost them, and saying so plainly seems better than burying it.

That is most of the job. Every line of custom code is a maintenance cost, and we will show you the three-year figure before you approve it — including when the answer is that standard Odoo already does it.