A web designer asking for money before starting is not automatically a red flag.
The more useful question is: how much risk are you taking with that payment, and what exactly happens after you make it?
There is no magic deposit percentage that makes a website project safe. A 30% deposit attached to a vague promise can be worse than a 50% deposit attached to a clear scope, credible provider, defined first milestone and written cancellation terms.
For a substantial custom website, I generally prefer a payment structure where money moves as the project moves. You should be able to point to what each payment starts, completes or unlocks.
What is the upfront payment actually paying for?
A professional website has work before there is anything impressive to click.
That can include:
- discovery and requirements
- sitemap and content planning
- technical decisions
- account setup
- wireframes or design direction
- reserving production time
- initial design and development
So the existence of a deposit is not the problem.
The problem is paying a meaningful amount when neither side can clearly explain what the project is, what the first phase contains, or what happens if the relationship stops.
Before you pay, ask one simple question:
“What will be true after this payment that is not true today?”
A good answer sounds like a project milestone. A weak answer sounds like “we will start working on it.”
Is 50% upfront normal for web design?
It can be reasonable, but the percentage alone tells you very little.
Imagine two projects.
A designer is building a tightly scoped five-page business website over three weeks. Half upfront and half when the agreed site is ready for launch may be simple enough for both sides.
Now imagine a custom platform that will take four months, includes authentication, payments, dashboards and several approval stages. Paying half of a much larger budget before the first meaningful checkpoint creates a very different risk profile.
The bigger and longer the project becomes, the more useful milestone billing becomes.
Instead of asking whether 50% is normal, ask:
- How large is the amount in real money?
- How long until I can inspect meaningful work?
- What deliverable triggers the next payment?
- What happens if the project stops halfway?
- What do I receive for work already paid for?
Those questions reveal more than the percentage.
A milestone should describe something you can inspect
“Development phase: 30%” is not a useful milestone by itself.
You need to know what development completion means.
For example, a website project might be structured around checkpoints such as:
| Stage | What you should be able to verify |
|---|---|
| Start | Signed scope, responsibilities, timeline and project setup |
| Design approval | Agreed key page designs or design system available for review |
| Development review | Agreed pages and functions working on a staging site |
| Launch readiness | Testing complete, agreed content loaded and known issues documented |
| Handoff | Ownership/access transferred and agreed documentation delivered |
The percentages can vary. The important part is that the trigger is observable.
This protects the designer too. It prevents a client from treating a completed phase as unfinished simply because they have changed their mind about the scope.
Do not pay a deposit before you know the full price model
A deposit is only one number.
Before paying it, understand the rest of the commercial structure:
- total fixed price or hourly/day rate
- what is included
- what counts as additional work
- how revisions work
- third-party costs such as hosting, licences or software
- when each later payment becomes due
- whether tax is included
- what maintenance costs after launch
A ₦300,000 deposit on a clearly defined ₦1,000,000 project means something very different from “₦300,000 to start, final cost depends on what we discover.”
The second model can still be legitimate, especially for uncertain technical work, but then you need a budget ceiling, discovery phase or another mechanism for controlling open-ended cost.
If you are still comparing quotations, read what a web design proposal should include before you pay. The proposal should make the payment schedule easier to understand, not create more questions.
What should be in writing before money moves?
At minimum, I would want these points clear:
1. Scope
Which pages, templates, features and integrations are included?
“Professional business website” is not a scope.
2. Payment triggers
What causes invoice two or invoice three to become due?
Tie payments to understandable project events where practical.
3. Timeline and client dependencies
A delivery date means little if nobody has said when the client must provide copy, images, approvals or access.
4. Changes and revisions
How many review rounds are included? What happens when the request is genuinely new scope rather than a correction?
5. Cancellation and refund terms
Do not assume “deposit” automatically means refundable or non-refundable. The agreement should say what happens if you cancel, if the provider cancels, or if work has already begun.
For Nigerian buyers, the Federal Competition and Consumer Protection Commission publishes consumer-rights guidance and a complaint process for dissatisfaction with goods or services. That does not replace a project-specific contract, but it is another reason to keep agreements, receipts and correspondence rather than relying on verbal promises.
Sources: https://fccpc.gov.ng/consumers/consumer-rights-responsibilities/rights-responsibilities/ and https://fccpc.gov.ng/consumers/complaint-handling/
6. Ownership and handoff
What happens to the domain, hosting, website admin, source code, analytics and other accounts after payment?
Payment and ownership are related, but they are not the same question.
My guide to who should own your website, domain, hosting and code goes deeper into this.
When 100% upfront deserves more scrutiny
Full upfront payment is not automatically wrong.
A small productised website package, template setup or one-day engagement may use full payment because the job is short and standardized. The provider may also have enough reputation that buyers accept those terms.
But for a substantial custom build, 100% upfront means the client has paid the entire commercial consideration before seeing the project progress through its major checkpoints.
That deserves a stronger answer to questions such as:
- Why is full payment required?
- What happens if delivery is materially late?
- What happens if the project is cancelled?
- What evidence exists that this provider reliably delivers comparable work?
- Is the exact scope written down?
- Which assets and accounts are already controlled by the business?
The US Federal Trade Commission’s consumer guidance for contractor work warns against paying for everything upfront and recommends written estimates and contracts. Web design is a different service category, so I would not mechanically apply construction rules to software or design work. The underlying risk principle is still useful: large advance payments deserve clear documentation and a credible delivery process.
Source: https://consumer.ftc.gov/articles/how-avoid-home-improvement-scam
A very low deposit is not proof that a project is safe
Buyers sometimes treat a small initial payment as protection.
It only limits the amount at risk on day one.
You can still lose time, miss a launch, end up with unusable work, discover that your domain sits in somebody else’s account, or make several small payments without ever reaching a usable outcome.
Evaluate the whole delivery system:
scope → payment → deliverable → review → next payment → launch → handoff.
That sequence matters more than whether the first invoice happens to be 20%, 30% or 50%.
The safest payment schedule is understandable without the designer explaining it
A business owner should be able to open the agreement later and answer:
- How much is the project?
- What have I paid?
- What has been delivered?
- What is due next?
- What event makes it due?
- What happens if either side stops?
- What do I own when the project is complete?
If those answers are difficult to find before you pay, fix the agreement before fixing the website.
The bottom line
Yes, it is normal for a web designer to want commitment before reserving time and starting work.
But do not judge a deposit by percentage alone.
Judge it by clarity, proportional risk and project progress.
For a small defined job, a simple upfront/final split may be perfectly sensible. For a larger custom build, milestone payments can keep money closer to observable progress. In either case, the scope, payment triggers, cancellation terms and ownership should exist in writing before meaningful money changes hands.
If you are currently comparing providers, use my web design proposal checklist alongside the questions to ask before hiring a web designer. If you want a website project structured around clear scope, ownership and handoff, see my web design service or contact me.
