
Hiring a website build: 7 costly mistakes
By Leonel Rocha · Product Designer
· 6 min read
The costliest mistakes when hiring a website are leaving the domain and hosting in the vendor's name, accepting a quote without a page list, not requiring mobile speed, ignoring accessibility, and not getting the rights assignment in writing. According to the Web Almanac 2025, only 48% of sites pass Google's mobile experience metrics. Almost all of these mistakes can be avoided in the contract, before work starts.
The costliest mistakes when hiring a website are leaving the domain and hosting in the vendor's name, accepting a quote without a page list, not requiring mobile speed, ignoring accessibility, and not getting the rights assignment in writing. According to the Web Almanac 2025, only 48% of sites pass Google's mobile experience metrics. Almost all of these mistakes can be avoided in the contract, before work starts.
- 48%
- of sites pass Google's mobile experience metrics, according to the Web Almanac 2025
- 95,9%
- of home pages have detectable accessibility failures, according to the WebAIM Million 2026
- 56,1
- accessibility errors per home page on average, in the same study
Many website problems start with a decision made at hiring time. The domain ended up in the agency's name. The quote didn't say how many pages were included. Nobody measured mobile speed. The site was delivered, paid for, and months later the company finds out it can't change a sentence without asking someone for a favor.
In this guide I list the 7 costliest mistakes when hiring a website build, with data from recent research, and what to ask for in each case. None of them is technical. All of them are solved with one question before you sign.
1. Leaving domain and hosting in the vendor's name
It's the most common mistake and the most expensive to undo. The vendor registers the domain under their own CPF or CNPJ “to make things easier.” It works until the relationship ends. Then the company finds out that the address on its business cards, on Google, and on its fleet vehicles belongs to someone else.
For .br domains, the registrant on file at Registro.br is in charge. Changing the registrant requires documents and depends on the cooperation of whoever holds it today. If that person has disappeared, it's a long road. I walk through the steps in how to recover your website's domain and hosting.
What to ask for: domain, hosting, email, Google Search Console, Google Analytics, and Google Business Profile in your company's name. The vendor gets admin access, not ownership. Before paying the last installment, look up the domain registrant in Registro.br's public search.
2. No written rights assignment

