Read a proposal for what it leaves out
Most risky web design proposals are not dishonest; they are vague. The danger is in what is missing: who owns the domain, what happens to logins at launch, exactly which pages are included, what "SEO" means and what support you get afterwards. If you have a proposal in hand, this guide lists the red flags to look for and, for each one, the kind of wording that protects you.
It is written for owners and managers evaluating a quote they have already received. If you have not yet contacted designers, start with our checklist of what to prepare before hiring, then come back here when proposals arrive.
Ownership red flags: domain, hosting and logins
Ownership problems cause the most painful disputes because they surface later, often when you want to change designers or the agency stops responding.
The domain will be registered in the agency's name
Some proposals say "domain included" and then register it in the agency's own account. You use the address for years, print it on signboards and visiting cards, and then discover you need the agency's permission to move it. Look for a line that names your business as the registrant.
No mention of handing over logins
If the proposal says nothing about access, assume you will not get it. You need the website admin login, the hosting control panel login and the domain registrar login, or at least the right to receive them on request.
Unclear ownership of the code, design and content
For custom work, the proposal should say whether you receive the source code and design files once paid. For theme-based sites, it should say whose name the theme licence is in. Content you supply, and content written for you, should be yours to reuse.
Better wording: "The domain will be registered in the client's name. On final payment, the client will receive the website admin, hosting and domain logins, and the source files for custom work."
Scope red flags: "unlimited pages" and no content plan
Vague scope is the main reason website projects run late and end in arguments about extra charges.
"Unlimited pages" or a page count with no names
"Unlimited pages" sounds generous, but it usually means the agency will create pages as long as you supply finished content, using one standard layout. A bare number like "10 pages" has the same problem. Ask for the pages to be named, with a note of which ones get a specific layout.
No content plan
If the proposal does not say who writes the text and supplies the images for each page, the project will wait for content that nobody has agreed to produce. A good proposal includes a sitemap and content plan, or at least a table of pages with "client supplies" or "agency writes" against each.
Revisions not defined
"Changes as required" invites conflict. A clear proposal states how many rounds of design changes are included and how further changes are charged.
Better wording: "Scope covers the 12 pages listed in Annexure A. Two rounds of design revisions are included. The agency will write text for the service pages from client notes; the client will supply photographs."
Design red flag: a template sold as custom design
Using a ready-made theme is perfectly reasonable and keeps cost down. The red flag is when a proposal describes the work as "custom design" or "designed from scratch" while the plan is to install a theme with your logo. You end up paying for original design and getting something many other sites already use.
Ask directly: "Is this based on a theme or template? If so, which one, and can we see the demo?" An honest designer will tell you and explain what will be changed for you. Also check whether the theme licence is paid for and in whose name, because some themes need renewal for updates.
Better wording: "The site will be built on the [named] theme, licensed in the client's name, with the home page and service page layouts customised as per the approved mock-ups."
Marketing red flags: vague "SEO included" and ranking promises
Almost every website proposal now says "SEO-friendly" or "SEO included". On its own, that phrase means very little. Basic SEO setup during a website build is a defined set of tasks: unique page titles and meta descriptions, a sensible heading structure, clean page addresses, image alt text, an XML sitemap, connecting Google Search Console and making sure pages load quickly on a phone. If those tasks are not listed, you cannot check whether they were done.
A stronger red flag is any promise of a particular ranking position or a guaranteed number of leads within a fixed period. Nobody controls how Google ranks pages, and Google's own guidance for site owners on Google Search Central explains what site owners can influence. Ongoing SEO is a separate, continuing service, like MATROP's SEO service, and should be quoted separately from the build.
Better wording: "SEO setup includes page titles, meta descriptions, heading structure, image alt text, XML sitemap and Google Search Console connection for all pages in scope. Ongoing SEO is not included."
After-launch red flags: no maintenance terms, no support period
A proposal that ends at "go-live" leaves you guessing about the most important months. Look for answers to these questions in writing:
- Bug-fix period: is there a period after launch during which faults in the agreed work are fixed without charge, and how long is it?
- Maintenance: is a yearly maintenance plan offered, and does it list what it covers, such as updates, backups, security checks and a number of content edits?
- Renewals: are hosting, domain and licence renewal amounts stated, or only the first year?
- Training: will someone show your staff how to update text, images and notices?
- Exit: if you stop the maintenance plan, will the agency hand over everything needed for someone else to take over?
For a detailed list of what a maintenance contract should spell out, see our guide on what a website AMC includes.
Payment and timeline red flags
Watch for a demand for the full fee in advance, a launch date with no list of what you must supply and by when, and no milestones between signing and launch. Projects run better when payments are linked to stages you can see, such as an approved design, a working site on a test address and the live launch. A realistic timeline also states its dependencies: the date holds only if content, photos and approvals arrive on time.
Quick reference: red flag, risk and better clause
Keep this table next to the proposal while you read it.
| Red flag in the proposal | Why it hurts you | What to ask for instead |
|---|---|---|
| Domain registered by the agency | You cannot move your address without them | Domain registered in your business name |
| No login handover | You are locked to one supplier | Admin, hosting and domain logins on final payment |
| "Unlimited pages" or unnamed page count | Scope disputes and generic layouts | Named page list with layouts noted |
| No content plan | Project stalls waiting for text | Table of who writes and supplies what |
| Template called custom design | Paying for work not done | Theme named, licence in your name |
| "SEO included" with no detail | Cannot check what was done | Itemised SEO setup tasks |
| Guaranteed rankings or leads | Promise nobody can control | Clear tasks and honest reporting |
| No support or maintenance terms | Unknown costs after launch | Bug-fix period and a written maintenance scope |
| Full advance, no milestones | Little influence if work slows | Stage payments tied to visible milestones |
Questions to send back before you sign, and where MATROP fits
Reply to the proposal in writing and ask the agency to confirm each point. A good agency will welcome the questions.
- Please confirm the domain will be in our business name and list the logins we will receive at launch.
- Please attach the named page list and say who writes and supplies content for each page.
- Is the design theme-based or original? If theme-based, please name it.
- Please itemise the SEO setup tasks included.
- What is the bug-fix period after launch, and what does your maintenance plan cover?
- Please state the year-two renewal costs for hosting, domain and any licences.
- Please link payments to milestones and list what you need from us for each one.
When you ask MATROP for a quote, you can put the same questions to us. Our website design and development work starts with your goals and a sitemap and content plan, moves through design, development and security and speed work, and ends with launch, basic training and the option of ongoing updates, backups and website maintenance. If you are looking for someone to build a large custom software platform rather than a website, our guide on checking a software development company is the better starting point.
Questions people ask
Is it a red flag if the agency builds my site on a WordPress theme?
No. Themes are a normal, cost-effective starting point. It only becomes a problem when the proposal calls it a custom design, does not name the theme or does not say whether the theme licence is included.
The agency says it will keep the domain in its account for safety. Is that acceptable?
It is safer for you to hold the domain in an account in your business's name and give the agency access to manage settings. If the relationship ends, you keep your address without needing their cooperation.
Should I ever pay the full website fee in advance?
It is better to pay in stages linked to clear milestones, such as design approval, a working site for review and launch. A full advance leaves you with little influence if the project slows or the scope is disputed.
What should "SEO included" actually mean in a website proposal?
It should list specific setup tasks, such as page titles, meta descriptions, heading structure, an XML sitemap and Search Console setup. Ongoing SEO work is a separate, continuing service and should be quoted as such.
