Web Design Payment Terms: How Freelancers Get Paid on Time

Set your web design payment terms before you write a single pixel: 40 to 50 percent upfront, the rest tied to milestones you can point at, and a final payment due before the site goes live. Put it in the contract, state the late fee in plain numbers, and never hand over the final files until the last invoice is paid. Do this and most "client paying late" stories simply do not happen to you.

The problem: you did the work, now you are the debt collector

Here is how it usually goes. You agree on a price over a friendly call. The client says "send me the invoice when it is done." You build the site, make three rounds of revisions, and launch on a Thursday. The client is thrilled. Then the invoice sits in their inbox for five weeks.

You send a polite nudge. Then a less polite one. The client replies that their accountant is on holiday, or that they "thought this was included in the retainer", or nothing at all. Meanwhile the site is live, you have no leverage left, and you are spending Sunday evening drafting a sentence like "just checking in on the invoice" for the third time.

The pattern behind it is almost always the same:

• No deposit, so the client has no skin in the game when the project starts.
• A single invoice at the very end, so all of your risk sits in one lump.
• Vague terms like "payment on completion", where "completion" is whatever the client says it is.
• Feedback that drags on for weeks, so "done" keeps moving.
• Files and hosting access handed over before the final payment cleared.

None of this makes your client a bad person. Most late payment is not malice, it is a lack of structure. If the structure does not say when money is due, people pay when it is convenient for them. Your job is to make "on time" the easy default.

The 7 steps at a glance

1. Decide your payment structure (deposit, milestones, final payment).
2. Set the deposit and make it non-refundable once work starts.
3. Tie milestone payments to deliverables, not to dates.
4. Define "done" so the final payment cannot be postponed forever.
5. Write net terms and late fees into the contract and onto every invoice.
6. Keep ownership of the files until the final invoice is paid.
7. Follow up on a fixed schedule, without drama.

Step 1 to 3: Build a structure that protects you

Pick a payment structure that matches the project size

For small projects (a landing page, a one-page site), a 50/50 split works well. Half before you start, half before launch. For mid-sized projects, three payments are cleaner: 40 percent upfront, 30 percent at design approval, 30 percent before launch. For large projects over several months, break it into four or more milestones so you are never more than a few weeks of work ahead of your cash.

The rule of thumb: you should never be owed more than you would be willing to lose. If a single missed payment would hurt your month, your structure is too back-loaded.

Make the deposit meaningful and non-refundable

A deposit of 30 to 50 percent does two jobs. It covers your first stretch of work, and it filters out clients who are not serious. A client who pays a deposit has made a decision. A client who will not pay one is telling you something about how the rest of the project will go.

State clearly in your contract that the deposit is non-refundable once work begins, because it covers the time you reserved for them (which you could have sold to someone else). This is standard, fair, and easy to explain. If you want a refund clause for the period before kickoff, add a short window, for example 48 hours after signing.

If you are unsure what the total should be in the first place, our guide on how to price web design projects walks through it.

Tie milestones to deliverables, not calendar dates

"Second payment due on 15 March" sounds clear, but it falls apart the moment the client takes two weeks to send content. Dates reward the party who delays.

Tie payments to events instead: "Second payment is due when the homepage design is delivered for review." Now the invoice goes out when you finish, and the clock starts when you deliver. If the client is slow, that is their delay, not a hole in your cash flow.

Good milestone triggers are things you can show:

• Contract signed and deposit received (project starts).
• Design concepts delivered for review.
• Staging site delivered for review.
• Final approval received (launch invoice).

A shared review link with timestamped, pinned comments makes the second and third milestones easy to prove. When a client approves a design inside a feedback tool, you have a dated record of exactly what they signed off on. That is much harder to argue with than "I think we agreed on that on a call."

Step 4 and 5: Define "done" and write the terms down

Define done before you start

"Payment on completion" is the single most dangerous phrase in freelance contracts. Completion of what, and who decides? Here is wording that closes the gap:

"The final payment is due upon delivery of the site for final review, or 14 days after delivery of the final version, whichever comes first. Payment is required before launch and before transfer of source files and hosting access."

Two things happen here. The client cannot stall the final invoice by dragging out feedback, and the launch itself becomes the thing they are waiting for. Nobody wants a finished site sitting offline because of an unpaid invoice.

To keep the revision phase from stretching, set a fixed number of revision rounds in the contract and a feedback deadline per round. We cover that in detail in how to manage the web design revision process.

Write net terms and late fees into the contract

Net 14 is a good default for freelancers working with small businesses. Net 30 is common with larger companies, but longer terms mean you finance their project. If a client insists on net 30 or net 60, build that into your price or ask for a larger deposit.

Late fees do not need to be aggressive. A typical clause: "Invoices unpaid after the due date accrue a late fee of 1.5 percent per month." In many European countries you also have statutory interest rights for commercial late payment, so check what applies where you and your client are based. Not legal advice, just a flag to look it up.

Then repeat the terms where people actually look: on the invoice itself. Include the due date as a date, not as "net 14". Include the payment method, the amount, and the late fee in one line. If your contract is the rulebook, the invoice is the scoreboard. For a full breakdown of the clauses that matter, see our web design contract template guide.

Step 6 and 7: Keep leverage and follow up like a professional

