Red Flags in Web Proposals (and What Good Ones Look Like)

The obvious red flags are easy.

No portfolio. No contract. No real business name. A price that sounds fake. A designer who only accepts payment through a sketchy channel. A promise to "rank you #1 on Google" by next week.

Most business owners know to be careful with those.

The more expensive red flags are quieter.

They often look professional. They may even sound like industry standard. A big deposit before any real direction. Vague ownership terms. No clear update policy. A beautiful proposal that never explains what happens after launch. A "custom" website that is really a lightly edited template. A low starting price with year-two costs hiding somewhere else.

Those are the red flags that hurt service businesses.

Not because every designer is trying to mislead you. Many freelancers and agencies do good work. But a website is not just a launch project. It is an ongoing business asset. If the relationship, access, pricing, and support are unclear, the site can become expensive long after the design looks finished.

Here are the red flags to watch for before hiring anyone.

Red flag 1: They start with design before strategy

A website project should not begin with colors, fonts, or homepage mockups.

It should begin with questions like:

• Who is the site for?
• What action should visitors take?
• Which services matter most?
• What does the business need to prove?
• What do competitors already say?
• What trust signals matter in this industry?
• What should be above the fold?
• What pages are actually needed?

If the process jumps straight into visual design, decisions become subjective very quickly.

You say, "I don't love this."

The designer says, "What don't you love?"

Everyone starts arguing about taste because nobody documented the strategy.

That does not mean visual design is unimportant. It matters. But design is easier to evaluate when there is a clear plan behind it.

A better question to ask:

What do you document before design begins?

Red flag 2: You pay a large deposit before seeing real direction

This is common.

A designer or agency asks for 40-50% upfront before any design work begins. That does not automatically make them bad. Many traditional projects work that way.

But it does shift risk onto the client.

You are paying before you have seen:

• The strategy
• The recommended structure
• The design direction
• The scope in context
• The support model
• The full long-term cost

That may be fine if you know the provider well and trust their process.

But if you are uncertain, ask:

What will I see before the first payment or before the project is fully committed?

If the answer is only "a proposal," look closer.

A proposal tells you what they plan to sell you. It does not always show you how they think.

Red flag 3: Ownership terms are vague

Website ownership can be confusing because a website is not one thing.

It usually includes:

• Domain
• Content
• Design
• Platform or CMS
• Hosting account
• Source files or build files
• Analytics and search accounts
• Images and brand assets

If a proposal says "you own your website" but does not explain which parts, ask for detail.

Do you own the domain? Do you own the copy? Do you own the design? Can the site be transferred? Can someone else maintain it? Can you export the content? What happens if you cancel?

The red flag is not that every provider has the same ownership model. They do not. The red flag is when the provider cannot explain the model clearly.

Red flag 4: "Unlimited updates" is not defined

Unlimited updates can be a good promise when it is honest and specific.

It can also become a problem when nobody defines what an update means.

A standard content update might be:

• Change business hours
• Swap a photo
• Update a service description
• Add a testimonial
• Edit a team bio
• Change a phone number
• Update a small section of page content

A larger improvement might be:

• Add a new page
• Redesign a section
• Build a landing page
• Run an SEO campaign
• Publish ongoing blog content
• Create a new form flow
• Refresh the entire site

Those are not the same level of work.

If a provider says "unlimited updates," ask:

What counts as a standard update, and what counts as larger work?

If they cannot answer, the unlimited promise may create friction later.

Red flag 5: There is no after-launch plan

A website launch is not the end of the website's life.

It is the beginning of its useful life.

After launch, someone has to handle:

• Hosting
• SSL
• Backups
• Security updates
• Platform updates
• Broken links
• Form issues
• Analytics verification
• Content changes
• Service updates
• Refreshes over time

If the provider's process ends at launch, ask:

What happens after the site goes live?

If the answer is vague, you may be buying a project instead of a working website relationship.

That can still be fine. Some businesses want a one-time project.

But service businesses that change over time usually need a support path.

Red flag 6: Year-two costs are unclear

Many proposals explain the launch price and skip the second year.

That is where owners get surprised.

Year two may include:

• Hosting renewal
• Domain renewal
• Plugin renewals
• Theme or builder renewals
• Maintenance retainer
• Per-change billing
• Security tools
• Backup tools
• SEO tools
• Refresh work

