Two quotes for a website can vary by as much as fivefold without anything in the documentation explaining the difference. The problem isn’t the price—it’s that a website is judged on what isn’t visible. A visitor can’t tell if the pages are indexable, if the code can be reused, or if the site will handle a surge in traffic or a hacking attempt. Neither can you, on the day of delivery.
Here’s what will help you make a decision before signing.
The Five Questions That Reveal the Quality
1. “Show me three websites you’ve delivered that are live online.”
Not screenshots—actual URLs. Then open them on your phone, not on a computer. Check the loading speed, readability, and whether the menu works with a finger. A portfolio consisting of visuals without clickable links often hides projects that were never launched or are no longer presentable.
2. “Who will own the domain name?”
The only correct answer is: you—in your name, with your access credentials. A service provider who keeps the domain in their own name owns your address—and any future negotiations will be to their advantage. The same goes for hosting and the web analytics account.
3. “What happens if I want to switch providers in two years?”
The answer speaks louder than any technical demonstration. A professional will explain where the code is located, how to retrieve a full backup, and what technologies are used. An evasive answer signals that you’re locked in—whether by choice or due to incompetence, the result is the same.
4. “What’s the plan for maintenance?”
A website is software that’s constantly exposed: it receives security updates, it can go down, and it must be backed up. If maintenance isn’t itemized in the proposal, it won’t happen. The point isn’t to pay for a subscription at any cost, but to know who will handle support, how quickly, and at what cost.
5. “How will people find the website?”
If the answer is limited to “we’ll do SEO,” dig deeper. Concrete details are verifiable: does each page have its own title and description; is the content present on the page as served, or only after the browser-side code runs; will a sitemap be submitted to search engines; will images be compressed? These are facts, not promises.
What Goes Wrong, and What It Costs
The flaws that matter don’t show up at launch. They appear six months later, and each one destroys one of the two reasons for having a website—to be found and to be trusted.
| Flaw | What It Costs |
|---|---|
| Pages without their own titles or descriptions | The site exists only for those who know its address, not for those searching for it |
| Content displayed only after browser-side code execution | Search engines may never see the text on internal pages |
| Uncompressed images, unnecessary scripts | Visitors on mobile devices leave before the page loads |
| Text embedded in images | Adding a second language becomes impossible without starting from scratch |
| Code that no one else can reuse | Every change depends on a single person, at their own rate |
| Content management system never updated | Defacement or spam sent from your domain |
None of these six issues are visible in a mockup. They’re all decided during the design phase. That’s the key difference between a site that’s cheaper to buy and one that’s cheaper to use.
The Options, Honestly
Subscription-based online website builders are suitable for a simple, static online presence—if you’re willing to depend on the platform and its pricing. The limitations become apparent as soon as you want a feature that isn’t in the catalog or want to migrate elsewhere.
A purchased theme that’s quickly installed delivers a visually decent result on a tight budget. The known pitfalls: an accumulation of extensions that slows everything down, and an attack surface that grows with every module added.
A developer or a studio costs more upfront and is justified when the site needs to do something specific—sell, register users, take reservations, support multiple languages, or integrate with your tools—or when it represents a significant portion of your business.
There’s no one-size-fits-all answer. There’s one question to ask: How much is a customer who finds you worth? If a single signed contract pays for the site, the “cheapest possible” approach loses its meaning.
Three Red Flags
- A quote with no detailed breakdown. “Website creation—total amount” allows for no comparison and no grounds for a complaint.
- A guarantee of a specific ranking on Google. No one can give that. Those who promise it are selling something else.
- No questions about your business. Anyone who doesn’t ask who you’re selling to or what the website needs to achieve won’t be able to design it to meet those goals.
Before Signing
Ask for the proposal to specify, in writing: the number of pages, who will write the content, the number of rounds of revisions included, ownership of the domain and access rights, what maintenance covers and its cost, the delivery deadline, and what you’ll receive upon completion.
A reputable service provider will provide this information without being asked. That, in itself, is already the best sign.
As for the rest of the project itself, the article Managing a Website Project details the six stages where decisions are made. And to return to the original reasons, Visibility and Credibility sets the stage. The portfolio showcases live websites, along with their URLs—you can visit them and apply the tests described above.