Website Developer Red Flags - Warning Signs to Avoid

Website Developer Red Flags: What to Look Out for Before You Sign

Ok, great - you’ve got an exciting new idea for a website and have even found a Web developer, but just before you sign the contract - something doesn’t feel right? Choosing someone to build your website can feel like a minefield.

There are excellent website designers and developers who will give you honest advice, explain your options and build something that genuinely helps your business. Unfortunately, there are also situations where business owners end up paying far more than expected, getting locked into expensive hosting contracts, or finding themselves unable to make simple changes without paying another hefty fee.

Not every bad experience is a scam. Sometimes it is simply poor communication, unclear pricing or a developer-client relationship that was never properly outlined from the start. But that’s ok - sometimes things aren’t meant to be but are these things avoidable?

There are some definite website developer red flags worth knowing before you sign a contract or hand over your domain, hosting or website.

Here are some of the biggest ones to look out for.

1. Extortionate hosting fees

One of the biggest red flags is being charged a large amount for website hosting without a clear explanation of what you are actually receiving.

The majority of hosting does cost money somewhere down the line*. Good hosting can make a genuine difference to website speed, reliability, security, support and now more than ever - website rankings.

But there is a big difference between paying for quality hosting and being charged an inflated annual fee simply because your developer controls the account.

Ask:

• Who owns the hosting account?
• What does the fee include?
• Is SSL included?
• Are backups included?
• Is website maintenance included?
• Can I move the website to another host?
• What happens if I stop working with you?

A particularly concerning situation is when you are told that moving your website elsewhere would be difficult, impossible or prohibitively expensive.

Your website should not feel like a hostage.

A developer may manage your hosting for convenience, and there is nothing inherently wrong with that. The important thing is transparency and ownership.

You should know what you are paying for. At Vassel I make that abundantly clear from the offset. I discuss what is wrong with your current site and whether I can help - no matter what situation you may be in.

2. Massive prices for a very simple WordPress website

A professional website is an investment, and there is no single "correct" price for a website.

However, it is worth asking questions when you are quoted a surprisingly large amount for a relatively ‘straightforward’ website.

A basic WordPress website with a handful of pages, a contact form, standard functionality and limited custom development is very different from a complex ecommerce platform, membership system or bespoke web application.

The price should reflect the work involved.

This does not mean you should automatically choose the cheapest quote.

In fact, extremely cheap websites can bring their own problems.

Instead, ask the developer to break the quote down:

What am I actually paying for?

You should be able to understand whether the cost covers things such as:

• Strategy and planning
• UX and design
• Copywriting
• Development
• WordPress configuration
• Plugins and licences
• SEO setup
• Accessibility
• Testing
• Hosting
• Training
• Ongoing support

A good developer should be comfortable explaining the price rather than simply presenting you with a large number. Take a look at my comprehensive 2026 guide on How Much Does A Website Cost so you can get a rough idea without being blindsided.

3. You're being pressured into a particular technology stack

Another warning sign is being told that you have to use a particular platform, framework or technology without your requirements being properly discussed first.

There are many excellent technologies available, more so now than ever in the world of constantly changing technologies and ever more competitive searches. Wordpress isn’t always the answer anymore.

Next.js and a headless CMS might make sense for your business. Shopify may be appropriate for an ecommerce business. A completely different solution might be better for someone else.

The problem isn't the technology.

The problem is when the technology is chosen for the developer rather than for the client.

A good developer should start with questions such as:

What are you trying to achieve?

Who will use the website?

What functionality do you need?

Who will manage the content?

What is your budget?

What might you need in two or three years?

Only then should the technology be discussed.

Be cautious if you are being pushed into a stack you do not understand simply because you are told it is "the best", "the only serious option", or something you "must" use.

You should be given informed choices, not pressured into a technical decision.

4. They become difficult to reach once the website is launched

This is one of the most frustrating experiences for a business owner.

During the sales process, your developer responds quickly.

They are enthusiastic.

They want your business.

Then the website launches...

And suddenly getting a response becomes incredibly difficult.

Of course, developers get busy. Nobody can be available every minute of the day.

But there is a major difference between having reasonable response times and effectively disappearing after launch.

Before starting a project, ask:

What happens after launch?

Find out whether support is included, what the response times are, and whether there is an ongoing maintenance agreement.

A website is not necessarily "finished" simply because it has gone live.