Paying for a website doesn't, on its own, make you the owner of the layout, illustrations, and code. Brazil's Copyright Law is direct. Article 50 says copyright assignment “shall always be made in writing.” Article 4 requires deals over these rights to be interpreted “restrictively.” And Article 49 only allows a full, permanent transfer through a “written contractual stipulation.”
In practice: anything the contract doesn't say is yours can be disputed. That matters the day you want to switch vendors, reuse the layout on a new landing page, or take the code to another team.
What to ask for: a clause that transfers the source code, design files (Figma or equivalent), images created for the project, and copy to the company. And delivery of those files along with the site, not “whenever you ask.”
3. Accepting a quote without a page list
Two quotes for a “company website” can have very different prices and both be right. One includes five pages, the other fifteen. One has a blog, a form connected to the CRM, and an English version. The other has a contact page with WhatsApp.
Without a page list, the cheap quote gets expensive at the first change. “That page wasn't in scope” is the line that starts the argument over timeline and price. I show what goes into the number in how much a professional business website costs.
What to ask for: the page list for the first version, what each page delivers (form, gallery, integration), who writes the copy, who provides the photos, and how many revision rounds are included.
4. Not requiring mobile speed
Most people who look up a business on Google do it on their phone. And mobile is exactly where most sites fall short.
The Web Almanac 2025, the HTTP Archive's annual report published in January 2026, shows that only 48% of sites pass Core Web Vitals on mobile, the metrics Google uses to measure the experience of people visiting a page. On desktop, it's 56%. The weak spot is the time to show the largest element on screen: only 62% of sites land in the good range on mobile.
In other words: hiring a website without a speed target means accepting the chance of landing in the bottom half. The site looks great in the presentation, shown on a big monitor with fast internet, and stalls on the customer's 4G.
What to ask for: a target measured on mobile, with Google's PageSpeed Insights, for example, written into the contract. Test the site on your own phone before you accept delivery.
5. Ignoring accessibility
Accessibility usually stays out of the quote because nobody asks. And the result shows up in the numbers. The WebAIM Million, which analyzes 1 million home pages every year, found in its March 2026 edition detectable failures on 95.9% of pages, up from 94.8% the year before. The average rose to 56.1 errors per page.
The most common errors are easy to avoid when they're part of the project from the start:
- Low-contrast text: 83.9% of pages.
- Images without alt text: 53.1%.
- Form fields without labels: 51%.
- Empty links: 46.3%.
Look at the third item. Unlabeled fields get in the way of the quote form, the part of the site that should bring in customers. And many of these errors also hurt how Google and AI tools read the site.
What to ask for: contrast, alt text, and accessible forms as part of the scope, not as an extra.
6. Leaving SEO for later
“We'll launch first and deal with SEO later.” That sentence costs months. A site that goes live without a sitemap, without titles written for search, without structured data, and without copy that answers what customers ask starts behind. And redoing the page structure after launch can cost rankings you had already earned.
Today this applies to AI too. People who ask ChatGPT or Gemini for a vendor get the names of companies whose sites the AI was able to read and understand.
What to ask for: sitemap, titles and descriptions for every page, structured data, and access for search and AI crawlers, all ready on launch day.
7. Not agreeing on what happens after launch
The site goes live and the contract ends. Three months later the form stops sending email, a plugin needs an update, or the security certificate expires. Who fixes it? How much does it cost? How fast?
Without this in writing, every problem becomes a negotiation. And on site builders and ready-made themes, updates are frequent.
What to ask for: what's covered after delivery, for how long, how much monthly maintenance costs, if any, and who to contact when something breaks.
How we do it at the Studio
At the Studio, we set a fixed price after discovery, and the deadline is written into the contract. Code, files, and access stay in the client's name. We have our in-house dev team, and we use Claude Code and Figma for design and build.
The sites we build in custom code launch with SEO and GEO from day one: structured data, sitemap, llms.txt, and robots open to AI. They include the corporate site for Tactik, a construction company, and the sales page for Conversão Visual, which scored 99 out of 100 on Google Lighthouse in October 2026.
What this means for you
Before you sign, ask the vendor seven questions:
- Whose name will the domain, hosting, and Google accounts be in?
- Does the contract transfer the code, layout, and files to me?
- Which pages are included and what does each one deliver?
- What's the mobile speed target and how will it be measured?
- Is accessibility in scope?
- Will SEO be ready on launch day?
- What happens when something breaks after delivery?
If the answers are clear and fit in the contract, you're hiring well. If they come back as “we'll figure it out later,” the cost shows up later, and bigger.
If you want a website with these answers in writing before work starts, website design at the Studio begins with discovery.
Common questions
Should the website domain be in my name or the agency's?
In yours, with your company's CPF or CNPJ as the registrant. The agency can have technical access to set things up, but ownership is yours. You can check who owns a .br domain in Registro.br's public lookup.
If I paid for the website, are the design and code already mine?
Not necessarily. Law 9,610/1998 says copyright assignments must always be made in writing and that contracts over these rights are interpreted narrowly. Ask for a clear clause assigning the code, layout, and files.
How do I know the delivered site is actually fast?
Put a mobile speed target in the contract, measured with Google's PageSpeed Insights, for example, and check it before you accept delivery. According to the Web Almanac 2025, only 48% of sites pass Google's mobile experience metrics.
Should I pick the cheapest quote?
Only if it has the same page list, deliverables, and guarantees as the others. A quote without written scope looks cheap until the first change. Compare item by item, not the final price.
Sources
- Web Almanac 2025: PerformanceHTTP Archive · Himanshu Jariyal, Prathamesh Rasam, Humaira, and Aaron T. Grogg · 2026-01-15 · EN
- The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pagesWebAIM · 2026-03-30 · EN
- Law No. 9,610 of February 19, 1998 (Brazilian Copyright Law)Office of the President of Brazil · 1998-02-19
Related service
Websites
Company websites in code, fast, found on Google and cited by AI
News Responsivo
Get the next article in your inbox
Cost, timelines, AI and behind the scenes of shipping products. No spam.


