Web Design Invoice Template - Canada

Each line item should describe a specific service or deliverable—homepage design, development, responsive mobile optimization, testing, or custom feature builds. Be detailed enough that clients understand what they're paying for, but concise enough to scan quickly. Include quantity and rate clearly. For example: 'Custom Homepage Design' with rate, or 'Responsive Mobile Optimization' with quantity and rate. Breaking services into distinct line items helps clients understand the value of each component and makes it easier to discuss changes or additional work in future projects.

List hosting and maintenance as separate line items from the primary design and development services. Hosting is typically a recurring monthly or annual charge, while maintenance covers ongoing support, updates, and monitoring. You can bill these as recurring charges on follow-up invoices or include them upfront if bundled. This separation helps clients understand which costs are one-time and which are ongoing, and establishes clear expectations for post-launch support obligations.

Build revision allowances into your project rate or explicitly include a limited number of revision rounds—for example, 'Up to 2 rounds of revisions included.' If revisions exceed the agreed scope, invoice them separately at your specified hourly or per-round rate. Document your revision policy clearly in your invoice terms or project agreement. This approach prevents scope creep and ensures both you and your client understand what's included in the base project price and when additional charges apply.

Project-based pricing works best when scope is clearly defined and you can estimate accurately—most web design clients prefer it because they know the total cost upfront. Hourly rates suit ongoing maintenance, retainers, or work with undefined scope. Many designers use a hybrid approach: quote a fixed project rate but track hours separately for revisions beyond the agreed scope. Choose based on how clearly the project scope is defined and your experience estimating similar work.

Most web design clients expect staged payments aligned with project milestones rather than a single invoice at the end. A common structure is 50% deposit to start, 25% at a midpoint milestone, and 25% upon completion and launch. Some designers use net 30 terms after delivery. Establish your payment schedule upfront in your proposal—clear expectations prevent confusion and ensure steady cash flow throughout the project lifecycle.

Organize by phase or milestone: Phase 1 (Discovery & Design), Phase 2 (Development & Integration), Phase 3 (Testing & Launch). Under each phase, list specific deliverables and services with their costs. This structure clarifies what each phase covers and when payment is due. Phased invoicing aligns naturally with project progression, making it easier to track deliverables and manage payments without overwhelming clients with a single massive invoice at the end.

Yes—domain registration, SSL certificates, email setup, and other ancillary services should be invoiced as separate line items. This clarifies what's included in your design and development fee versus what are additional products or services. Clients may already own their domain or prefer to register elsewhere, so separating these items gives them flexibility. Clear line-item separation also improves accounting accuracy and helps clients understand which costs recur and which are one-time.

Include a brief 'Project Summary' or 'Scope' section referencing the original agreement or proposal. List the key deliverables: number of pages, core features, integrations, content management setup, or any custom functionality. Reference your signed proposal by number or date if one exists. This creates a clear record of what was agreed and what the invoice covers. If significant changes were made during the project, note them on the invoice to document any scope adjustments or additional work.