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
| Clause | What to write down | What happens if you skip it |
|---|---|---|
| Scope | A list of tasks, each with an outcome | Arguments over what the price covered |
| Exclusions | Licence, services, migration, development | Surprise invoices halfway through |
| Timeline | Stage dates and what the client provides for each | Delays nobody can explain |
| Acceptance | Test scenarios and a deadline for feedback | A project that never closes |
| Access and data | Who owns the portal, how access is granted and revoked | A portal that depends on the partner |
| Change requests | How new work is estimated and at what rate | Extra work with no estimate or sign-off |
| Support | Hours package, response time, how requests are logged | Nobody to fix things after go-live |
| Payment | Currency, company details, schedule, taxes | Late 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.
