How to Invoice as a Web Developer: Deposits, Launch, Hosting

A website project has one moment that changes everything about getting paid: launch. Before launch you hold the deliverable; after launch the client has it, and a final invoice that arrives a week later competes with every other bill they have. Most web billing disputes come from two other gaps: work that was never in the estimate (entering content, extra templates, a new integration) and recurring costs (hosting, domains, plugin licences) that nobody owned after handover.

This guide covers a build schedule that ties the last payment to launch, who should own the domain and hosting, a worked three-invoice example with a change order, care-plan billing and the tax forms clients ask for. For an annotated single invoice, see the web development invoice example. For quoting, see how to price web design. Building native mobile apps instead? The app developer invoicing guide covers store accounts and test builds.

How should a web developer schedule invoices for a build?

Tie each invoice to something the client can see and approve:

1. Kickoff deposit (often 30% to 50%). It secures your schedule and covers early design work. See deposit invoicing for wording.
2. Staging approval. The full site is built on a staging URL and the client signs off on it. This is the largest payment in most builds.
3. Final payment before launch. Issue it when staging is approved and content is in, and switch DNS to the new site once it is paid. For small clients this is the single most effective way to avoid a chased final invoice.

Corporate clients often cannot pay before launch because their accounts payable runs on Net 30 after an approved invoice and purchase order (PO). In that case, take a larger staging payment, launch on the agreed date, and put the PO number on the final invoice. See Net 30 terms.

Write two things into the contract to keep this schedule from stalling: an acceptance rule ("approved in writing, or no written objection within 5 business days of the staging link") and a content deadline. If content is late, the contract can let you invoice the staging milestone on time and move the launch date, rather than both waiting on the client.

Who should own the domain, hosting and plugin licences?

