Web Development Invoice Example: Annotated Template with Line Items

Sample web development invoice

Payment Terms: Net 15. 35% deposit before development begins; balance due at launch. Wire transfer or ACH preferred.

Notes: Staging site available at staging.bloomfloralsupply.com for review. Includes 30 days of post-launch bug fixes. Ongoing maintenance available at $150/hr.

Field-by-field breakdown

• From: Agency or freelancer business name, address, and billing email.
• To: Client's business and the project owner or decision-maker.
• Project reference: Link to the original proposal so both parties know exactly what scope is being billed.
• Line items by phase: Separating design, front-end, back-end, and QA helps clients understand where time was spent.
• Third-party costs: Domain and hosting are pass-through expenses -- list them separately for clarity.
• Deposit deduction: Show the upfront deposit and subtract it to display the remaining balance.
• Post-launch support: Note what is included (30-day bug fixes) and what costs extra (ongoing maintenance).

Common line items for web developers

Variations

• Fixed price vs. hourly: Fixed-price invoices bill by milestone (e.g., "Design phase -- 30% of $20,000"); hourly invoices list actual time.
• Retainer / maintenance: A monthly line item for hosting, security updates, and minor edits (e.g., $500/month).
• With tax: Some states tax software and digital services. Add a tax line if required.
• International: Specify currency, add VAT if applicable, and include SWIFT/IBAN for wire transfers.

Tips for web development invoicing

1. Bill at milestones (design approval, development complete, launch) rather than waiting until the end.
2. Log hours with descriptions so clients can see exactly what each hour covered.
3. Separate third-party costs from your labor so clients see your actual rate clearly.
4. Include a post-launch warranty period in your notes -- it builds trust and sets boundaries.

FAQ

Q: Should I charge for revisions during development? A: Include a set number of revision rounds in your scope. Beyond that, bill hourly and note the rate on the invoice.

Q: How do I handle scope creep mid-project? A: Issue a change order with new line items and get written approval before doing the work. Add the change order lines to your next invoice.

Q: Do I charge sales tax on web development? A: It varies by state. Most states do not tax custom software development, but some tax SaaS or digital products. Check your state rules.

---

Create clean web development invoices with the InvoiceQuickly web dev template.

Step-by-step: build a web dev invoice that AP processes without questions

1. Match invoice line items to your statement of work — if SOW lists "Discovery, Design, Development, QA, Launch" as five phases, the invoice should reference those exact phase names. AP teams reconcile against the SOW; mismatched terminology triggers manual review.
2. Reference the PO number when one exists — for B2B clients with $5K+ engagements, almost all use POs. Putting "PO# 12345" at the top of the invoice cuts processing time from weeks to days.
3. Itemize retainer hours separately from project work — if you bill a recurring retainer + occasional project work, separate them. "Maintenance retainer (March 2026)" + "Custom integration build (PO 12346)" prevents confusion in the client's accounting.
4. Document third-party costs with receipts attached — hosting, domain, third-party API fees, stock assets. Pass-through at cost or with a small (10–15%) administrative markup. Attach vendor receipts so AP can validate.
5. Send milestone invoices the day a milestone is hit — not at month-end. Speed matters; AP teams process invoices faster when tied to a specific deliverable.

Real web developer billing scenarios

• A boutique agency in Brooklyn structures $80K Shopify migrations into 5 milestones at 20% each (Discovery, Design, Build, QA, Launch). They invoice the day each milestone is signed off, never wait until end-of-month, and collect 100% of milestone 5 within 14 days of launch.
• A solo full-stack dev in Boulder bills retainer monthly on the 1st (predictable client cash flow), project work milestone-based (no surprises). She separates the two on different invoices because client AP teams sometimes route them to different approvers.
• A development shop in Austin discovered enterprise clients pay 40% faster when invoices include itemized hours by sprint, ticket numbers, and PR links. The transparency removed 80% of "what was this work for?" emails.

More web development invoicing FAQs

Should I bill hourly or fixed-fee for custom development? Fixed-fee for projects with documented requirements (50%+ of agencies use fixed pricing). Hourly for discovery, ongoing maintenance, and engagements where scope evolves. Hybrid is common: fixed for the build, hourly for support thereafter.

How do I handle scope creep on a fixed-fee project? Issue a change order with new dollar amount, signed by client, BEFORE doing the additional work. The change order references the original SOW and adds a new milestone. Don't fold extra scope into existing milestones — it dilutes everything and trains clients to expect scope expansion for free.

What's the standard deposit for new dev clients? 33–50% of project total at SOW signing, with the deposit covering discovery and initial architecture work. New clients without payment history should always pay 50%; established clients with on-time history can sometimes do 25%.

How do I bill for hosting and infrastructure? Either pass through at cost (with vendor invoices attached) or wrap into a "managed hosting" line item with a clear monthly amount. The pass-through model is cleaner for the client; the wrapped model gives you margin for management overhead.

What about ongoing maintenance after launch? Quote a monthly maintenance retainer separately (typically $200–$2,000+/month depending on app complexity). Bill it on the 1st of the month for the coming month — not in arrears. Predictable for the client, predictable cash flow for you.