Short answer
When you commission a website, write a one-page brief first, ask for the proposal item by item and get ownership of the domain, hosting, code and accounts in writing. Prepare the texts and photos yourself, collect feedback in one list, run the launch checklist and take the access details at handover.
You have three proposals in front of you. One says a single line: “Corporate website, design and development.” Another lists twelve items but doesn’t say who will write the texts. The third gives a page count and never mentions the domain name. For anyone commissioning a website, the first difficulty often comes before the build: putting into writing what you want, what the proposal covers and what you will own when the work is done.
This article is for the person buying the site. We covered which pages a company site needs in what a company website needs, so we won’t repeat that here. This is about your side of the process: what to write, what to ask for, what to prepare and what to receive.
The six stages, and who does what in each, are below:
1. Write a one-page brief
A brief is not a contract. It is a short document that stops the agency asking you the same questions again and again, and it makes sure three proposals are written for the same job. Seven headings are enough:
- Purpose. What enquiry should the site bring in: a quote request, an appointment, an order, a phone call? Write it in one sentence.
- Visitors. Who comes, and what do they ask? The three questions you hear most often from customers are a good start.
- Current situation. The old site, the domain name, company email addresses and the tools you use (CRM, payment, booking).
- Draft page list. It doesn’t have to be final; the team will suggest changes.
- Three example sites. Ones you like and ones you don’t, with reasons.
- Constraints. Languages, systems to connect, a fixed launch date tied to a trade fair or campaign.
- The decision-maker. The person who collects feedback and gives approval, as a name.
2. What a proposal should list
Compare proposals by scope; the total on its own tells you little. The table below shows the items a good proposal states separately, and what happens when one is missing:
| Item | What you should see in the proposal | If it is missing |
|---|---|---|
| Pages and templates | Page list, number of templates, which are custom designs | Every extra page becomes a new negotiation |
| Text and images | Who writes, who translates, where photos come from | The schedule slips here first |
| Admin panel | What you can change yourself, whether a walkthrough is included | You wait for a developer even for a small fix |
| Integrations and languages | Forms, CRM, payment, maps; the scope of each language | Forms don’t work or languages stay half-done |
| Review rounds | Number of rounds, what a round covers, how out-of-round work is handled | An expectation of unlimited revisions, or surprise extra work |
| Measurement and speed | Analytics, form events, a speed target | Nobody knows whether the new site works |
| Ownership | Whose name the domain, hosting, code and accounts are in | You have to negotiate on the way out |
| After launch | Support scope, maintenance, who updates the content | The site is left without an owner after launch day |
| Schedule | Delivery by stage and what is expected from you | Who caused a delay becomes a dispute |
We explain why speed is a proposal item in why a fast site sells more. For a wider list of questions to put to the team before they quote, see how to choose a digital agency.
3. Who will own the domain, hosting and code
This is the shortest line in a proposal and the one that costs most later. Have four things written separately:
- Domain name. The registrant should be your company, and you should be able to log in to the registrar account. Under ICANN’s transfer policy, registrants must be able to move their domain names between registrars, and a transfer uses a unique authorisation code (AuthInfo) issued by the registrar. If the agency holds that code, a transfer depends on the agency’s goodwill. The policy covers generic extensions; for .tr, check the rules in your registrar’s documentation. We cover the extension options for a business registered in North Cyprus in our guide to North Cyprus domain names.
- Hosting. The account should be opened in the company’s name. If the agency manages it, that should be in writing, with panel access and handover available on request.
- Code and design files. For a custom-built site, whose name is the source code repository in? For a ready-made platform, whose name are the theme and plugin licences in? Write down what you will receive at handover.
- Accounts. Google states that a verified owner has the highest level of permission in Search Console. The owner role should sit in the company’s account, with the agency added as a user. The same rule applies to analytics and the tag manager.
Some teams open and manage the domain and hosting on your behalf. Who manages the account is secondary; what decides it is who the registrant is and whether the handover is in writing.
4. What you need to prepare
Text and photos are the work that decides the schedule in most projects, because the design is finished before the content is ready. Take these on from the start:
- Texts. Nobody knows your services, your story and the questions you get asked better than you. Google’s content guidance also asks that it is clear who created the content and that first-hand experience shows. Even if a content team writes the draft, the approval should come from the person who knows the company best.
- Photos and logo. Pictures of your own team, product and premises are stronger than stock images. If stock is used, say who buys the licence; if people can be recognised in a photo, get their permission.
- Legal texts. Article 10 of Law No. 6698 requires the data controller, when collecting personal data, to tell people who the controller is, why the data is processed, who it may be transferred to and why, the method and legal basis of collection, and the person’s rights. The team building the form places the notice; your legal adviser should prepare the text.
- References. Customers who allow their name on the site.
- Access. The current domain, the old site and the email account.
5. How review rounds work
Revisions drag on in most projects because there are no written rules. These six steps keep a round short:
- Before each round, the team says what is to be reviewed: first structure and design, then pages with real content, finally the whole site.
- The decision-maker named in the brief collects every comment in one list. Settle conflicting views within your own team before sending anything to the agency.
- Each item says three things: which page, what you see, what you want. Attach a screenshot.
- Instead of “I don’t like it”, write the reason: “the heading is hard to read”, “the button doesn’t fit on a phone.”
- A request for a new page or feature is not round feedback; it becomes a separate written decision.
- Each round closes with written approval. An approved part is not reopened in a later round without a new reason.
6. Launch-day checklist
Most launch-day jobs are small on their own, but everyone notices when one is missed. Work through this list with the team, putting a test date and your name beside each item:
- Search engine signals. According to Google’s documentation, a noindex tag drops the page from search results entirely. If it travels from the test address to the live site, the site stays out of Google; the test address, in turn, must not be indexed.
- Old addresses. If the site replaces an old one, every old address needs to redirect to its new equivalent. The detail is in keeping SEO through a site rebuild.
- Forms. Send each form from a real phone; the email or CRM record should arrive and the thank-you page should open.
- Links. Phone, email and WhatsApp links should reach the right person.
- KVKK and cookies. The privacy notice sits next to the forms and the cookie choice works.
- Address and security. The site opens at a single address over HTTPS, with and without www going to the same place.
- Speed. Measure the home page and one inner page on a phone.
- Measurement. Form submissions appear as events. For the steps, see the GA4 setup checklist.
- Ownership. You are the verified owner in Search Console.
- Backup. The first backup is taken and you know where it is kept.
7. What you should receive at handover
Handover is a checklist, not a last email from the team. The table below summarises what you receive and why each item is asked for:
| Item | What you receive | Why |
|---|---|---|
| Domain name | Your company as registrant, and access to the transfer code | You can move it independently of the team |
| Hosting | Panel access, account in the company’s name | You can act in an outage or a split |
| Code and design files | Repository access or an archive, design files, licences | Another developer can take over |
| Admin panel | An administrator account and a short walkthrough | You update content yourself |
| Analytics and Search Console | Owner role with you | The data stays with the company |
| Content and backup | Originals of texts and images, database and media backup | You can restore if the site breaks |
| Documentation | Which tools, which integrations, how it is deployed | Knowledge sits in a document |
| Support | Post-launch support scope in writing | You know whom to write to when something breaks |
In our web and software service we list the handover items and post-launch support separately in the proposal.
Common mistakes
- Asking three agencies for proposals without a brief, then being unable to compare them.
- Leaving text and photos for “later”, so the content isn’t ready when the design is.
- Leaving the domain in the agency’s account and never asking who the registrant is.
- Sending feedback in pieces, from different people, through different channels.
- Forgetting the noindex tag from the test address on the live site, or letting the test address get indexed.
- Settling for a “the site is ready” email at handover, without taking the access details and files.
Common questions
What do I need to give an agency to commission a website?
Your brief, logo and brand files, access to your current site and domain, your service or product information and an authorised decision-maker. The proposal should say who prepares the texts and photos.
How many review rounds should I have?
There is no single right number. What matters is that the number and scope of rounds are written in the proposal and that it is clear from the start how out-of-round work is handled. Collecting feedback in one list shortens the rounds.
Is it a problem if the agency buys the domain name?
Not if your company is named as registrant and you have access to the registrar account or a written right to a transfer. If the agency appears as registrant, you depend on its cooperation to get the domain back when you part ways.
One thing you can do today: write the seven headings above into a document and finish it on a single page. A second: log in to your registrar account and see whose name appears as registrant for your domain and when it is due for renewal. Both can be done before you talk to any agency, and both change the direction of that conversation.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.