The biggest web-design red flags are not a particular platform, price or company size. They are lack of transparency: unclear ownership, unexplained recurring charges, vague scope, no credible live work, promises the supplier cannot control and technical decisions that seem designed around the provider rather than the business.
A red flag is not proof somebody is dishonest.
It is a reason to ask another question.
That distinction matters.
A €5,000 website is not automatically a rip-off.
A monthly maintenance plan is not automatically unnecessary.
WordPress is not automatically wrong.
A freelancer is not automatically risky.
But some patterns deserve scrutiny.
They cannot explain what the quote includes
You receive:
Business website package — €3,500.
What does that mean?
How many page types?
Custom design?
Content?
Photography?
Forms?
Hosting?
SEO?
Revisions?
Analytics?
Launch?
If the supplier cannot turn the price into a clear scope, you cannot properly compare the quote.
Vagueness benefits the seller.
Clarity benefits both sides.
The price changes every time you ask a normal question
Web projects can legitimately change scope.
But normal clarification should not feel like stepping through a minefield of surprise charges.
A good agreement makes the boundary understandable.
What is included?
What is extra?
How are changes approved?
You should not discover halfway through that basic mobile responsiveness or the contact form was considered an optional add-on.
They will not show you live work
Maybe they are new.
That is not automatically a problem.
Everybody starts somewhere.
But if a supplier claims years of experience and cannot show any real live work or meaningful examples, ask why.
Screenshots can hide:
broken navigation;
slow mobile experience;
generic copy;
forms that do not work.
A live site is stronger evidence.
Every portfolio website looks almost identical
Consistency of quality is good.
Identical structure for:
dentist;
plumber;
consultant;
restaurant;
accountant;
is different.
It may indicate a template-driven process.
That is fine if it is sold honestly and priced accordingly.
It is a concern if you are being sold a highly custom strategic project.
The question is fit.
They avoid explaining whether templates are used
Templates can be a legitimate way to reduce cost.
There is no need to be embarrassed about them.
So if the answer becomes oddly evasive, that interests me.
A buyer should know whether they are paying for:
custom design;
a customised template;
a website-builder theme;
a standardised package.
The label should match the service.
The domain is registered only in their name
This deserves serious attention.
A designer may register a domain on behalf of a client for convenience.
But the business should have a clear ownership/control position.
If changing supplier means the current designer can withhold the business's domain, the arrangement is unhealthy.
Your domain is not just another website file.
It may control:
the website;
business email;
brand identity.
Read who should own your domain.
They make moving supplier deliberately difficult
Some platforms are naturally less portable than others.
That is not automatically malicious.
The red flag is deliberate opacity.
You ask:
What happens if I leave?
and nobody will tell you.
Or the answer is:
You lose everything.
Sometimes contractual/licensing reasons genuinely constrain portability.
Those constraints should be known before you sign.
A good service should retain you because it is useful.
Not because leaving breaks the business.
There is a large monthly fee with no clear service
This is one of the industry practices I think small businesses should challenge more often.
You pay:
€150;
€250;
€400 a month
after the project.
Ask what happens each month.
Hosting?
Updates?
Backups?
Content edits?
Support time?
SEO?
Software licences?
Monitoring?
Those can all be legitimate.
But "website management" is not an explanation.
If a static brochure website costs almost nothing to serve and there is no meaningful ongoing work, a large monthly "hosting" bill deserves scrutiny.
I explain the distinction in do I need monthly website fees?.
They bundle everything so you cannot see the recurring costs
Domain.
Hosting.
Email.
Plugins.
SEO.
Maintenance.
All inside one monthly price.
Bundling is not inherently bad.
It can be convenient.
The problem is not knowing what you are actually buying.
If you want to leave, which parts stop?
Which accounts are yours?
Which software needs replacing?
Transparency now prevents arguments later.
They promise first place on Google
No web designer controls Google's organic rankings.
A supplier can improve:
technical foundations;
content;
relevance;
authority;
local SEO;
site structure.
They can make a strong case for likely improvement.
They cannot honestly guarantee Google's ranking algorithm will put a particular page first for a competitive query.
A guarantee like that is not confidence.
It is a promise about somebody else's system.
Article 96 goes deeper into this.
They promise "SEO" but cannot describe any work
Ask:
What does SEO included mean?
If the answer never gets beyond:
we submit it to Google,
that is thin.
Modern search foundations may involve:
crawlability;
indexing;
site structure;
titles;
canonical URLs;
sitemap;
performance;
content;
local relevance;
structured data where appropriate.
Not every website package needs an ongoing SEO campaign.
It should still be possible to describe the work.
Their sales pitch relies on fear
Examples:
Your business will disappear without this.
Google will penalise you if you do not rebuild immediately.
Your current site is about to become illegal.
AI will make your business invisible unless you buy our package.
There are genuine technical and legal risks in web work.
Fear should come with a specific factual explanation.
If the urgency disappears when you ask for the source, be cautious.
They invent complexity you cannot connect to a business need
A five-page service business is sold:
custom database;
proprietary CMS;
bespoke hosting environment;
enterprise analytics;
monthly software stack.
Why?
Sometimes there is a reason.
Usually, the supplier should be able to explain it in one or two ordinary sentences.
If the architecture seems complicated mainly because complexity creates recurring dependency, I would question it.
They sell a CMS when you have no editing requirement
A content-management system can be excellent.
If the business publishes every week, it may be essential.
If the client changes a phone number once every two years, it may be unnecessary.
Selling the same architecture to every business regardless of requirements suggests the supplier is optimising its own workflow.
Not necessarily the client's.
They cannot explain why the chosen technology suits you
This is the positive version of the same point.
Ask:
Why are you recommending this?
A strong answer might be:
You need a browser-based CMS because your team publishes news regularly.
Or:
This is a stable five-page marketing site, so a simpler static architecture avoids unnecessary maintenance.
That is judgement.
"Because that's what we use" is weaker.
They want you to pay for every feature before they know the business
Booking.
Chatbot.
Blog.
Portal.
Newsletter.
CRM.
Automation.
E-commerce.
You may need some of them.
The conversation should establish that.
Feature-selling before requirement discovery can inflate the project very quickly.
They will not discuss ownership in writing
Website ownership is nuanced.
Third-party libraries, fonts and software may remain licensed.
That is normal.
The concern is when the supplier avoids documenting:
domain control;
website rights;
source handover;
account access;
licences;
what happens at termination.
If a commercial relationship depends on nobody ever asking who owns anything, that is not a strong arrangement.
Read who owns the website for the practical distinction.
They want all important accounts under their email
Sometimes an agency centrally manages accounts for operational reasons.
That can be legitimate.
For a small-business site, I would still ask why.
Domain.
Analytics.
Search Console.
Booking.
Payment provider.
Those are business assets.
Client ownership or clearly documented shared access usually creates a healthier long-term position.
They insist their proprietary system is the only sensible solution
A proprietary platform can be excellent.
The issue is whether the limitations are clear.
What can be exported?
What happens if the provider closes?
Can another developer work on it?
Do you need to stay on their hosting forever?
If those trade-offs are acceptable, fine.
If they are hidden until departure, not fine.
They dismiss every cheaper option as unprofessional
This is a sales tactic I dislike.
Cloudflare can be professional.
Static websites can be professional.
Open-source software can be professional.
A €500 site can be professional when the scope fits.
A €5,000 site can also be worth every cent.
Professionalism comes from whether the solution is appropriate and well executed.
Not whether the supplier selected the most expensive possible infrastructure.
Gavin's take
This one matters to me because scepticism can become its own sales trick. Some websites genuinely justify substantial budgets, specialist teams and ongoing support. The red flag is not a high price or a low price; it is a provider who cannot connect the price to identifiable work and business value.
They dismiss every expensive option as a scam
The opposite is also a red flag.
Some projects genuinely cost a lot.
Custom applications.
Large content migrations.
E-commerce.
Complex integrations.
Research.
Photography.
Copy.
Brand work.
Heavy stakeholder management.
A designer who claims every website over €1,000 is a rip-off is not showing judgement either.
The point is to connect cost to work.
They cannot tell you what happens after launch
You ask:
What happens when the site goes live?
and the answer is effectively:
It goes live.
Who owns the accounts?
Who tests the forms?
How are future changes handled?
What if a dependency breaks?
Does the project include a short support period?
What ongoing costs continue?
There should be an answer.
They pressure you to sign immediately
Some discounts have genuine deadlines.
Capacity can be limited.
But a website project is not usually an emergency consumer purchase.
If the supplier resists giving you time to understand:
scope;
ownership;
ongoing costs;
contract;
that is information.
You should be allowed to know what you are buying.
They never ask what success means
This might be the biggest design red flag.
The conversation is entirely about:
pages;
animations;
features;
colours;
technology.
Nobody asks:
What should the website do for the business?
More enquiries?
Better-quality enquiries?
Credibility?
Bookings?
Recruitment?
Reduce repetitive questions?
Support a sales process?
A site can be technically polished and commercially irrelevant.
How Built by Gavin differs
I am not interested in convincing every business it needs the largest possible project.
My model works when the site can be:
custom;
focused;
technically solid;
reasonably priced;
low in unnecessary recurring cost.
I want clients to understand domain control and ongoing costs.
I do not use the need for hosting as an excuse to invent a permanent revenue stream.
And if a business genuinely needs something more complex than I should sensibly build, I would rather scope that honestly than disguise a large software project as a normal website.
Worth knowing
A single red flag is not always proof of a bad provider. What matters is the pattern: vague scope, vague ownership, pressure, unexplained recurring charges and promises nobody can responsibly guarantee. Good suppliers should make the decision easier to understand, not harder.
The bottom line
The biggest red flag is not one platform or price.
It is a supplier who makes ordinary questions difficult to answer.
What am I buying?
What will it cost?
Why are you recommending this?
What do I own?
What will I pay later?
Can I leave?
A good web designer should be able to answer those without making you feel unreasonable for asking.
Something in a web-design quote does not feel right?
You can compare it against my pricing and scope or send me the structure of the quote.
You can remove the other supplier's name. The useful part is understanding what the arrangement actually means.
---