Full transparency first: I’m based in Jundiaí, Brazil, and I sell exactly this service. This article has an obvious interest behind it. Which is precisely why the goal here isn’t “hire me”. It’s to give you the criteria I would use to compare vendors if I were on the other side of the table, including the cases where the best path isn’t me.
Search for website design and you’ll find a bit of everything: marketing agencies, freelancers, someone’s nephew who “knows computers”, drag-and-drop platforms. Prices range from a few hundred to tens of thousands, and at first glance the delivered sites all look the same. The difference shows up later, when the site needs to generate contacts, show up on Google, and be updated without pain.
What matters more than the vendor’s city
Let me start by dismantling the criterion behind the search itself. Building a website is a service that works well at a distance: video calls, approvals by link, delivery in the cloud. A good professional in another city delivers more than a mediocre one on your street.
Where proximity genuinely helps: in-person meetings on larger projects, knowledge of the local market, and referrals you can actually verify. Those are real advantages, but secondary ones. None of them compensates for a weak process.
The criterion that separates vendors isn’t where they are, it’s how they start. Whoever sends a fixed quote within the hour, without asking anything about your business, is selling a template under another name. Whoever starts by asking what the site needs to generate (leads, bookings, sales, authority) is selling the right service.
The questions that reveal who you’re talking to
In a first conversation, these questions do the work of a lie detector:
“Will the site be in my name?” Domain, hosting and analytics accounts need to be registered under accounts you own. There’s an entire business model built on locking clients in through domain ownership. If the answer is evasive, say thanks and move on.
“What happens after delivery?” A site with no maintenance and no data reading loses performance over time. A good answer mentions follow-up, measurement and adjustment. A bad answer is “that’s on you”.
“How do you measure whether the site is working?” If the answer doesn’t include some form of conversion measurement (GA4, events, tracked forms), the vendor delivers graphic design, not a business tool. I’ve written about what a website needs to generate leads, and none of it works without measurement.
“Does the site ship optimized for Google?” Basic technical SEO (indexing, speed, structure) should come standard, not as an upsell. For a local business, also ask about the integration with your Google Business Profile, which is where local search happens first.
Freelancer, agency or platform?
Each format has its place, and I’ve covered the comparison in detail in freelancer vs agency vs template. The summary, applied to the reality of a small business:
Signs of a good vendor
- Asks questions before quoting
- Shows cases with results
- Explains the tech choices
- Delivers everything in your name
- Talks measurement unprompted
Red flags in any format
- Fixed price with no diagnosis
- Portfolio with no business context
- Technology treated as a secret
- Domain registered under their name
- Promises the top spot on Google
About that last red flag: nobody honest guarantees a Google ranking. What can be guaranteed is the solid technical work that creates the conditions to rank. If someone promises you the first position, ask them to put in writing how long it will take and for which keyword, and watch the answer change.
So how much does it cost?
Price ranges vary by scope, technology and strategic depth, and I keep an honest guide on what a professional website costs with the ranges practiced in the market. For the hiring decision, the reasoning that matters is a different one: a price that’s too low is a symptom.
Run the math backwards: if a website costs $1,500 and takes, say, 60 hours of proper work across diagnosis, design, content and development, the vendor’s hour comes out to $25. Either the professional is just starting out (which can be a good deal, with adjusted expectations), or something in those 60 hours isn’t going to happen. Usually the diagnosis, the content and the measurement: exactly the parts that make a website pay for itself.
The decision checklist
- Did the vendor ask about your business before talking price?
- Will domain, hosting and analytics stay under your accounts?
- Is basic technical SEO a defined deliverable?
- Does the proposal mention how conversion will be measured?
- Have you seen at least one case with context and results?
- Is post-delivery defined: maintenance, adjustments, follow-up?
If a local vendor and a remote one tie on these criteria, the local one wins the tiebreaker: face-to-face meetings have value, and knowing the regional market helps with content. But the tiebreaker is the last step, not the first filter.
What this means for your business
A website is one of the few marketing investments that works 24 hours a day for years. The difference between hiring well and hiring cheap doesn’t show up at delivery: it shows up six months later, in the number of contacts that arrive (or don’t) through it.
Choosing with criteria costs you a few extra conversations now. Choosing wrong costs a full rebuild later, plus the time the right site would have already spent generating customers.
Author
Raphael Pereira
Designer & strategist focused on performance-led digital experiences.
Related posts
Freelancer vs agency vs template: how to choose for your business
The right answer depends on three variables that most people ignore before asking for a quote.
Continue reading
Why freemium doesn't work with AI products
The traditional SaaS playbook doesn't survive AI's marginal cost. See what companies like Stripe and Notion are doing instead.
Continue reading
How Notion uses AI to increase product manager autonomy (and you can do the same)
Notion's Head of Product argues that cultivating autonomy matters more than mastering tools. Here's how it changes the way you structure product teams.
Continue reading