You may need help with updates, bugs, content changes, security issues or technical questions. I have already helped a client with their website who had this very experience with a previous developer. Read about how we navigated this situation together and revamped their site in the process, here!

A top tip here is to establish check-in time after launch. Here at Vassel I understand that not every business want’s the same support package, however I understand that every business will need support somewhere down the line. Having a pay-as-you-go series of hours is a popular choice for many of my clients. Allowing a series of hours to be cashed in at any time after launch if you need revisions is a top flexible option.

5. Every tiny change comes with a huge maintenance bill

Another red flag is being charged an unreasonable amount for very small changes.

Changing a phone number?

£XX.

Updating a paragraph?

£XX.

Adding a new image?

£XX.

Changing the wording of a button?

£XX.

There are legitimate reasons why developers charge for maintenance. Their time has value, and some changes can be more complicated than they look.

But if you feel like every five-minute change has turned into an expensive invoice, it is worth asking whether the website has been built with the client in mind or just to fill pockets.

A good website should make reasonable content updates manageable.

That might mean giving you a CMS you can use yourself, providing training, or offering a sensible maintenance arrangement for changes you would rather have someone else handle.

The goal should be to make maintaining your website straightforward - not to create artificial dependence.

6. They refuse to give you access to your own website

This is a particularly important one. Establish this straight away and if you even get a whiff of this being difficult down the line don’t walk away, RUN!

You should know what accounts and assets belong to your business. If they are associated to your brand and you pay for them, you should be the only one to own them.

That can include:

• Your domain
• Your hosting account
• Your WordPress installation
• Your CMS
• Your website files
• Your database
• Your analytics
• Your Google Search Console account
• Your email accounts
• Your content and images

A developer may legitimately manage some of these on your behalf.

That's fine.

What isn't fine is refusing to give you access or suggesting that you are not entitled to it.

Your website is a business asset.

You should not have to beg a developer for access to something you have paid them to create or that you actually pay the bill for.

7. You're locked into their system

This is perhaps the biggest long-term red flag.

Imagine you have paid for a website, but a year later you decide to change developer.

Suddenly you're told:

"You can't take the site with you."

Or:

"The code belongs to us."

Or:

"You'll have to rebuild everything."

Sometimes there are legitimate technical reasons why a website cannot simply be picked up and transferred without work.

For example, a bespoke application may depend on particular infrastructure or proprietary systems.

But there is a difference between a technically complex migration and deliberately creating vendor lock-in.

Before starting a project, ask:

If I wanted to move my website to another developer in three years, what would happen?

The answer should be clear.

Your developer should not be trying to make it impossible for you to leave.

8. Everything sounds deliberately complicated

You don't need to understand every piece of technical terminology involved in building a website.

But you should understand the important decisions affecting your business.

Be cautious when technical language seems to be used to avoid answering straightforward questions.

You should be able to ask:

"Why do we need this?"

and receive an answer you can actually understand.

A good developer doesn't make you feel stupid for asking questions.

They translate technical decisions into business decisions.

So, how do you protect yourself?

Before signing a website contract, make sure you know:

What am I getting?

What does it cost?

What ongoing costs will there be?

Who owns the website?

Who owns the domain and hosting?

Can I access the website myself?

Can another developer take over in the future?

What support is included after launch?

How much do additional changes cost?

And most importantly:

Does the developer seem interested in what my business actually needs?

You don't need the most expensive website.

You don't need the newest technology.

You don't need a huge monthly maintenance package.

You need a website that is appropriate for your business, your customers and your goals.

If you have alarm bells ringing for any of the above, don’t panic - reach out to me. Delighted to have a chat about any prospective agreement or help you to navigate exiting one that hasn’t got your best interests at heart.

A website developer should be your partner, not your gatekeeper

The best website projects are built on trust.

That means being honest about what you need, what you don't need, what things cost and what technology is appropriate. Take a look at my handy guide into ‘Do I actually need a Website designer?’ - a totally valid question.

At Vassel Creative, I believe you should understand what you're paying for and why.

That means no unnecessary technology for the sake of it, no deliberately confusing pricing, and no attempt to make you dependent on one person forever.

Your website should be a business asset that you control — not something you are afraid to lose access to.

Thinking about a new website?

Before you commit to a developer, get an independent view of what your business actually needs.

Get in touch with me, Vassel Creative to discuss your website, requirements and budget!