The client. A domain is registered under a contract with an ICANN-accredited registrar, and the registrant takes "sole responsibility for the registration and use of" the domain and must keep its contact details accurate (ICANN: Registrants' Benefits and Responsibilities, accessed October 2026). If the domain sits in your registrar account under your name, the client's business depends on your account, and a falling-out becomes a transfer dispute.

Practical rules:

• Domains and hosting: the client creates the accounts with their own card and adds you as a user. If you must buy something to keep the project moving, buy it in the client's name and rebill it at cost on the next invoice, with the receipt.
• Paid themes, plugins and APIs: state on the estimate whether the licence is yours (used under your developer licence) or bought for the client, and when it renews. Annual renewals that silently land on your card are the most common unbilled cost in web work.
• Credentials: list what you hand over in the final invoice notes ("Registrar, hosting, CMS admin and analytics access transferred to client accounts on launch"), so handover is in writing.

Worked example: a small-business site in three invoices

Hypothetical example; the price and rates are illustrative inputs, not market data. A freelance developer quotes $9,600 to rebuild a 12-page site for a physiotherapy clinic, with terms of 30% at kickoff, 40% on staging approval and 30% before launch, each due in 7 days. Change orders are billed at $95 an hour. During the build the clinic asks the developer to enter 18 service-page texts it had planned to enter itself (change order CO-01, 9 hours). A booking-form plugin licence is bought in the clinic's name for an assumed $99 a year.

The project total is $9,600 + $855 + $99 = $10,554. Invoice 3 goes out on 27 April, due 4 May, with the note "DNS will be switched to the new site on 5 May once this invoice is paid." Content entry is its own numbered change order, because the original estimate assumed the client would supply and enter text. The plugin line says whose name the licence is in and that it renews yearly, so next year's renewal is the client's, not a surprise.

After launch, the clinic signs up for a care plan: $350 a month, invoiced on the 1st, including 3 hours of updates and small changes, with overage at $95 an hour. In a month when the work took 4.5 hours, the next invoice adds "Care plan overage, May: 1.5 hours × $95 = $142.50" alongside the next month's $350, and the ticket list goes in the notes.

How should a web developer bill maintenance and care plans?

As a fixed monthly fee in advance, with the included work written down. A care plan invoice should say:

• What is included: for example, CMS and plugin updates, backups, uptime monitoring and up to 3 hours of small changes.
• Hours used against hours included, with a short task list.
• Overage as its own line at the stated rate, billed on the next invoice.
• Rollover rules: whether unused hours carry over, for how long, or expire at month end.
• What is not included: new pages, redesigns and new integrations are quoted separately.

Separate the care plan from hosting even if you resell hosting. The client should be able to see that "keep the site updated" and "keep the server running" are different services with different costs. If you do add a margin on hosting you manage, agree it in the contract and say so on the line.

What do web clients most often dispute?

The things the estimate left vague. Six to watch:

1. Content entry and migration. Say who enters content and moves old pages, and price it if it is you.
2. Bugs versus features. Define a bug as the site not doing what the approved staging site did. Anything new is a change order.
3. Revision rounds on design. State the number included before the build starts.
4. Redirects and SEO setup on a migration. Put them on their own line, because they are invisible work the client only notices if they go wrong.
5. Third-party integrations (booking, payments, CRM). Their APIs and fees are outside your control; price the integration, not the third party's uptime.
6. Cancelled projects. A kill fee clause ("work to date at the stated rate, and the deposit is non-refundable") turns a cancellation into a final invoice instead of an argument.

What should a web development invoice include?

Beyond the standard fields in what to include on an invoice, add the project name and milestone, the staging or production URL, the change-order numbers and approval dates, the hours and rate for any hourly work, reimbursed costs at cost with receipts, the client's PO number if they use one, and any launch or handover condition in the notes. For international clients, state the currency; see invoicing international clients.

Which tax forms and taxes apply to web developers?

US business clients will usually ask for Form W-9 before paying. For payments made in 2026, a client files Form 1099-NEC for a non-employee only if it pays you $2,000 or more in the year; card and third-party payment network payments are reported on Form 1099-K instead (IRS: Instructions for Forms 1099-MISC and 1099-NEC, accessed October 2026). Sales tax on website design, hosting and digital products varies by state, and some states tax services or digital goods that others exempt. Check your state's guidance before adding tax and see the sales tax nexus guide if you sell into several states.

Copyright in the code and design you create as a contractor stays with you unless your contract transfers it in writing. Most web contracts assign it to the client on final payment; the app developer guide explains the US rules in more detail.

For pay context, the US Bureau of Labor Statistics puts the median annual wage for web developers at $92,650 in May 2025, and says 18% of web developers are self-employed; its wage figures exclude self-employed workers (BLS Occupational Outlook Handbook: Web Developers and Digital Designers, accessed October 2026). A freelance rate has to be well above the salary equivalent, because it also covers your own taxes, software, unbilled sales time and gaps between projects.

This is general information, not tax or legal advice. Check your state's rules and your contract with an adviser. Last reviewed: October 2026.

How to invoice web projects with InvoiceQuickly

You can type or say what to bill ("Invoice Northside Physio staging milestone, 40% of $9,600, plus CO-01 content entry 9 hours at $95, due in 7 days") and InvoiceQuickly drafts the client, lines, rates and terms into an editable invoice that you review before saving. It does not send anything on its own.

What fits a web build:

• Estimates (Pro): send the build quote as an estimate; the client accepts it in their private portal and you convert it to an invoice in one step.
• Partial payments (all plans): record a bank transfer, card, cash or check payment against an invoice and track the remaining balance.
• Pro ($9/month): unlimited invoices, email delivery with the PDF attached, a payment link from your own Stripe or PayPal account for the remaining balance, scheduled reminders before and after the due date, branded PDFs and CSV export. Free covers 5 invoices, 5 clients and 3 AI drafts in total.
• Care plans (Pro): a monthly recurring schedule can create the fixed fee as a draft for review or send it automatically. The recurring form has one line item with saved tax, discount and payment terms, so bill overage on a separate invoice.

What it does not do: there is no care-plan hours counter, so compare hours used with hours included yourself. Pro does track time (a timer or manual entries) against projects and bills selected unbilled hours into a draft invoice; your own tracker works too. There is no deposit feature and line amounts cannot be negative, so bill each stage as its own invoice, as in the example. One tax rate applies per invoice. It does not manage hosting, domains or renewals for you. See the features overview and pricing.

When this approach is not the right fit

• Agency white-label work. If you build for an agency that bills the end client, invoice the agency on its terms, usually hourly against its PO, and leave the launch-payment tactic to them. See subcontractor invoicing.
• Large clients with procurement rules. Many will not pay a deposit or pay before launch. Price the payment delay into the quote, or agree more milestones, rather than fight their process.
• Template or theme sales. Selling a product to many buyers is e-commerce, not client invoicing, and needs a store with checkout and tax handling.
• Hosting resellers at scale. If hosting is a large part of your revenue, you need billing software built for subscriptions and usage, not a freelance invoice.

Frequently asked questions

Should a web developer get paid before or after launch?

For small and medium clients, before: issue the final invoice when the staging site is approved and the content is in, and switch DNS once it is paid. Corporate clients that pay on Net 30 after launch need a larger staging payment instead, and their PO number on the final invoice.

Should I bill hosting separately or include it in a care plan?

Separately. Ideally the client pays the hosting provider directly. If you resell or manage hosting, put it on its own line with the renewal date, and say whether you add a margin. The care plan line should cover only your work: updates, backups, monitoring and included hours.

How do I handle scope changes on a fixed-price website?

Write a change order before doing the work, with a number, a description, the price or hours, and the client's written approval. Bill it as a separate line on the next milestone invoice, citing the change-order number and approval date, so the original fixed price stays visible.

How do I invoice a retainer when the hours vary each month?

Bill the fixed fee in advance, show hours used against hours included with a short task list, and add any overage at the stated rate on the next invoice. Say in the contract whether unused hours roll over and for how long.

How do I write up a simple invoice for a small web job?

For a one-off fix or small change, one invoice is enough: your details, the client's details, an invoice number and date, a line describing the work with hours × rate or a flat fee, the total, the due date and how to pay. The how to write an invoice guide covers each field.

---

Start from the web developer invoice template, the web design invoice template or the WordPress developer invoice template. For milestone wording, see milestone-based invoicing. More guides are on the InvoiceQuickly blog. To draft your next milestone invoice, start free.