Should You Pay a Web Designer Before Seeing the Design?
Paying a web designer before the final design is normal when the agreement clearly defines scope, stages, feedback, ownership and exit points.
Part of our guide: How Much Does a Small Business Website Redesign Cost in the UK?
It is normal to pay a web designer a deposit or first milestone before seeing the finished design, because research and design are paid professional work. The safer question is not whether any money comes first, but what the agreement promises, what you will review at each stage and how both parties can respond if the direction is wrong.
Some build-first or speculative models show a meaningful concept before full commitment. They can reduce one kind of uncertainty, but their limits and ownership still need to be clear.
Why designers request payment upfront
A deposit reserves time and demonstrates commitment. The designer may begin discovery, research, content planning and structural work before a polished visual appears.
Requiring all creative labour without payment would transfer the project’s risk entirely to the supplier. Established professionals usually use deposits or staged invoices instead.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
A deposit is not payment for nothing
The contract should connect the first payment to defined work. This may include onboarding, workshops, audit, sitemap, wireframes or an initial design direction.
Ask when each deliverable will appear and what happens after review. Avoid paying against labels that neither party can explain.
Keep invoices and approvals with the project record.
Common payment structures
Projects may use an initial deposit with a final balance, equal staged payments or invoices tied to deliverables. Longer work may be billed monthly.
No structure is universally safest. Milestones are helpful when each stage has understandable acceptance criteria.
Very small projects may reasonably require full payment, while a large build normally deserves more stages.
Check the supplier before paying
Verify the legal trading identity, contact details and relevant work. Review live sites, not only portfolio pictures.
Ask for references where the investment or risk is substantial. Check that the invoice and contract name the same entity.
Research reduces risk but cannot replace a clear agreement.
Read the scope
The scope should describe pages, templates, content, functions, integrations, testing and launch work. It should also state client responsibilities and exclusions.
A promise to design a website can mean anything from one concept to a complete tested build. Clarify quantities and definitions before payment.
The proposal comparison guide helps identify common gaps.
Understand the design process
Ask what you will see first: research findings, wireframes, a visual direction, a prototype or a working page. Each answers different questions.
Confirm when real content is used and how mobile layouts are considered. One desktop homepage image is not the entire experience.
Know which decisions become fixed after approval.
Agree feedback and revisions
Record the number and type of revision rounds. Ask what counts as a round and how feedback should be consolidated.
Revisions normally refine an agreed direction. A complete change in business strategy may require new scope.
Give specific feedback connected to audience, content and requirements rather than unexplained preference.
Use meaningful milestones
A useful milestone marks completed value, such as approved structure, agreed design system, working templates or tested launch.
Avoid schedules based only on dates when essential inputs are missing. Deliverables should be inspectable before the next significant payment.
The designer should also receive prompt payment when the agreed milestone is met.
Clarify cancellation
The contract should explain notice, work completed, outstanding invoices and delivery of paid-for material. Understand whether the deposit is refundable and in which circumstances.
A non-refundable reservation fee may be reasonable when capacity has been held, subject to applicable contract and consumer rules.
Seek appropriate legal advice for your circumstances rather than relying on a general article.
Clarify ownership
Ask when rights in designs, code and content transfer. Suppliers commonly retain ownership until invoices are paid.
Identify third-party fonts, themes, stock images and software that are licensed rather than transferred. Confirm ongoing fees.
Ensure the business owns or controls the domain, data and core service accounts.
Protect account access
Do not hand over sole control of the domain or business email. Give the supplier appropriate access while retaining an administrator and recovery route.
Create project-specific accounts where practical and remove obsolete access later. Never send passwords in insecure documents.
Practical control matters as much as contractual wording.
Distinguish concept work from production
A visual concept may demonstrate style and hierarchy but not include responsive behaviour, accessibility, content migration, integrations or browser testing.
A working preview may provide more evidence but can still be incomplete. Ask what has and has not been built.
Base payment decisions on the named stage, not assumptions created by an impressive screen.
Speculative design models
Some suppliers create an initial proposed improvement before asking for full commitment. This can help a business assess thinking and direction.
The supplier must explain how much is complete, whether the preview is reusable and what further work costs. It should not imply that a concept is a launch-ready website.
Afterworks explains its own model in what a speculative website redesign is.
Unpaid speculative pitches
Traditional competitive pitches may ask several agencies for free creative work. This can favour suppliers able to absorb the cost and encourage attractive assumptions before discovery.
If original design thinking is central to selection, consider a paid discovery or concept stage for shortlisted teams.
Respect intellectual property in unsuccessful proposals.
When paying in full upfront may be reasonable
A small fixed product, short consultation or established standard package may require advance payment. The lower scope and clear deliverable can make that proportionate.
Check refund and scheduling terms. Use a payment method that provides appropriate records and protection.
For a large bespoke project, staged payments usually align risk and progress more clearly.
When to be cautious
Pause when the supplier refuses a written scope, demands an unusually large irreversible payment or cannot identify the trading entity. Vague ownership and pressure to pay immediately are also concerns.
Other warning signs include guaranteed rankings, copied portfolio work and payment to unrelated personal accounts without explanation.
One concern may have an innocent answer. Ask and document it.
Do not use withheld payment as routine leverage
Once agreed work is delivered, withholding payment to obtain extra scope damages the relationship and may breach the contract.
Raise quality or scope concerns through the documented acceptance process. Identify the specific requirement and proposed remedy.
Fair protection works for both client and supplier.
Approving a design is not the end
The site still needs content, development, accessibility, performance, forms, migration and testing. Keep later payments connected to later evidence.
Use pre-launch checks before approving launch. Inspect the public site after deployment as well.
Do not release the final payment merely because one visual mockup looks finished if the contract covers a working site.
Questions before the first payment
- Which work does this invoice start or complete?
- What will I see next and when?
- How is feedback handled?
- What is excluded?
- What happens if either party cancels?
- When does ownership transfer?
- Which licences or recurring fees remain?
- Who controls the domain and accounts?
Clear answers should appear in the proposal or contract.
Keep decisions in writing
Meeting notes, approved deliverables and change requests should be recorded. This prevents memory differences and helps new stakeholders understand the project.
Email confirmation can be useful, but substantial scope changes should update the formal agreement.
Documentation should support collaboration rather than create unnecessary bureaucracy.
Consider escrow for unusual risk
Escrow or platform milestone services can hold funds until agreed conditions are met. They may help with unfamiliar remote suppliers or marketplace projects.
Review fees and dispute rules. Escrow does not define a good deliverable by itself.
Most established direct relationships can use ordinary contracts and staged invoices.
Budget for client responsibilities
The project may depend on timely content, photographs, access and approvals. Delays can reserve supplier capacity or extend the schedule.
Understand charges for paused work and remobilisation. Name one person to consolidate feedback.
The payment plan works best when the client can meet its own milestones.
Frequently asked questions
What percentage deposit is normal?
Practices vary with project size, duration and supplier. Evaluate the amount against reserved capacity, early work and remaining milestones rather than relying on one universal percentage.
Should I pay before signing a contract?
No substantial custom project should begin without written terms that identify the parties, work, price and responsibilities.
What if I dislike the first design?
Use the agreed feedback process and explain how it misses the brief. The contract should state revision and cancellation options.
Can I keep rejected concepts?
Not automatically. Rights depend on the agreement and payment. Ask before reusing any concept.
Is a working preview safer than a mockup?
It can provide more evidence, but check what remains incomplete. Neither format replaces scope, testing and ownership terms.
Pay against clarity and progress
Upfront payment is reasonable when it starts defined professional work within a balanced agreement. Verify the supplier, understand each stage and release later payments against meaningful evidence.
Afterworks offers a build-first speculative redesign so businesses can see a meaningful proposed improvement before choosing whether to make the full commitment.
