How agencies share documents with clients professionally

Most agencies have a system for everything — briefs, timesheets, invoices, handovers — except the moment that matters most, which is handing the work over. That bit is usually “attach the PDF and hope.”

Here’s the system I’d use instead. It isn’t complicated. It’s mostly about deciding, once, which things are files and which things are links, and then never thinking about it again.

The rule: persuade with a link, record with a file

Every document you send a client is doing one of two jobs.

Persuading. A proposal. A pitch. A brand book. A campaign report. A portfolio. These exist to be read, and every step between the client and the content is a place where reading doesn’t happen.

Recording. A contract. An invoice. A signed SOW. A spec they’ll need in eight months. These exist to be kept.

Send the first as a link. Send the second as a file. The mistake almost everyone makes is sending both as files, which means the most persuasive thing you own arrives in the same format as an invoice — and lands with the same enthusiasm.

Make it look like your agency, not like a tool

If you take one thing from this: the reader your client opens should not have a third company’s logo on it.

You’ve been hired to be the expert. A document that arrives wrapped in someone else’s branding quietly introduces a third party into a two-party relationship, and invites exactly the question you don’t want: what am I paying them for, if a tool did this?

So, in order of preference:

1. The client’s brand. For anything you’re producing for them — a catalogue, a report they’ll share onward — it should look like theirs. You’re invisible, which is the job.
2. Your agency’s brand. For pitches and proposals, where the point is that you made it.
3. A tool’s brand. Never, on client-facing work. This is what white-labelling is for, and it’s the single feature I’d refuse to compromise on.

Keep each client’s work separate

This sounds like housekeeping. It’s actually about the one mistake you can’t recover from.

If everything lives in one big folder, sooner or later you send the wrong link, or a client stumbles into a document that isn’t theirs. It’s a small operational slip with an enormous cost: it tells them their material is being handled loosely, and everything else you say about being careful becomes noise.

Give each client their own workspace, with their own branding and their own domain if you can. It also makes the boring stuff easier — offboarding is deleting one thing rather than auditing everything.

Instrument it, so you stop guessing

The follow-up is the worst part of agency life. Too early and you’re needy; too late and it’s gone cold. Most people resolve this by feel.

You don’t have to. If the document is a link, you can see whether it was opened, when, and how far they got. That converts the follow-up from a guess into a decision:

• Opened, read to the end, twice. Call them. Today.
• Opened, bounced at page two. The problem is page two. Don’t re-send the same thing — fix it.
• Never opened. They’re not ignoring you; it never got there. Resend, cheerfully, without the passive aggression you’d have deployed otherwise.

That last one has saved me more work than any other thing on this list. Most “silence” isn’t rejection. It’s a mail server.

Make it updatable

Client work changes. Pricing shifts, a page has a typo, the deck gets a new case study the week after you send it.

If you sent a file, you’re now sending a follow-up email that starts “please ignore my last…”, which is a small credibility withdrawal every single time. If you sent a link, you replace the document and the link they already have shows the new version. Nobody needs to know.

This is unglamorous and it’s probably the feature I’d miss most.

The whole system, in five lines

1. Persuasive documents go out as links. Records go out as files.
2. The reader carries your brand or the client’s — never a tool’s.
3. Each client gets their own space, so links can’t cross.
4. Check who read what before you follow up.
5. Update in place rather than resending.

None of that requires new software, in principle. In practice it requires software that lets you white-label, separate clients, and see reads — which is a short list, and is more or less exactly why I built one.

---

Living Page is built for this: per-client workspaces, full white-label, your own domain, and read analytics. See the agency plan.