Free web design invoice and website estimate templatesKeep the build, scope and final invoice equally clear.

Name the stage being billed and what was delivered at it, the number of pages and revision rounds, and extras such as copywriting or content migration. Third-party costs like hosting, domains and plugin licenses belong on their own lines with the period covered, and the handover terms should say when the client owns the site and its logins.

It depends on how many pages and user flows the site needs, how many stakeholders join the workshops, whether you do user research or content planning, and how much of the brief the client has already written. The generator opens that line at $700.00 so the invoice is not blank; replace it with your own fee.

The deposit is its own invoice against the accepted proposal. Design and build are billed by stage, each invoice naming what was approved, and hosting or maintenance is a recurring invoice on its own cycle, not a line buried in the build. Keeping them apart means a client who cancels hosting does not reopen the build fee.

Tie it to launch or to sign-off on staging, whichever comes first, so a client who delays going live does not delay paying for finished work. State in the proposal that the site goes live, or files are handed over, once the final invoice is paid. Milestone billing gives every stage a trigger and a due date.

Your leverage is the handover: keep the site on your staging server, and hold admin logins, source files and the domain transfer until the balance clears, as long as your contract says so. Do not take down a live site without a clear contract term allowing it, as that can start a dispute of its own. Send a statement of what is owed, then a final notice.

In many states web design services are not taxed, but some states tax them, some tax digital products or software, and a few tax hosting. Premium themes or plugins you resell can be taxed differently from your design time. The generator lets you set tax per line, so check your state, and the client's state if it differs.

Price them before you build them. Send a short change order with the added pages or features and the fee, get approval in writing, then add it as its own line on the next stage invoice. Per-page pricing makes this easy, because an extra page already has a rate on the original quote.

Write the schedule into the estimate: a share of the total due on signing, on design approval, on staging and on launch, each tied to something the client can see. Then send one invoice per milestone that names the stage, what was delivered and what has been paid so far.

Whatever your proposal states and the client signs. Many studios take a share up front so discovery and wireframes are covered if the project stops. Invoice it as its own document and send a receipt when it clears.

As its own recurring invoice, separate from the build. Name the month covered, what the plan includes (updates, backups, a set number of edit hours) and the hourly rate for anything beyond it, so small requests do not become free work.

A statement of work is your written scope: pages, features, rounds, what is excluded and the milestone schedule. You write it and keep it with the proposal; put its reference and a one-line summary on each invoice so the client's accounts team can match it.

The client, in most cases. Either they pay the provider directly, or you list the cost on its own line with the period it covers. Renewals then land with the owner of the site, not with you.