How to Get Paid Before Delivering Freelance Work
The "stop delivering before payment" insight came from watching a pattern repeat itself constantly: freelancer finishes the work, sends the files, follows up once, follows up twice, hears nothing. The client has everything they wanted. The freelancer has nothing.
It's not a client quality problem. It's a process problem. Once you deliver, your leverage is gone. The fix isn't better contracts or more follow-ups; it's changing the order of operations so payment is structurally required before delivery happens.
Why the Standard Approaches Don't Fully Work
Upfront deposits help but they don't solve the final delivery problem. You still have to send the last files and hope the remaining 50% shows up. Invoicing software makes it easy to send invoices; it does nothing to ensure they get paid. "Just trust them" is not a strategy.
The cleanest solution is a payment-gated delivery link: you put your finished files somewhere with a URL, you put that URL behind a Stripe payment wall, you send the client the payment wall link instead of the files. They pay → they get the files. The payment is the key that unlocks the delivery. Ghosting becomes structurally impossible because the files don't exist from the client's perspective until payment confirms.
The Workflow
Finish your deliverable and upload it to Google Drive, Dropbox, or anywhere that gives you a shareable link. Go to unseal.link, paste that link, set the amount owed, and generate a paywall link. Send the client that link.
The whole setup takes under 60 seconds. In your message to the client, you can say something like: "The [project name] is complete and ready for handoff. You can access all files here: [link]. Payment is processed through Stripe; you'll receive the download link immediately after."
That framing is professional and matter-of-fact. It's not asking permission or apologizing for requiring payment. It's just how the delivery works.
What the Client Experiences
They open your link and see a clean page with the project name, the amount, and a Stripe checkout. Card details or Apple Pay. Payment processes in about 2 seconds. The file link arrives in their inbox within 30 seconds. No account to create, no app to install.
From their side it functions exactly like buying any digital product online. Most clients don't blink. The ones who push back hard on paying before receiving digital files are usually telling you something important about themselves, and you've learned it before it cost you anything.
What File Types Work
Anything with a URL. Google Drive for designs, documents, spreadsheets, and video files. Dropbox for large assets and zip archives. Figma for design handoff. GitHub for code. Frame.io for video deliverables. If it has a link, it works.
For document deliverables like brand guidelines or strategy reports, upload the PDF to Google Drive and set sharing to "Anyone with the link can download." For design files, a Figma view link or a Drive folder with exported assets both work well.
The Numbers
If you're doing $2,000 projects and getting ghosted on final payment even twice a year, that's $4,000 in lost revenue. unseal.link's fee is 4.5%; on a $2,000 project that's $90. The math makes the decision pretty obvious.
For smaller deliverables ($200-$500 projects), the same logic applies at a smaller scale. The habit of payment-gated delivery is worth building regardless of project size; it's easier to maintain a consistent process than to decide case by case.
When Not to Use This
For large enterprise clients with established AP departments and net-30 terms, payment-gated delivery isn't appropriate. They have real procurement processes that require invoices before payment, and they're low ghosting risk anyway.
This workflow is for small business clients, solopreneurs, and individuals, especially new clients you haven't worked with before. Use it by default for anyone you don't have a multi-year track record with.
FAQs
What if the client wants revisions after paying?
Payment covers the agreed deliverable. Revisions within the original scope are part of the project. Out-of-scope revisions are a new conversation, and potentially a new paywall link for the additional work.
Can I use this for milestone-based projects?
Yes. Create a separate unseal.link for each milestone. First draft delivery, revision delivery, final delivery: each gets its own payment-gated link. The client only gets each version after that milestone's payment clears.
What if I need to refund?
Full refund control from your dashboard. One click. Since the files were delivered digitally, you're not obligated to refund in most cases, but you have the option.
Is this awkward to explain to clients?
Less awkward than chasing an unpaid invoice for 3 months. Most clients, when presented with a professional payment link, just pay it. The framing matters: "here's how I handle deliveries" is different from "I don't trust you to pay." Lead with the former.