Hold the files until the last invoice is paid

This is not about being petty. It is about timing. Until the final invoice is paid, you keep control of: the source files and design files, the production deployment or the transfer of hosting and domain access, and any licensed assets (fonts, stock images, plugins) transferred in your name.

Say so in the contract: "Ownership of the final deliverables transfers to the client upon receipt of full payment." Most clients never think twice about this because it is what everyone expects. The ones who do push back are the ones you needed this clause for.

A practical tip: build and review on a staging link you control, and only move to the client's live environment once the final payment arrives. See our notes on staging site best practices for how to set this up.

Follow up on a schedule, not on a mood

Most freelancers chase payments emotionally. They wait until they are annoyed, then send something too sharp, or they stay quiet because it feels awkward. Replace that with a fixed schedule:

• Day 0: invoice sent with the due date visible.
• Day -3: friendly reminder before the due date.
• Day +1: short note that the invoice is now overdue, with the invoice attached again.
• Day +7: firm reminder that references the late fee in the contract.
• Day +14: call or message, pause work on any other open tasks, and stop all new deliverables.

Here is a template for the Day +1 message that works without sounding cold:

"Hi Anna, a quick note that invoice 2026-014 was due yesterday. I have attached it again for convenience. If something is blocking payment on your side, let me know and we will sort it out. Thanks!"

No guilt, no sarcasm, no emoji parade. Just facts and an invitation to talk. If you want more of these scripts, our client communication templates cover payment reminders and the awkward moments around them.

Real-world example: Maya and the restaurant website

Maya is a freelance web designer who builds sites for small hospitality businesses. Her first year, she worked with "pay when it is done" and a handshake. On a restaurant project worth 3,200 euros, she delivered the site, the owner loved it, and then paid in two parts: 1,000 euros after five weeks, and the remaining 2,200 euros after another eleven weeks. She followed up seven times. The project cost her roughly 20 hours of unpaid chasing on top of the build.

The next year she changed three things. She required a 40 percent deposit before kickoff. She tied the second payment (30 percent) to delivery of the design for review, and the third (30 percent) to final approval, due before launch. And she moved all review to a shared link where the client left pinned comments directly on the staging site, so the approval was recorded and dated.

On her next comparable project (a 3,500 euro café site), the deposit arrived the same week as the signed contract. The design milestone invoice was paid within four days. The client approved the final version on a Tuesday through the review link, the last invoice went out that afternoon, and it was paid on Friday. Total chasing: one reminder, sent three days before the due date. The project was not smaller or easier. The structure was just better.

Bottom line

Good payment terms are not about distrust, they are about clarity. Take a deposit, tie payments to deliverables, define what "done" means, put late fees in writing, and keep the final files until the last invoice is paid. Do that consistently and you will spend your time designing, not chasing.

FAQ

What are good web design payment terms for freelancers?

A common standard is 40 to 50 percent upfront, one or two milestone payments tied to deliverables, and the final payment due before launch. Use net 14 on every invoice and state late fees in the contract. This keeps your exposure small and your cash flow steady.

How much deposit should a freelance web designer ask for?

Between 30 and 50 percent for most projects. Smaller projects often use 50 percent, since the total is low and the risk is relatively high. Larger projects can use 30 to 40 percent paired with several milestones. Whatever you pick, make the deposit due before work starts.

Should the deposit be refundable?

Generally no, once work has begun. The deposit pays for the time you set aside for the client. If you want to be fair, allow a short cancellation window right after signing, such as 48 hours, and make the deposit non-refundable after that.

What should I do if a client does not pay my web design invoice?

Follow a fixed reminder schedule: a friendly reminder before the due date, a note the day after, a firmer message after a week referencing the late fee, and a call after two weeks. Pause further work and hold back final files and hosting access until payment arrives. If it goes beyond that, send a formal demand letter before considering legal steps.

Is it okay to hold a website hostage until the client pays?

It is legitimate to withhold final deliverables, launch, and transfer of ownership until payment, as long as your contract says so. Do not take down a live site the client already paid for, and do not sabotage anything. Retaining files you have not yet been paid for is a very different thing from deleting work.

Should I charge a late fee on web design invoices?

Yes, if it is stated in your contract and on the invoice. A modest fee such as 1.5 percent per month is common. Check the rules for commercial late payment where you and your client are based, because statutory interest may apply even without a clause.

What is a good payment structure for a web design project?

For a mid-sized project, 40 percent at signing, 30 percent when the design is delivered for review, and 30 percent before launch works well. For smaller projects, a simple 50/50 split is usually enough. The principle is that you never get ahead of your money by more than a few weeks.

How do I make sure the final payment is not delayed by endless feedback?

Define "done" in the contract: a fixed number of revision rounds, a deadline for each round, and a rule that the final invoice is due on approval or a fixed number of days after the final version is delivered. Collect all feedback in one place, with dated comments, so everyone can see what was approved and when.

Get clean, dated approvals that back up your invoices. [Try dotts free →](https://dotts.se)

Further reading

• How to Price Web Design Projects as a Freelancer (Without Guessing)
• Web Design Contract Template for Freelancers: What to Include and Why
• Scope Creep in Web Design: How Freelancers Stop It
• How to Get Client Sign-Off on a Website: A Freelancer's Complete Guide