The short answer: get it in writing that everything built for the website is registered to your company or handed over to it: the domain, the hosting account with full control-panel access, administrator rights on the CMS, the source code and theme, database exports, backups, and the analytics and ad accounts. Ask for the words “no vendor lock-in” in the contract, with your right to move, copy or migrate the site at any time. The agency can stay on as a service provider; the keys stay with you.
In 40 seconds
Related: Web Design Services — or see every industry we serve in B2B marketing.
- Insisting on ownership before you sign is not being difficult; on a hundred-page bilingual build it is the most important clause.
- The list is short: domain and hosting in the company’s name, CMS admin rights, code and backups delivered, content and 3D assets licensed to you, analytics and ad accounts owned by you with the agency as a user.
- Then the large-site specifics: a page plan, native writing in both languages, CMS roles, a performance budget and acceptance criteria.
- Whatever stays with the agency should be a service you can stop, never a hostage you have to ransom.
Why the documentation and handover clause comes before the design
An engineering and contracting company in Oman commissioned a bilingual website of roughly a hundred pages, with a content-management system and an interactive 3D experience, delivered as a first phase with optional later phases. Before signing, the general manager asked one question in his own words: “We are commissioning a large two-language website of about a hundred pages: what must we get in writing so we are never held hostage by the company that built it?” He got written confirmation: an admin panel his team controls independently; full CMS administrator access at final handover; full hosting control-panel access covering files, database, backups and environment; “no vendor lock-in” in those words; and the right to move, copy or migrate at any time.
He was right. A site of that size takes months and a serious budget, and once live it is where consultants and procurement teams check you before a tender. If the domain is registered to someone at the agency, the hosting sits inside the agency’s own account, or your login is editor-only, the handover exists on paper only. You find out the day you change suppliers or lose the person who knew the passwords.
The clause does not signal distrust. It makes the relationship rest on service quality, not on how hard it is to leave.
The ownership checklist: what to get in writing
Attach these as a contract schedule, one line each:
- Domain in the company’s name: registered to your company with an email on your own domain, not to an agency employee.
- Hosting account in the company’s name: full control-panel access to files, databases, backups, environment settings and email.
- CMS administrator rights: enough to create, suspend and assign roles to users without asking permission.
- Source code, theme and custom code: delivered in full, in a repository or archive you keep.
- Database export on request: within a stated time, such as two working days, with no hidden fees.
- Downloadable backups: scheduled, and stored where you can reach them, not only on the agency’s server.
- Content, images and 3D assets: copy, photography and models are permanently licensed to your company and listed in the handover file.
- Analytics, Search Console, Tag Manager and ad accounts: created under your company, with the agency as a user you can remove.
- Documentation and handover: a CMS guide, a recorded training session and a register of every account.
- Exit terms: a notice period, transfer support, and nothing withheld over a dispute.
What you should own, what can stay a service, and what is a red flag
Maintenance, support and website hosting and security are normal paid services. The test is whether you can stop the service without losing the asset:
| Item | What you should own | What can stay with the agency as a service | Red flag |
|---|---|---|---|
| Domain | Registered for your company and documented | Renewals and DNS settings | Registered to an employee or the agency |
| Hosting | The account and full control panel | Monitoring, updates, security | “It’s on our server, you don’t need a login” |
| CMS | Admin rights, including creating users | Support and new page builds | Editor-only login, or a closed platform that cannot move |
| Code and theme | A complete copy you may use and modify | Later phases | A licence “for use on our hosting only” |
| Content and 3D assets | Ownership or a perpetual licence | New content production | Assets you may not use outside the current site |
| Analytics and ads | Accounts created for your company, agency as user | Management and reporting | Accounts inside the agency’s login, so the data leaves with them |
| Backups | Copies you download and keep | Scheduling and restore tests | Backups only on the agency’s server |
| Support | Documentation another team can work from | An annual agreement with clear scope | Support you cannot cancel without the site going down |
What changes when the site has a hundred pages in two languages
Ownership protects your exit; success is decided before the first design. For large company website design, six points belong in the written scope:
A page plan before design
Ask for a sitemap organised by service (design, construction, maintenance), by sector (oil and gas, infrastructure, commercial buildings) and by reference project, with each page’s purpose and its visitor’s question. Design follows the plan, not the reverse.
Two languages written natively
The Arabic page for the project owner and the English page for the international consultant are written for their readers and search terms, then linked so Google understands the pair.
CMS roles that protect the layout
Ask for an editor who adds a project from a ready template without breaking the design, a reviewer who approves, and an administrator who controls everything.
A performance budget
Set a mobile load-time limit per page type, and load 3D only on demand.
Phase one versus options
Name what is in phase one and price each later option in writing now, so additions do not become new negotiations.
Acceptance criteria
Every page live in both languages, forms reaching the right inbox, speed within budget, accounts transferred, first backup in your hands.
As an illustrative range rather than a quote, large bilingual corporate builds in Oman typically run from about OMR 3,000 to OMR 20,000 depending on scope, page count and interactivity, and phase one usually takes several months. For specifications and gated documents, see RFQ-ready B2B websites with confidential datasheets.
When a 3D experience earns its place, and when it is decoration
In B2B, interactive 3D earns its budget when it explains what photographs cannot: a walk-through of a plant you delivered, an infrastructure project whose stages a consultant can follow, or an equipment showroom where a buyer turns a large unit around before requesting a quotation. There it replaces a meeting.
It is decoration when it is a rotating homepage model that carries no information and slows mobile pages. The test: if you cannot name the question it answers, it is decoration. If you go ahead, own the original model files, provide a static fallback for weaker devices, and load it on demand.
Six questions before you sign the website contract
- In whose name will the domain and hosting be registered, and when do we get control-panel access?
- Will we have full CMS administrator rights, including creating users ourselves?
- Will you deliver a complete copy of the code, the theme and the 3D model files?
- Will you write “no vendor lock-in” and our right to migrate at any time into the contract?
- Exactly what is in phase one, and what does each later option cost?
- If we move to another provider, what is the notice period and who supports the transfer?
When we’re the right fit — and when we’re not
What this client asked for is our default: VadeCom books domains and hosting in the client’s own name, as a hosting partner since 2007, and hands over admin rights, code and database exports; that is the standard worth demanding from any provider. We fit an engineering, contracting, industrial or B2B services company in Oman, the Gulf or Egypt that wants a bilingual website built on a page plan and measured by qualified inquiries. A B2B company website starts from $600 (about 30,000 EGP or roughly OMR 230), larger builds are priced on their written scope, and website hosting and security start from $160 per year. We are not the right fit if the goal is the cheapest site without a page plan, or 3D purely for decoration.
Related reading
- Corporate website design for B2B companies
- B2B marketing and website design in Oman
- B2B websites for RFQs, specifications and confidential datasheets
- Renewing an annual marketing retainer: what to review
- VadeCom — B2B marketing agency, Egypt and the Gulf
FAQ
Am I entitled to the source code of my company website?
Yes, if the site was built for your company and paid for by it. Write delivery of the code, theme and custom modules into the contract, with the right to use, modify and move them. Licensed third-party software is the reasonable exception, listed by name.
What is the difference between admin and editor access in a CMS?
An editor can only add and change content. An administrator can create and suspend users, change settings and manage modules. Without admin rights, the site is still in someone else’s hands.
Does the hosting have to stay with the agency that built the site?
No. The agency can manage hosting as a service, provided the account is registered for your company, documented, and your team holds full control-panel access.
How long does a hundred-page bilingual website take?
Phase one usually takes several months across the page plan, native writing in both languages, design and review. Content approval inside your company is often the slowest part, so name one reviewer early.
Does a contracting company need a 3D experience on its website?
Not necessarily, but it helps when showing a project or facility that photographs cannot explain. Load it on demand, keep the original model files, and never let it slow the core service pages.
