The proposal is the relationship in miniature
By the time a proposal lands in your inbox, the charm offensive is over and the paperwork begins. This is the document that predicts how the project will actually run: what is promised, what is ambiguous, and where the costs hide. Most disputes between small businesses and web agencies trace back to something that was visible in the proposal, or conspicuously missing from it.
Here are the ten red flags worth hunting for in any web proposal, grouped by the damage they do, plus the questions that flush them out before you sign anything.
Fuzzy scope: flags one to three
1. Deliverables without numbers
'A modern, responsive website' commits the agency to nothing. A real proposal counts things: how many page templates, how many rounds of revisions, which browsers and devices are tested, and whether content entry is included or you will be pasting in forty pages yourself.
2. 'Unlimited revisions'
It sounds generous; it is actually a warning. Unlimited revisions means the agency has priced in vagueness, usually by padding the fee or by defining 'revision' more narrowly than you think. Two or three structured rounds with a clear definition is healthier for both sides.
3. A timeline with no dependencies
If the schedule does not state what the agency needs from you and when (content, photography, approvals), you will later be told the delay is yours. Good proposals make client-side dependencies explicit.
Need a hand with this?
Our team delivers Web Design for UK businesses — with a free initial consultation, transparent fixed quotes and no lock-in contracts. Tell us what you're working on →
Ownership and lock-in: flags four to six
4. Silence on intellectual property
Under UK copyright law, the creator owns the work unless it is assigned in writing. Paying the invoice does not automatically make the design and code yours. Look for a clause assigning full IP in the deliverables to you on final payment. Where the build uses open-source or licensed components, the proposal should say so and confirm your right to keep using them.
5. Domain or hosting registered in the agency's name
Your domain is a business asset, like the lease on your premises. If the proposal has the agency registering it 'for convenience', you are handing over the freehold. Register the domain yourself and grant the agency access instead.
6. No admin access to your own site
Some agencies deliver editor accounts only and keep administrator rights to themselves. That is a leash. You may choose never to use full access, but you must have it from day one.
Money mechanics: flags seven to ten
7. Hosting at a mystery markup
'Hosting: £60 per month' with no named provider or specification usually means £10 of commodity hosting wearing a £50 label. Marking up for genuine management is legitimate; hiding what sits underneath is not. Ask what the platform is and what the management actually includes.
8. The retainer trap
Watch for maintenance retainers with twelve-month minimum terms, automatic renewal and ninety-day notice periods buried in the small print. A confident agency retains clients with service, not clauses.
9. Payment schedule extremes
One hundred per cent upfront is a red flag; so, oddly, is 'pay on completion', which invites disputes about what 'complete' means. A staged schedule tied to milestones (deposit, design approval, launch) protects both sides.
10. Licensing gaps
Stock photography, premium fonts and paid plugins are often licensed to the agency's own account. When you part ways, your site can quietly become unlicensed. The proposal should state that licences are purchased in your name or formally transferred at handover.
Ten questions that expose the truth
- Who owns the design, code and content once the final invoice is paid, and is that written into the contract?
- Will the domain, hosting and all licences be registered in my company's name?
- Exactly how many pages, templates and revision rounds are included?
- What do you need from me, and by when, for the timeline to hold?
- What happens if we part ways mid-project, and what do I keep?
- Can I have full administrator access from day one?
- What is the hosting platform, and what does the monthly fee actually cover?
- What are the notice period and minimum term on any ongoing services?
- Is the site built on a standard platform another developer could take over?
- Can I speak to two clients whose sites launched more than a year ago?
That last one matters most. Fresh references are chosen for their glow; year-old references reveal what support is like once the launch buzz has gone.
Key Takeaway
Before signing, get four things in writing: itemised deliverables with numbers (pages, revision rounds, browsers tested), a clause assigning full IP ownership of design and code to you on final payment, the domain and hosting registered in your company's name, and an exit process with handover of all credentials and licences. Any agency that resists one of these is telling you exactly how the relationship will end.
What a good proposal looks like
None of this is exotic. A trustworthy proposal names its numbers, assigns ownership plainly, itemises third-party costs at face value and reads as though the agency expects you to leave one day and is not frightened by it. The agencies most relaxed about your exit are usually the ones you will never want to leave.
If you have a proposal on your desk and something in it feels vague, our team is happy to give a straightforward second opinion.