Invoicing Per Article, Per Word, or Per Retainer
· 4 min read
You wrote four blog posts this month for one client, a single 3,000-word whitepaper for another, and you have a third client on a fixed monthly arrangement. Three jobs, three ways to bill. The invoice for each one should look different, because the thing you sold was different. Get the line items wrong and you invite the exact question you do not want: "What am I actually paying for here?"
Below are three worked examples with real numbers. Copy the structure that matches how you charge.
Per article: one line per deliverable
You agreed a flat 250 dollars per blog post. You delivered four in March. The clean way to invoice this is one line item per article, each with the title, so the client's marketing lead can tie every charge to a published piece.
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Blog post: "5 Onboarding Emails That Convert" | 1 | $250 | $250 |
| Blog post: "How to Price a Free Trial" | 1 | $250 | $250 |
| Blog post: "Churn Signals You Can Fix in a Week" | 1 | $250 | $250 |
| Blog post: "Writing a Renewal Email That Lands" | 1 | $250 | $250 |
Subtotal 1,000 dollars, terms Net 15, due date shown. Naming each post matters. When the invoice reaches accounts payable, a line that just says "Content x4" gets flagged. A line with a real title gets approved.
If the scope grew mid-month (say the client asked for a bonus fifth post at a higher rate), do not silently add it. Send the extra line as a change on the invoice and let them approve it. JupiterInvoice treats content changes as a new version, so the client sees exactly what moved from V1 to V2 and you both work from the same record instead of arguing over an email thread.
Per word: show the rate, the count, and the piece
Long-form and technical work often gets billed by the word. Say your rate is 0.40 dollars per word and you delivered a 3,200-word whitepaper plus a 900-word summary. The invoice needs to make the math obvious, because a per-word charge invites recalculation on the client's end.
| Description | Words | Rate | Amount |
|---|---|---|---|
| Whitepaper: "State of API Security 2025" | 3,200 | $0.40 | $1,280 |
| Executive summary (same project) | 900 | $0.40 | $360 |
Subtotal 1,640 dollars. Put the word count in its own column so nobody has to divide the total to check it. Set the count at the final delivered draft, not your first pass, and say so in the invoice notes. That single sentence heads off the "but the draft was longer" conversation.
Per-word billing is where clients most often want a purchase order attached before they pay, because the amount is calculated rather than round. If their AP team needs a PO number on the invoice, JupiterInvoice lets the recipient add it themselves after you have sent the invoice, and you get notified. No reissue, no new PDF.
Per retainer: bill the same amount, define what it buys
A monthly writing arrangement is the simplest invoice to produce and the easiest to get pushback on, because the client is paying a fixed number without a stack of deliverables in front of them. Fix that on the invoice itself. Spell out the scope the fee covers.
| Description | Amount |
|---|---|
| Monthly content retainer, April 2025: up to 6 blog posts (max 1,200 words each), 1 round of edits per post, 48-hour turnaround on briefs | $2,400 |
One line, one number, but the scope is right there. When you deliver fewer than six posts in a slow month, the client still sees what they bought and why the fee held. When they ask for a seventh post, you have a written baseline to point at before you quote the overage. If you want to understand the mechanics behind a fixed monthly fee, the definition of a retainer arrangement lays out how the commitment works on both sides.
Retainers reward consistency in your numbering. Bill on the first of the month, keep the same format every time, and your bookkeeping stays clean. A consistent invoice number format that increments on its own removes one recurring decision from your month.
Mixing models in one month
Most working writers run all three at once. That is fine. Bill each client on their own invoice using the structure they agreed to, rather than forcing everything into one format. A per-article client and a retainer client should never see the same layout, because they are not buying the same thing.
Whichever model you use, the invoice needs to survive the client's approval process. That means a real invoice number, an issue date, your payment details, and terms the client already agreed to. JupiterInvoice keeps the sender fields locked once you issue, lets the recipient add their PO or fix their billing address without a reissue, and tracks the invoice from Sent through to Approved so you know it actually landed. The invoicing setup built for writers and copywriters is shaped around exactly these three billing models.
Pick the structure that matches the job, name every deliverable, and build the invoice before you forget the word count. If you want to see the fields that keep AP from stalling you, the pre-send checklist runs through them in order.