Web Design Deposit and Milestone Payment Terms That Get You Paid
Set a web design deposit and milestone payment terms clients won't dispute, then collect every payment by card or ACH and protect your final invoice.
Photo: Pixabay
On this page 7 sections
- Why Every Website Project Needs a Web Design Deposit
- 50/50 vs. Thirds vs. Milestone Schedules: Which Fits Your Project Size
- Tying Milestone Payments to Deliverables Clients Can't Dispute
- Collecting Deposits by Card, ACH, or Invoice Link
- Refundable vs. Non-Refundable Deposits in Your Web Design Payment Terms
- What to Do When a Client Stalls Before the Final Payment
- Next Steps: Getting Your Payment Setup in Place
Key takeaways
- Match your schedule to project size: 50/50 for small builds, thirds for mid-size projects, and deliverable-based milestones for large or long projects.
- Tie each payment to a written client approval, not to a date or a vague "phase."
- Collect payments through hosted invoice links or a virtual terminal, and get written authorization for any card kept on file.
- Collect the final payment before launch on the client's domain, and keep your contract and records strong enough to hold up in a chargeback.
Many website projects that end in an unpaid invoice don't start with a bad client. They start with loose payment terms: no clear web design deposit, vague milestones and a final payment that depends on goodwill.
The site sits finished on staging, the client goes quiet, and the agency has already spent weeks of design and development time it can't recover. This guide covers deposit structures for different project sizes, milestone triggers that hold up when a client pushes back, and how to collect each payment by card or ACH so it actually clears.
Why Every Website Project Needs a Web Design Deposit
Web design front-loads your labor. Discovery, sitemap planning, wireframes and first design concepts all happen before the client has anything usable. If the project stops there, you've done much of the thinking and the client has paid nothing.
A deposit does three jobs:
- It covers early work. Discovery and design time are real costs, even if the project never launches.
- It confirms commitment. Clients who pay to reserve a spot in your schedule tend to answer emails, deliver content and show up for review calls.
- It holds your calendar. When you turn down other work to start a project on a set date, the deposit pays you for that slot.
A deposit also sets the tone. When an agency starts work before payment, the client learns that deadlines are flexible. When an agency waits for the deposit to clear, the client learns the terms are real.
50/50 vs. Thirds vs. Milestone Schedules: Which Fits Your Project Size
No single schedule fits every project. The structures below are common starting points, not industry benchmarks. Adjust them to your costs, your client base and the length of the build.
| Schedule | Typical Fit | How It Splits | Main Risk |
|---|---|---|---|
| 50/50 | Small brochure sites, landing pages, short timelines | Half to start, half before launch | Half your fee depends on the client returning at the end |
| Thirds | Mid-size sites with distinct design and development phases | Start / design approval / pre-launch | The final third can stall if content arrives late |
| Milestone-based | Large builds, e-commerce, custom functionality, long timelines | A deposit plus payments at defined deliverables | More invoices to manage, and you need clear acceptance terms |
How Much Deposit for a Website Project?
As an illustrative guide:
- Small projects: A 50% deposit is a common choice. A 50/50 web design payment structure is easy to explain, and on a small project the balance at risk is manageable.
- Mid-size projects: A deposit of roughly one-third, or a slightly larger first payment such as 40/30/30, covers discovery and design work.
- Large projects: A smaller percentage deposit (say, 25–30%) followed by several milestone payments keeps any single invoice from becoming a sticking point. With larger sums at stake, it pays to bill more often.
Illustrative example: On a $6,000 brochure site, a 50/50 split means $3,000 to start and $3,000 before launch. On a $24,000 e-commerce build, a milestone schedule could look like this: a $6,000 deposit, $6,000 at design approval, $6,000 at staging handoff and $6,000 before go-live. The difference shows up at the end. On the larger project, you're waiting on one-quarter of the fee at launch, not half.
Ongoing maintenance, hosting and care plans are a separate matter. Bill them as recurring payments, not as part of the build schedule. For setup guidance, see our guide to subscription and membership payment processing.
Tying Milestone Payments to Deliverables Clients Can't Dispute
Milestone payments in web design work best when each payment is triggered by an event the client confirms in writing. Avoid triggers like "end of month two" or "design phase complete." Clients can argue with those.
Strong milestone triggers for website projects:
- Signed proposal and deposit received. Work begins only after both are in hand.
- Sitemap and wireframes approved. The client signs off on the structure and page list.
- Design comps approved. The homepage and key interior templates are approved after the agreed number of revision rounds.
- Staging site delivered. A functional build is live on a staging URL and ready for client review.
- Launch approved. The client confirms the site is ready to go live, and the final payment is due before any DNS changes.
Build Approvals Into Your Process
- Set an acceptance window. State that a deliverable counts as approved if the client doesn't send written feedback within a set number of business days. Choose a window that suits your clients and your contract.
- Cap revision rounds. Specify how many rounds each milestone includes. Extra rounds become billable change orders.
- Separate client-caused delays. A frequent reason a site stalls on staging is that the client hasn't delivered copy, photos or product data. Your contract should state that when client content is late, the milestone payment comes due on the original schedule or after a set delay, even if the site can't launch yet.
- Document every scope change. New pages, extra integrations or a new plugin requirement should get a written change order, with its own price and payment terms, before you do the work.
This documentation also protects you if a client later disputes a card payment. Signed approvals, dated emails and staging links are the evidence that the work was delivered as agreed.
Collecting Deposits by Card, ACH, or Invoice Link
Web design payments are almost always card-not-present: the client pays from their office, not at your counter. That affects both cost and risk. Card-not-present transactions generally carry higher interchange than in-person ones, so ask your provider how your online payment processing pricing treats them.
Hosted Invoice and Payment Links
Sending a payment link with each invoice is usually the cleanest option. The client enters their own card or bank details on a secure hosted page, so your team never handles raw card numbers. If you invoice from accounting software, a QuickBooks integration can connect invoices to payment collection, and gateways such as Authorize.Net or NMI support hosted payment pages and invoicing. To understand how these pieces fit together, read payment gateway vs. merchant account.
Keyed Card Payments Through a Virtual Terminal
Some clients prefer to read their card number over the phone. A virtual terminal for keyed card payments handles this from a browser. Follow these habits:
- Turn on address verification (AVS) and CVV checks for every keyed transaction.
- Never ask clients to email card numbers or post them in project management tools.
- Record who authorized each payment and when.
ACH Bank Transfers
For large milestone invoices, many clients prefer ACH because it's a familiar way to pay vendors, and it can be a cost-effective rail for bigger tickets. Ask your provider about settlement timing, return windows and how disputes work for business accounts versus consumer accounts. Those terms determine when you should treat funds as final.
Cards on File for Later Milestones
Some agencies collect a card with the deposit and charge it automatically at each milestone. If you do this, get explicit written authorization that spells out the amounts, triggers and timing. Card brand rules govern stored credentials, so confirm the requirements with your processor before setting this up.
Offsetting Processing Costs
Some agencies want to pass card costs on to clients. Cash discount pricing, dual pricing and surcharging programs are each set up differently, and surcharging rules vary by state and card brand. Confirm current requirements before you change your invoices.
Expect Underwriting Questions
Processors look closely at businesses that take payment before delivering the work. Expect questions about your typical project size, timelines and refund policy. Long gaps between payment and delivery can affect how your account is set up, and in some cases a processor may require a reserve. Be accurate and upfront in your application; it leads to a more stable account.
Refundable vs. Non-Refundable Deposits in Your Web Design Payment Terms
Calling a deposit "non-refundable" doesn't automatically make it enforceable. Contract law varies by state, and courts often consider whether a retained amount reasonably reflects work performed or losses the agency actually suffered. Treat this section as general information, and have a qualified attorney review your contract.
Your contract language should cover:
- What the deposit pays for. For example, it reserves schedule time and covers discovery and initial design work.
- When it becomes non-refundable. For example, once work begins or once a specific deliverable is delivered.
- Cancellation terms. If the client cancels mid-project, are they billed for work completed to date, a kill fee or both?
- Ownership transfer. Rights to the final designs, code and source files pass to the client once you receive full payment.
- Refund method. Approved refunds go back to the original payment method.
Clear terms also matter in chargebacks. Card issuers evaluate disputes based on the evidence both sides provide, so a signed contract, a clearly disclosed cancellation policy and documented deliverables strengthen your case. Displaying the refund policy at checkout or on the invoice helps, too.
What to Do When a Client Stalls Before the Final Payment
It's a familiar scenario: the site is finished on staging, the client has approved it, and the final invoice sits unpaid. Here's how to stay in control:
- Don't launch on the client's domain until the final payment clears. Keep the site on staging or on hosting you control until the invoice is paid, and state this in your contract.
- Send a launch-readiness notice. Confirm in writing that the site is complete, list what was approved, and attach the final invoice with a payment link.
- Follow up on a set schedule. Send consistent, professional reminders at set intervals, and reference the late-fee or pause terms in your contract.
- Apply your contract terms. That can mean pausing further work, applying agreed late fees or treating the project as abandoned after a defined period.
- Escalate if needed. For large balances, a formal demand letter or legal counsel may be the next step.
Be careful about taking down a site that's already live or withholding access in ways your contract doesn't explicitly allow. Doing so can create legal exposure, which is why these terms need to be in place before the project starts.
The simplest fix for stalled final payments is structural: make go-live depend on the final payment, and say so in the proposal the client signs.
Next Steps: Getting Your Payment Setup in Place
Clear terms only work if paying is easy. A secure invoice link, a virtual terminal for clients who prefer to pay by phone and an ACH option for large milestones cover most web design billing situations.
MannyPay works with agencies through our payment solutions for web design businesses, including virtual terminals, gateways and accounting integrations. To review your options, request a free quote, and our team will walk through what fits your project size and billing workflow.
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.
