Journal · Bitrix24

Bitrix24 implementation contract: what to include

CRM projects usually go wrong not because of bad setup but because the contract describes the scope in one line. Here are the clauses worth checking before you sign.

A Bitrix24 implementation contract should cover eight things: the list of work, what is excluded, stage deadlines (a standard launch with us takes from 14 days), acceptance, who owns the portal and access, how scope changes are handled, support and payment. MakeBiz Technologies contracts through MakeBiz Technologies FZE LLC, invoices in AED, fixes the quote before work starts and offers post-launch support from AED 1,250 for 5 hours a month.

MakeBiz Technologies · 11 November 2026 · 7 min read

Scope is written as a list, not as the word "implementation"

A line that says "Bitrix24 CRM implementation" in the contract fixes nothing. A month in, the client assumes the accounting integration was included and the partner assumes it was not. So write the scope as a list of tasks with outcomes: a sales pipeline with these stages, roles and permissions for these groups, a WhatsApp channel connected, an invoice template with 5% VAT created.

The second list matters just as much: what the contract does not cover. Typically that is the Bitrix24 licence, paid third-party services, data migration, complex integrations and custom development. If an item appears in neither list, you will almost certainly argue about it later. Our standard setup is broken down in the guide to turnkey Bitrix24 implementation, and it works well as a starting point for your list.

This is a buyer's checklist, not legal advice: have your lawyer review the contract wording.

Eight clauses prevent most disputes

ClauseWhat to write downWhat happens if you skip it
ScopeA list of tasks, each with an outcomeArguments over what the price covered
ExclusionsLicence, services, migration, developmentSurprise invoices halfway through
TimelineStage dates and what the client provides for eachDelays nobody can explain
AcceptanceTest scenarios and a deadline for feedbackA project that never closes
Access and dataWho owns the portal, how access is granted and revokedA portal that depends on the partner
Change requestsHow new work is estimated and at what rateExtra work with no estimate or sign-off
SupportHours package, response time, how requests are loggedNobody to fix things after go-live
PaymentCurrency, company details, schedule, taxesLate payments and exchange rate surprises

The table does not replace a contract, but it is a quick pass before you sign. If the draft says nothing on two or three of these rows, ask the partner about them. We published a similar checklist for AI projects in our news on questions to ask a contractor before signing.

Deadlines are tied to stages and to client decisions

A standard Bitrix24 launch with us takes from 14 days. In the contract, though, a single end date is less useful than stage dates: discovery, setup, training, handover. Next to each stage, note what the company has to provide: an owner on your side, the list of users, signed-off pipeline stages, a sample invoice, access to the portal.

That way both sides can see why a date moved. If signing off the stages took a week, setup starts a week later, and that is not the partner's breach. What makes UAE projects longer (multiple entities, accounting, migration, channels) is covered in our news on CRM implementation timelines.

Get our draft contract before the call

List of work, stages, acceptance and a quote in AED. Standard setup from AED 10,000, launch from 14 days

Request the contract

Acceptance runs on scenarios, not on impressions

"The system is set up" cannot be tested. Scenarios agreed in advance can. For example:

  1. a new WhatsApp message creates a lead and reaches the right rep
  2. a deal moves through every pipeline stage, and required fields stop anyone skipping a step
  3. an invoice in AED with 5% VAT goes out from the deal using your template
  4. a rep sees only their own deals, the manager sees the whole team
  5. automation rules create tasks and send notifications at the right stages

Add a feedback window, for example a few business days after handover, and one rule: a defect is something that does not work according to an agreed scenario. A new wish ("could we also get a report by emirate?") is a change request and is estimated separately. That split is what stops acceptance from dragging on forever.

The portal, access and data stay with your company

The Bitrix24 portal and licence should be registered to your company, and the portal administrator should be one of your employees. The partner works under a separate user account that you can switch off at any time. Put it in writing:

  • the portal, service accounts and data belong to the client
  • the partner gets access for the duration of the work, and it is revoked at the end
  • settings, templates and integration notes are handed over with the system

At MakeBiz Technologies this is a standard term: access and data stay with the client. How licences are issued and what plans exist is on the Bitrix24 licences page.

Change requests and support get their own terms

Every project produces tasks that were not in the quote. A good contract says how to handle them: the partner gives an estimate in hours before starting, the client confirms in writing, and the work is billed at the agreed rate. With us, work beyond the standard scope is AED 200 an hour, see Bitrix24 development.

Post-launch support is easier to manage as a separate agreement or annex covering the hours package, how requests are submitted and the response time. Our packages are 5 hours for AED 1,250 a month, 10 hours for AED 2,300 and 20 hours for AED 4,200, with extra hours at AED 250. The scope is on the Bitrix24 support page.

Payment in AED and the parties' details

For a UAE company, the simplest set-up is a contract with a local entity and invoices in dirhams: no exchange rate maths and no cross-border payments to explain to your accountant. MakeBiz Technologies contracts through MakeBiz Technologies FZE LLC, invoices in AED and fixes the quote before work starts. Service prices exclude licences and VAT, and the UAE VAT rate is 5%. All prices are on the pricing page, and the implementation scope is on the Bitrix24 in Dubai page.

The payment schedule (one payment or by stage) is for the two sides to agree. What matters is that payment milestones match acceptance milestones, so money follows results you have checked. If you are still choosing a partner, start with our guide on how to choose a Bitrix24 partner in the UAE.

Questions and answers

Do I need a contract for a standard setup?

Yes. Even a standard package deserves a contract with the list of work and the acceptance process. It is short, but it settles what the price included.

Can I see the draft contract in advance?

Yes. You can ask MakeBiz Technologies for the draft before the first call, so your lawyer can review it while we discuss the scope.

What if we need new work during the project?

The partner estimates the task in hours, you confirm in writing, and the work is billed at the agreed rate. With us, work beyond the standard scope is AED 200 an hour.

Who owns the portal when the contract ends?

Your company owns the portal, licence, accounts and data. The partner's access is revoked when the work ends, and the configuration stays with you.

What currency is the implementation paid in?

Dirhams. The contract is with MakeBiz Technologies FZE LLC and invoices are issued in AED. Prices exclude licences and VAT.

Let us agree the scope and the contract

Tell us what needs to be set up and how many people will use the CRM. We will send the list of work, a quote in AED and a draft contract

By clicking the button you agree to the privacy policy

CallWhatsAppRequest