Red flags in a website proposal

A proposal is where promises turn into commitments. Most problems that surface halfway through a website project were visible in the proposal, if you knew where to look. This guide lists the red flags we see most often and what a better version looks like.

Scope red flags

The scope is a list of adjectives

"A modern, responsive, SEO-optimized website" describes almost every site. A useful scope names the pages or templates, the features (forms, booking, shop, integrations), the number of design concepts and revision rounds, and what is delivered at the end.

Ask for: a page or template list, a feature list and the number of revision rounds.

Nothing is excluded

Every honest proposal has exclusions. If nothing is listed, you will discover the exclusions later, usually as extra invoices. Common ones: copywriting, photography, content migration, third-party license fees, translations, ongoing maintenance.

Ask for: a written "not included" list.

Content is not mentioned

Who writes the words, who sources the images and who loads the content are three different jobs. If the proposal is silent, assume they are yours. Missing content is one of the most common causes of delay.

Ask for: a clear split of who provides, writes and enters each type of content.

No mention of your existing site

If you have a site with search traffic, the proposal should mention redirects and protecting rankings. If it doesn't, you could lose traffic you spent years earning. See Don't lose your SEO during a migration.

Ownership red flags

Accounts will be set up "on our account"

Domains, hosting, analytics and app subscriptions should be in your name, or in an account you control, with the agency given access. An agency holding your domain is the single biggest lock-in risk. See Website ownership.

The contract doesn't say who owns the work

Look for a clause that transfers ownership of the design and code to you when the project is paid. Some agencies keep rights to reusable components or frameworks, which is reasonable, but you should have a license to use them indefinitely.

Proprietary platforms with no exit

Some agencies build on their own in-house content system. That can be fine, but ask what happens if you leave. If the answer is "you'd have to rebuild", factor that into the price.

Money red flags

A price far below everyone else's

A much lower quote usually means a smaller scope, a template, junior staff or work done elsewhere. Sometimes that is exactly what you need. Just make sure you are comparing like with like. What a website actually costs explains what drives the difference.

Open-ended hourly billing on a build

Hourly billing is normal for open-ended support. On a defined build, it shifts all the risk of overruns to you. If a proposal is hourly, ask for an estimate range and a cap.

No process for changes

Projects change. A good proposal says how changes are requested, priced and approved before work starts.

Recurring costs left out

The build price is only part of it. Hosting, licenses and maintenance continue every year. See Hidden costs to watch for.

Promise red flags

Guaranteed rankings

No one can guarantee a position on Google. Google says so itself in its guidance on hiring an SEO. A proposal that promises "page one in 30 days" is a reason to walk away.

Guarantees without definitions

Some agencies do offer real performance guarantees. A real one defines the metric, the baseline, the time window, how it's measured and what happens if it's missed. If any of those are missing, it's marketing.

Unrealistic timelines

A timeline that ignores your part (content, feedback, approvals) will slip. Look for a schedule that shows your deadlines as well as theirs.

Process red flags

No discovery or strategy phase. Jumping straight to design means decisions get made on guesses.
No testing phase. Ask how the site is checked on phones, in different browsers and for accessibility before launch.
No handoff. You should get logins, documentation and training at the end. See Transferring accounts and ownership to you.
No named people. "Our team" is not a person.

A quick proposal checklist

Before you sign

0 of 7 done

Scope: pages, features, revision rounds and deliverables are listed.
Exclusions: written down.
Content: who writes, sources and loads it is clear.
Ownership: you own the domain, accounts and finished work.
Timeline: includes your responsibilities and deadlines.
Money: total price, payment terms, change process and recurring costs are clear.
After launch: support, maintenance and handoff are described.

Saved in this browser only.

Frequently asked questions

Should I get a lawyer to read the contract?

For a significant project, yes, especially the clauses on ownership, liability and termination. It is a small cost compared with a dispute later.

Can I ask an agency to change their proposal?

Yes. Proposals are a starting point. A reasonable agency will clarify scope, add exclusions or adjust terms when you ask.