Written by The problem: the words are done, the money isn’t
Copy is a strange deliverable to invoice for. It’s not a physical object, it’s rarely “final” in the client’s mind until it’s live on the page, and it’s easy for a client to sit on a finished draft for a week without any real work left to do on their side. Meanwhile you’re waiting on an invoice that’s somewhere in a queue.
A payment request — a link the client can pay right away — shortens that gap by turning payment into a single action instead of a document someone has to process.
Where the delay usually comes from
- The draft is delivered, but “final” review drags on for reasons unrelated to the writing itself.
- Invoices go to someone who wasn’t part of the project and doesn’t recognize the request.
- Smaller copy jobs (a single landing page, one email) don’t justify a full invoicing setup for either side.
- International clients add bank-transfer delays and fees on top of the wait.
A workflow that keeps payment attached to delivery
- Finish and deliver the copy (doc, Google Doc comment-ready link, or CMS draft).
- In the same message, include a short note on what’s included and the payment request link.
- The client pays, or forwards internally for approval.
Sending the request in a separate follow-up message is the single most common reason payment stalls — it turns a bundled action into two things the client can put off.
Example scenarios
Landing page copy. Deliverable: final copy for a page, ready to hand to a designer or drop into a CMS. Attach the payment request the moment the copy is marked final — not after it goes live, which depends on someone else’s timeline.
Email sequence. Deliverable: a set of emails (welcome series, launch sequence, nurture flow). Bill against the agreed sequence length once all emails are delivered, rather than waiting to see open or click rates — performance isn’t something you control after handoff.
Blog content package. Deliverable: an agreed batch of articles or posts. For ongoing content work, billing per batch (rather than per article) keeps the payment request from becoming a constant interruption.
Product messaging / positioning. Deliverable: a positioning doc, key messages, or a style guide. This kind of strategic writing is easy to undersell — treat the finished document as the deliverable, distinct from whatever marketing execution comes after it.
What to include with the request
Attach a short summary next to the link so the client doesn’t hesitate over what exactly they’re paying for:
- What was delivered (page copy, sequence, batch, positioning doc)
- Where to review it (doc link, CMS draft)
- The payment request link
If the client needs a formal invoice too
A payment request doesn’t replace a client’s accounting requirements — some finance teams still need a formal invoice on file. That’s fine: use the request as the “pay now” action, and provide the invoice alongside it if asked. This isn’t tax advice; check your own obligations if you’re unsure.
Using Gitpay
Gitpay lets you create a payment request and share the link directly — a lighter alternative to setting up a full invoicing tool for project-based copywriting work.
Where to go next
- How our payment works — fees and how payouts connect to Stripe, Whop, or PayPal.
- How to request payment after delivering software work — the same idea applied to code delivery, if you also do technical writing or documentation work.
If you’d rather send a link than wait on an invoice, create your next payment request on Gitpay.
