Most people research web design costs for weeks before they sign anything. Almost nobody researches how they’re expected to pay for it, and payment terms are where a surprising number of projects actually go wrong, not the price itself.
The short version: standard practice is a deposit before work starts, followed by either a second payment on completion or a series of milestone payments tied to project phases. What should worry you isn’t a deposit. Every reputable studio asks for one. It’s a full payment up front, no written scope, or a final payment that’s due on a date rather than on your acceptance of the finished work.
Terms get skipped in the buying process for an understandable reason. By the time you’re comparing quotes, you’re focused on whether the number fits your budget, not on the mechanics of how you’ll hand that money over. But the terms are what determine your leverage for the rest of the relationship. A well-priced project with bad payment terms can leave you paying in full before you’ve had a real chance to object to anything. A more expensive project with a proper acceptance clause gives you room to push back if the finished work doesn’t match what was promised.
Common payment structures
| Structure | How it works | Watch for |
| 50/50 split | Half to start, half on completion | “Completion” should mean your sign-off, not the agency’s calendar |
| 30/40/30 milestones | Tied to design approval, development, and launch | Each milestone should have a clear, specific deliverable attached |
| Monthly retainer | Fixed monthly fee for ongoing work | Best suited to maintenance or long-running engagements, not a one-time build |
| Pay on completion | Full payment only once site is live | Rare for a reason: almost no studio will front the entire cost of your build |
None of these structures is inherently better than the others. What matters is whether the structure ties your money to something specific happening, not to a date passing on a calendar.
What a deposit is actually for
A deposit isn’t a show of good faith or a formality. It’s what reserves your spot on an agency’s schedule and covers the discovery and design work that happens before you see anything finished. Discovery, wireframing, and initial design direction all take real hours before a single page exists that you could reject. Nobody reputable works entirely on spec, doing all of that speculative work and hoping to get paid at the end.
If a studio asks for nothing up front, that’s usually a sign they’re either new enough to need the work at any cost, or structuring things so leverage sits entirely with them for the rest of the project. A full-payment-at-the-end arrangement means they’re carrying all the financial risk of you disappearing mid-project, so somewhere else in the relationship, the terms tend to balance that risk back in their favour.
A typical deposit runs somewhere between a quarter and half of the total project cost, though the exact figure varies by studio, project size, and how much custom work is involved before anything visible gets produced. What matters more than the specific percentage is what it’s tied to: capacity and discovery work, not an arbitrary number picked to feel proportional to the total quote.
Milestone payments and what triggers them
The strongest version of a milestone structure ties each payment to a deliverable, not a date. “30% due two weeks after signing” is a date. “30% due on approval of final designs” is a deliverable. The difference matters because a date-based schedule pays the agency whether or not you’ve actually approved anything, while a deliverable-based schedule protects both sides. You’re not paying for work you haven’t seen, and the agency isn’t stuck waiting indefinitely for sign-off on something you’ve quietly stopped responding to.
Review and acceptance clauses
This is the part worth paying the most attention to, and it’s often buried in language that sounds interchangeable but isn’t. A contract that says the final payment is due “30 days after delivery” is different from one that says it’s due “on your written acceptance of the completed site.” The first pays the agency on a clock. The second pays them once you’ve actually confirmed the work meets what was agreed.
A proper review-and-acceptance clause gives you a defined window to test the finished site and flag anything that doesn’t match scope, before the final invoice is due, rather than being on the hook for full payment the moment the agency considers the project finished, regardless of whether you agree.
Red flags
A handful of patterns are worth walking away from, or at minimum negotiating hard on:
- 100% of the fee requested up front
- No written scope document, just a verbal understanding of what’s included
- No defined change-order process for scope adjustments
- Final payment tied to a calendar date with no acceptance step
- A studio that can’t or won’t define, in writing, what “complete” means for your project
Any one of these on its own isn’t automatically disqualifying. Plenty of legitimate studios have a slightly unusual structure for a specific reason, and it’s fair to just ask why. Several of them together is a pattern worth taking seriously, particularly the combination of no written scope and a date-based final payment, since that’s the combination that leaves you with the least recourse if the delivered site doesn’t match what you expected.
It’s also worth noticing what these red flags have in common: every one of them shifts risk onto you without giving you anything in exchange. A deposit is a normal risk-sharing arrangement. Full payment up front with no defined scope isn’t sharing risk. It’s transferring all of it to you and hoping the relationship stays good enough that it never matters.
Change orders
Scope changes happen on almost every project: new pages get added, functionality gets swapped, priorities shift partway through. The healthy version of this is a change order. The new scope gets quoted and approved in writing before the work happens, so it shows up as a line item you agreed to rather than a surprise on the final invoice. If a studio can’t tell you how they handle mid-project changes, ask before you’re the one finding out mid-project.
There’s a reasonable middle ground worth expecting here too. Small adjustments, a headline swap, a minor layout tweak, a section reordered, shouldn’t generate a change order every time; that level of nickel-and-diming makes a working relationship exhausting for both sides. The line is scope that meaningfully expands the project: new pages beyond the agreed count, new functionality that wasn’t quoted, or a full design-direction reset after you’ve already approved one. That’s where a change order belongs, quoted and agreed before the work starts rather than absorbed silently and then explained on the invoice.
Our terms
Standard projects are split into two payments: a deposit to begin work, and the balance on completion, due after you’ve reviewed and accepted the finished site. We don’t ask for the full amount up front. Larger builds are broken into milestones tied to project phases instead. We also offer interest-free payment plans on request if spreading the cost makes a project workable for you. If you’re still working out roughly what a project should cost before getting into terms, our guides on Calgary web design prices, WordPress project costs, and website startup costs cover that ground, and the price calculator will get you a rough number in a couple of minutes. And if you’re earlier in the process, still comparing studios rather than reading contracts, our guide to choosing a website designer covers the questions worth asking before terms even come up.
