Web Design Kill Fees: Getting Paid When a Client Cancels Mid-Project
Price a web design kill fee by project phase and write a termination clause that's easier to defend if a client cancels or disputes the charge.
Photo: Pixabay
On this page 7 sections
- A Deposit Protects Your Calendar, Not Your Mid-Project Work
- Build the Web Design Kill Fee From Project Phases
- The Penalty Rule Most Kill Fee Advice Gets Wrong
- What Your Termination Clause Should Say
- Invoice Before You Charge a Card on File
- How Visa and Mastercard Treat a Disputed Kill Fee
- Hand Over the Work Once the Balance Clears
A web design kill fee is what a client owes you when they end a project before it's finished. The kill fee most likely to survive a challenge charges full price for each completed phase and your hourly rate for the phase in progress. Anything the client has already paid comes off the total. Put that formula in your termination clause, have the client sign off on it separately, and send an invoice before you charge any card on file.
Web projects need this more than most service work because your costs come early. If a client cancels a ten-week build at week six, you're left with weeks of design and development nobody has paid for. You've also got a hole in a calendar you kept open by turning down other jobs. Whether a contract can be enforced depends on state law. This article is general information, not legal advice, so have an attorney review your termination language before you rely on it.
A Deposit Protects Your Calendar, Not Your Mid-Project Work
Many agencies treat the deposit as their kill fee. The two overlap, but they cover different risks.
| Deposit | Kill Fee | |
|---|---|---|
| When it's paid | Before work starts | When the client terminates |
| What it covers | Reserved schedule and early discovery | Work delivered beyond the deposit |
| How it's set | Fixed amount or share of the total | Completed phases plus current-phase hours |
| Where it fails | Too small for a late cancellation | Challenged as a penalty or "services not rendered" |
A non-refundable deposit does its job when a client walks away during discovery. Once you're deep into development, it no longer covers what you've built. If your upfront terms need work, start with deposit and milestone payment terms for web design. A kill fee uses the same phase structure.
Build the Web Design Kill Fee From Project Phases
Price each phase separately and tie it to a deliverable the client can see. Most builds have four:
- Discovery and strategy: the sitemap and technical requirements
- Design: wireframes and template mockups through the agreed revision rounds
- Development: the build itself on a staging site, including CMS setup
- Launch and QA: testing and content load through DNS cutover
The kill fee adds up every finished phase at full price. The phase in progress is billed at your stated hourly rate, capped at that phase's price. Approved change orders count as earned work, so give each one its own line the client will recognize. Our guide to documenting change orders so they hold up shows how to record them.
Worked Example: Flat Percentage vs. Phase-Based Fee
These numbers are illustrative. Assume a $12,000 project with discovery and launch at $1,500 each. Design costs $4,000 and development $5,000. The contract hourly rate is $125. For comparison, a different contract charges a flat 50% ($6,000) on any cancellation.
| Client cancels... | Phase-based fee | Flat 50% fee |
|---|---|---|
| Day 3 of discovery, 6 hours logged | $750 | $6,000 |
| After design approval, before development | $5,500 | $6,000 |
| Midway through development, 16 hours logged | $7,500 | $6,000 |
| During launch QA, 8 hours logged | $11,500 | $6,000 |
In the first week, the flat fee charges eight times what you've earned. At the end, when nearly all the work is done, it leaves you $5,500 short. An issuer or a judge can follow the phase-based column line by line, and each line has a timesheet or a deliverable behind it.
Where the Deposit and a Capacity Fee Fit
Take the mid-development row and assume the client paid a $3,000 deposit at kickoff. Earned work is $1,500 + $4,000 + $2,000 = $7,500. Credit the $3,000 deposit and the balance due is $4,500.
Some agencies add a capacity fee for booked weeks they can't fill on short notice. An illustrative $1,000 capacity fee would raise the balance to $5,500. That line is the hardest to defend, for the reason in the next section. Keep it modest and tie it to the weeks you actually blocked off. The contract should say what it pays for.
The deposit in the day-3 row raises the same issue. Keeping $3,000 against $750 of logged work is defensible only if the contract says the deposit pays for reserving your schedule.
The Penalty Rule Most Kill Fee Advice Gets Wrong
Courts generally won't enforce a contract penalty. The Restatement (Second) of Contracts § 356, quoted in Lexology's comparison of liquidated damages rules, allows damages to be fixed in advance "only at an amount that is reasonable in the light of the anticipated or actual loss caused by the breach and the difficulties of proof of loss." An unreasonably large amount is unenforceable as a penalty. The Restatement isn't a statute. Courts in many states rely on it, but your state's case law is what decides the question.
Two points get lost here. First, a client who ends the project under your termination clause hasn't necessarily breached the contract. They used a right you gave them. When the fee pays for work you've already delivered at prices the client agreed to, it looks more like the contract price than like estimated damages. That's why the phase-based structure is the safer one. Second, labeling a fee "liquidated damages, not a penalty" doesn't settle anything. Courts look at whether the amount is reasonable, not at what you called it.
The weak spot is any charge for work you haven't done. Flat percentages and capacity fees both fall into that category. So does a large non-refundable deposit with little work behind it. Those are the amounts a court may test against your real loss. States apply that test with different strictness, so go over this part with your attorney.
What Your Termination Clause Should Say
Your web design kill fee is easiest to defend when the client clearly agreed to it before any work began. The termination clause should cover these points:
- Notice: who can terminate and how (written notice to a named contact), plus the date work and billing stop
- Fee formula: completed phases at full price plus current-phase hours at a stated rate, with approved change orders listed separately
- Capacity fee: if you charge one, the amount and the reserved weeks it pays for
- Deposit treatment: whether it's credited against earned work or kept as a scheduling fee
- Payment terms: when the final invoice is due and the payment methods you accept
- Card-on-file consent: explicit permission to charge a stored card for amounts due under the clause, with the calculation spelled out
- Handover: deliverables and intellectual property transfer once the balance is paid
- Your own exit: your right to terminate if the client goes silent for a set period or misses a milestone payment
Get a signature on the full contract. Then get a separate acknowledgment of the cancellation terms, such as initials beside the clause or a dedicated checkbox in your e-signature tool. If the charge is ever disputed, that record is your first exhibit.
Invoice Before You Charge a Card on File
Send an itemized termination invoice first, even if your contract authorizes a charge to a stored card. Show each phase with its hours, subtract the credits, and attach the termination clause with a due date. Clients are far more likely to dispute a charge that surprises them than one they saw coming.
Charging a saved card later counts as a merchant-initiated transaction under the card networks' stored-credential rules. Moneris's overview of Visa's framework explains that "prior to storing credentials for future use, merchants must establish a consent agreement with the cardholder." Visa's own developer documentation on credentialed transactions makes the same point: you need the customer's consent to store their card before you run a merchant-initiated charge on it. Later charges also carry data linking them to the first transaction. For Visa, the Merchant Risk Council notes that this is the Network Transaction ID.
A kill fee calculated under a clause the client initialed fits that model. A surprise charge does not. Confirm the current requirements with your processor, and ask how its virtual terminal for keyed and card-on-file payments sets the stored-credential indicators.
A lower-risk route is a payment link the client pays themselves. When the client completes the payment on their own, that's strong evidence they accepted the charge. ACH can cost less on a large balance, but it depends on the client's cooperation. If you pass card costs on to clients, read the compliance points in passing card fees to clients on large web design invoices first.
How Visa and Mastercard Treat a Disputed Kill Fee
A client who disputes a kill fee usually makes one of two claims. The first is "I canceled, so I shouldn't be charged." On Visa, that falls under dispute condition 13.7, Cancelled Merchandise/Services, and your best evidence is a cancellation policy the client accepted when they signed on. Visa's Updates and Clarifications to Dispute Rule Language says an issuer must wait 15 calendar days from the date the merchandise was returned or services were cancelled before filing. The one exception: the wait doesn't apply if it would push the dispute past its time limit. Use that window to talk to the client.
The second claim is "the work was never delivered." Your answer is that you were willing and able to finish, and the client stopped the project, not you. Delivery records for completed phases make that case. On Mastercard, both complaints usually land under reason code 4853, Cardholder Dispute. Chargeflow's Mastercard reason code guide calls 4853 "Mastercard's broadest cardholder-dispute code" and maps the older 4855 Goods or Services Not Provided code to it. The same evidence answers both.
Your processor's response deadline is usually tighter than the network's own window, so start work the day the notice arrives. Build one package that answers either claim:
- Signed contract, with the termination clause highlighted and the client's separate acknowledgment
- The client's dated cancellation notice
- The itemized termination invoice and proof you sent it before charging
- Timesheets or project-management logs for the phase in progress
- Delivery records for completed files, such as access logs or download confirmations
- Messages where the client approved mockups or staging builds
Put a one-page summary on top that points to each exhibit. Make sure your billing descriptor names your agency in a way the client will recognize. For more on structuring the response, see winning web design chargeback disputes.
Hand Over the Work Once the Balance Clears
The handoff affects both your reputation and your dispute position. A client who received the files they paid for has a weak "services not rendered" claim. Once payment clears, send the discovery documents along with the approved design files and their exported assets. For finished development, include a site or code export. Then add credentials for any accounts created in the client's name and a short status summary. Use a channel that logs delivery, and keep copies.
Domains and hosting registered to the client were never yours to hold back, and neither is content the client supplied. Withholding them to pressure a client can create legal exposure and weaken your dispute file. Whether you can take down an unpaid client's site covers where that line usually falls.
Before your next proposal goes out, test your current contract against the four cancellation points in the example table. If any row gives a number you couldn't explain to an issuer, rewrite the clause before you send the proposal. If you're also reviewing how you take keyed and online payments, MannyPay works with web design agencies and freelancers on card-on-file processing and gateways. Request a free processing quote and a MannyPay specialist will respond within one business day.
Sources
- Visa: Updates and Clarifications to Dispute Rule Language
- Moneris: Visa Stored Credential Transaction Framework Overview
- Visa Acceptance (Cybersource) Developer Center: Credentialed Transactions
- Merchant Risk Council: Card-on-File Done Right: How to Stay Compliant with the Stored Credential Mandate
- Chargeflow: Mastercard Chargeback Reason Codes
- Lexology: Liquidated Damages and Penalty Clauses: A Civil Law Versus Common Law Comparison (quotes Restatement (Second) of Contracts § 356)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
