The writing got fast. The handover didn't. Here's why the last step of client work — getting the finished thing in front of the client — quietly became the slow part, and what a good version of it looks like.
There's a specific feeling that shows up in client work now. The analysis is sound, the writing is better than it used to be, the whole thing came together in an afternoon rather than over three days — and then you spend twenty minutes deciding how to actually send it, and something about the last step makes the work feel less finished than it is.
That feeling is worth taking seriously, because it isn't nostalgia. Something real changed, and it changed asymmetrically.
Think about the old ratio. Two or three days to research and write a report; four minutes to attach it and press send. At that ratio the delivery step is invisible — nobody optimises the four minutes, and nobody should.
Now the first number is an afternoon and the second number is unchanged. The handover hasn't got worse in any absolute sense. It's simply become a much larger fraction of the whole, and fractions are what you notice. This is also why the fix feels overdue rather than novel: the problem was always there, sitting underneath a bigger one.
There's a second-order effect that matters more. When producing a revision was expensive, you produced few of them, and each one was a considered event. When a revision costs an hour, you produce several — and every one of them multiplies the delivery problem, because each revision is another copy in someone else's inbox with no indication of which supersedes which.
Sending a file is sending a copy. That sounds obvious and its consequences are not.
You lose the ability to correct. The moment the file leaves, the version your client has is frozen. Find a transposed figure an hour later and your only move is a second email that begins with an apology — and now there are two documents in their inbox and a coin-flip about which one they open.
You lose version truth. By the third round, "the latest one" is a phrase that means different things to each of you. Most of the awkwardness in a review cycle isn't disagreement about the work. It's disagreement about which artefact is under discussion.
You lose the rendering. A document renders against whatever fonts, application version and screen the recipient has. Your spacing drifts, your charts flatten, your carefully-set tables wrap. You made something precise and they received something approximate.
You lose the signal. You cannot tell whether it was opened. When a client goes quiet you're left choosing between two very different stories — they read it and are thinking, or it's sitting unopened under forty other emails — and those call for opposite follow-ups.
None of these is fatal on its own. Together they're why a piece of work you're proud of can land feeling like admin.
Export the report as a self-contained page, drop it in, and send the link. It opens in their browser, stays current when you revise, and stops opening on the date you choose.
The reflex fix is to stop attaching and start sharing a folder. It solves the size problem and almost nothing else.
Cloud storage is built around a genuinely good idea — your files should live in one place and follow you everywhere. That design serves working material extremely well. It serves finished material poorly, because it gives the recipient a container rather than the contents. They land on a listing, work out which item is current, download it, and open it in whatever their machine picks. Three steps and two chances to open the wrong thing before they've seen your work at all. And some of the time, they hit a sign-in or an access request first.
None of that is a flaw in the product. It's what a sync tool is for. It's just that storage and delivery are different jobs, and using one tool for both is where the friction comes from.
Strip it back to what the client should experience: they get one address, they click it, and the work is there. No download, no application, no account, no wondering whether it's the current version.
Working backwards from that, four things have to be true.
It opens as a page, not a file. The layout you built is the layout they see, on a laptop or a phone. Charts stay interactive, links stay clickable, nothing depends on what software they have.
The address is the credential. Nobody signs in. This is the part people get wrong most often, usually with good intentions — a login feels more secure. But asking the person paying you to create an account to read what they commissioned is the most reliable way to delay a review by a week. A link with enough randomness in it can't be guessed or crawled into, which makes holding it the permission. The trade-off is honest and worth stating: a bearer link can be forwarded, so treat it like a key.
It stays current. Replace the file, keep the address. The link you sent on Monday opens Thursday's version. This single property removes most of the version confusion in a revision cycle, because there is only ever one artefact to discuss. It's also why sending a link before the work is finished stops being reckless — the link improves rather than expires.
It has a lifespan you chose. Set the end date when you send it, not when you remember to. An engagement's materials shouldn't stay open forever by default, and a page that simply stops opening is a cleaner boundary than a request that everyone delete their copies. Where the contents carry pricing or strategy, put a password in front so that holding the link isn't enough by itself.
One caution, because this is where the argument gets oversold: none of the above makes a report good. A weak analysis delivered beautifully is still weak, and clients can tell.
What it does is stop the delivery from subtracting. The work you did should arrive at full strength — same layout, current version, one click, no friction to navigate before they reach the first sentence. That's a low bar, and it's routinely missed, and missing it is expensive precisely because it's invisible: nobody ever writes back to say "your handover was clumsy". They just take longer to reply.
The tell that you've got it right is small and specific. The client's response is about the work — a question about the recommendation on page four — rather than about the file. When the file stops being a topic, the handover is doing its job.
If your report started life as something an AI tool wrote for you, there's one extra step to plan for rather than discover: the tools that produce these documents mostly keep sharing inside the account or organisation that made them, which is right for internal work and leaves external delivery to you. Knowing that in advance turns it into a step in your process instead of a surprise at the end of one.
Recurring reports break in a way one-off deliverables don't: every send produces another address, and the old ones keep working with old numbers in them. Here's the version where the report has one address for the whole engagement.
Interactive dashboards lose their interactivity in PDF, screenshot, and screen recording. The trade-off, and where private-link hosting fits between handoff and full deployment.
Five channels agencies use for client previews — and what each accidentally reveals about the work in progress. Where private-link delivery sits, and when it's worth the swap.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.