Ask:

What will this website cost me in year two?

Then ask:

What will it cost me over five years?

A good provider may not know every future detail, but they should be able to explain the likely categories.

Red flag 7: "Custom" is not explained

Almost every website provider uses the word custom.

The word can mean very different things.

It might mean:

• Fully custom strategy, structure, design, and build
• Custom design on a standard platform
• A customized template
• A white-labeled theme
• A page builder layout with custom colors and content
• A semi-custom system with reusable components

None of those are automatically bad.

A template may be the right fit for a simple site. A fully custom build may be unnecessary for many service businesses. A reusable component system can be efficient and high quality.

The red flag is when "custom" is used as a vibe instead of a definition.

Ask:

What parts are custom, and what parts are based on templates, reusable components, or platform defaults?

A good provider should be able to answer without getting defensive.

Red flag 8: Nobody explains who writes the copy

Many website projects stall because everyone thought someone else was writing the words.

The designer thought the client would provide copy.

The client thought the designer would write copy.

The agency included "content placement" but not copywriting.

The result is a good-looking design filled with weak, generic, or unfinished content.

Ask:

Who writes the words on the site?

Then ask:

Who decides what each page needs to say?

For a service business, copy is not filler. It explains your services, earns trust, answers objections, and gets visitors to call, book, or request a quote.

If nobody owns it, the site will suffer.

Red flag 9: Launch means "we publish it" and nothing else

Publishing the site is not the whole launch.

A real launch should include checks like:

• Domain and DNS configuration
• SSL active
• Forms working
• Key links working
• Mobile behavior checked
• Browser behavior checked
• Analytics verified
• Sitemap available or submitted
• Search Console connected when appropriate
• Backup or recovery path confirmed

Those are not the only launch tasks, but they are examples of the kind of verification that should not be left to chance.

Ask:

What exactly do you check before and after launch?

If the answer is "we make it live," that may not be enough.

Red flag 10: There is no exit path

This is the quietest red flag.

Many website proposals explain how the relationship starts. Fewer explain how it ends.

You should know:

• Can you cancel?
• Is there a cancellation fee?
• What do you keep?
• What do you lose?
• What can be transferred?
• What cannot be transferred?
• What happens to hosting?
• What happens to your content?
• What happens to the design?
• Is there a buyout?
• How long does a transition take?

If you feel awkward asking, ask anyway.

A healthy provider relationship should be able to discuss the end before the beginning.

Red flag 11: The project has no decision points

A website project should have clear moments where you can say:

• Yes, this is the right direction
• No, this needs to change
• We need to adjust scope
• We are ready to approve
• We are ready to launch

Without decision points, projects drift.

Feedback gets messy. Scope grows quietly. Timelines stretch. The client never knows whether they are reviewing strategy, design, content, or polish.

Ask:

What do I approve, and when?

The answer should be specific.

Red flag 12: The provider gets defensive when you ask normal questions

This may be the most important one.

A good web designer may not have the exact same model as Evident. They may charge upfront. They may build on WordPress. They may use Webflow. They may offer retainers. They may work project-by-project.

That is all fine.

What matters is whether they can explain the model clearly.

If you ask about ownership, cancellation, updates, hosting, or year-two costs and the provider becomes vague, annoyed, or dismissive, pay attention.

Those are not difficult questions.

They are the questions a good designer should want you to ask.

How Evident tries to do this differently

Evident Sites was designed around the problems that make website projects feel risky.

We are not the right fit for every business.

If you want a one-time project, full platform control from day one, or a fully custom software application, another path may be better.

But if you want a clear process, predictable pricing, and a site that is cared for after launch, these red flags are exactly what the Evident model is meant to avoid.

The bottom line

The biggest red flags in web design are not always dramatic.

They are often the missing details:

• Who owns what?
• What happens after launch?
• What counts as an update?
• What happens in year two?
• What happens if I leave?
• What happens if you disappear?
• What do I get to see before I pay?

If a provider can answer those questions clearly, you are in a much better position to make a good decision.

If they cannot, the proposal may be hiding more risk than the price suggests.

Before you sign anything, ask the uncomfortable questions. A good designer will respect you for it.

If you are evaluating web designers and want to see how Evident answers every one of these questions, book a free discovery call. We will walk through the process, pricing, and ownership in plain English before anything starts.