How I Send Deliverables to Clients Without 10 Email Threads
I used to finish a project and immediately dread the next step: actually getting the files to the client. Not because the work wasn't good, but because the delivery process was always a mess. I'd send a WeTransfer link. They'd miss the email. I'd re-send. They'd ask for one file in a different format. I'd re-upload. They'd forward it to their business partner who couldn't open it. Ten emails later, the project that took me a week to build took another three days to hand off.
If this sounds familiar, you're not bad at email. The problem is that email was never designed for delivering project files. It was designed for conversations. Using it for deliverables is like using a hammer to cut wood — you can force it, but there's a reason saws exist.
Why email delivery always spirals
The core problem is that email threads are linear and ephemeral. Every message pushes the previous one further down. Attachments get lost between replies. Version confusion is inevitable because there's no single source of truth — just a chain of messages where "final_v2_REAL_final.pdf" could be in any of them.
Then there's the access problem. When your client needs to share the deliverables with their team, they forward the email. Now you've got people you've never met replying to the thread asking questions. Or worse, the forwarded email strips the attachments because of file size limits, and you're back to square one.
The system I switched to
The solution isn't a better email strategy. It's removing email from the delivery process entirely. Here's what I do now: every project gets a single, permanent link that the client can access anytime. All files live there. The project status is visible. When I upload a new deliverable, the client can see it immediately without me sending anything.
No email required. No "check your spam folder." No re-sending the same ZIP file because their inbox storage was full. The client bookmarks the link on day one, and every deliverable from that point forward is already waiting for them when they need it.
What actually changed in my workflow
The biggest shift wasn't technical — it was psychological. I stopped treating delivery as a separate event. Instead of "finishing the work and then delivering it," delivery became part of the work itself. I upload files as I go. The client can see progress in real time if they want to, or they can check in once at the end. Either way, the files are always where they expect them.
This also eliminated the dreaded "hey, can you re-send that file?" message. When there's one place to find everything, clients stop asking you to find it for them. I estimate this saved me 2-3 hours per week across all my active projects — time I used to spend digging through sent folders and re-uploading attachments.
How to set this up yourself
You have a few options depending on your budget and how polished you want the experience to be. At the free end, a shared Google Drive folder with a consistent naming convention works. Create a folder per client, a subfolder per project, and share the link. It's not pretty, but it's better than email.
A step up is a Notion page shared with the client. You get more structure — status fields, descriptions, embedded files — but the client needs to understand Notion's interface, which isn't always a given.
What I personally use now is a client portal. I set one up with ClientDesk because I wanted something branded with my logo that clients could access without creating any accounts. I upload files, update the project status, and the client sees everything through their portal link. It took me about five minutes to set up, and I haven't sent a deliverable over email since.
The one thing that makes any system work
Whatever tool you pick, the key is consistency. Send the client their link on day one of the project. Tell them: "Everything related to your project will be here. Bookmark this link." Don't also send files over email as a convenience — that defeats the purpose. Train both yourself and your clients to use one system, and the email thread problem disappears.
The goal isn't to find the perfect tool. It's to stop using email as a file cabinet. Any dedicated system — even a shared folder — will cut your delivery headaches in half. Pick one, commit to it for your next project, and see how it feels. I'd bet you won't go back.