How tech and digital freelancers invoice
Digital work spans a wide range of billing models — and the right model depends on the nature of the engagement. Getting the structure right from the start avoids scope disputes and speeds up payment.
Web developers often use milestone billing: splitting a project into defined phases, each tied to a deliverable and a percentage of the total fee. This aligns payment with progress and reduces the risk of doing work without getting paid. Each milestone invoice should name the deliverable clearly — 'Design approval', 'Backend API complete', 'Final QA and launch'.
Virtual assistants typically bill hourly or on a monthly retainer. For hourly work, itemise time by task type — 'Email management (4 hrs)', 'Research (2 hrs)' — so the client can see where their budget went. Tool and software costs incurred on their behalf are pass-through expenses, billed at cost on a separate line.
Translators bill per source word or per target word; journalists often bill per article, per word, or per day rate. Whichever rate you use, state the unit clearly on the invoice — word count, article title, or day rate — so there's no ambiguity when the client reviews it against the brief.
Tech & digital freelancer invoice checklist
- Milestone or deliverable description — name the specific phase, feature, or output being invoiced
- Rate and unit — hourly rate and hours, per-word rate and word count, or flat project fee
- Software / tool expenses — pass-through costs billed at actual cost on a separate line
- Scope reference — note the project brief, spec, or contract version the work is based on
- Revision or change order flag — if any work is outside original scope, label it clearly
Tips for tech and digital freelancers
Use milestone billing to protect cash flow
Never complete an entire project before invoicing. Break work into 2–4 milestones and invoice each one on delivery. A 30–50% deposit at project start is standard. This keeps your cash flow healthy and gives the client clear checkpoints to approve work before the next phase begins.
Bill software expenses as pass-throughs
If you're purchasing tools, hosting, or APIs specifically for a client's project, those are billable at cost. Agree upfront whether they're included in your project rate or invoiced separately. Keep receipts and pass them on with the invoice — clients appreciate the transparency.
Name scope creep on the invoice
When work goes beyond the original brief, don't silently absorb it. Add a separate line item: 'Additional feature — user authentication (out of original scope)'. This creates a paper trail, normalises charging for extras, and protects you if the client disputes the total.
Frequently asked questions
How do I invoice for a milestone-based project?
Split the project total into milestone payments and invoice each one separately — or use a single invoice with milestone line items showing what each payment covers. For example: 'Milestone 1 — discovery and wireframes (30%)', 'Milestone 2 — development (50%)', 'Milestone 3 — testing and launch (20%)'. Tie each milestone to a deliverable so payment is linked to tangible progress.
Can I charge for software subscriptions on my invoice?
Yes, if the subscription is a direct cost of completing the client's project — a design tool, hosting, a domain, a third-party API — it's billable as a pass-through expense. Add it as a separate line item: 'Software: Figma subscription (1 month)' at cost. Agree upfront whether software costs are included in your project rate or billed as extras.
How should translators invoice — per word or per hour?
Most translators bill per source word or per target word, depending on the language pair and client expectations. Per-word billing is transparent and easy for clients to verify against the source document. For revision and editing work where word count is hard to measure, hourly billing is more appropriate. State the word count and rate on the invoice so there's no ambiguity.