Send Clients One Link, Not Ten

The deliverable is done. Now comes the awkward part: pasting nine URLs into an email and hoping the client opens them in the right order. There's a cleaner handoff.

The handoff is a mess

You did the work. The project's done, the pages are polished, everyone's happy. Then you sit down to actually send it and the whole thing falls apart in the last ten feet.

Because the handoff is nine separate links. The homepage mockup, the mobile version, the style guide, the interactive prototype, the copy doc, the analytics dashboard, the two revisions the client asked for. You paste them into an email, add little labels so they're not a random wall of blue text, and hit send hoping the client opens them in the right order.

They won't. They'll open the first two, lose the email, and ask you to "resend everything" next week.

Why a pile of links reads as unfinished

Here's the uncomfortable part: a wall of URLs doesn't just look messy — it makes finished work feel unfinished. A client can't tell the difference between "here are nine deliverables" and "here are nine loose ends." The presentation is part of the deliverable. Sloppy handoff, sloppy impression, no matter how good the pages are.

One link, every deliverable

A collection fixes the last ten feet. You group every page you're handing off behind a single link — host-html.com/c/client-name — in the order you want the client to walk through it, with a blurb on each so nothing needs explaining. (The general how-to is here if you want the mechanics.) One link in the email. One thing to open. One thing to bookmark and come back to.

It reads like a finished project, because it is one.

The client handoff, step by step

1. Publish every deliverable as its own page.

2. Make a collection named for the client or the project.

3. Order it like a walkthrough — overview first, details after, revisions clearly marked. Blurb each card.

4. Send the one link. On a plan with team seats, the collection can belong to the whole team, so the designer, the copywriter, and the PM all add their pieces to the same handoff — and you manage who's on the team from your team settings.

When a deliverable changes

Client work changes after you send it. The honest edges:

• Swap a page without resending.: Update or replace a page and the collection reflects it — the client's one link still works. No "v7_FINAL_FINAL" email thread.
• Free pages go dark after a few days.: Fine for a quick review, risky for a handoff a client revisits next month. Client work usually wants permanent pages.
• Lock the sensitive ones.: Password-protect a page and it stays locked inside the collection — the right people get in, the link is still safe to forward.

Which plan, and why

Collections live on every paid plan, from Pro ($12/mo) up. Pro covers a solo freelancer's handoffs. The tiers above it add team seats, which is the one agencies want: a shared collection the whole team contributes to, so the client gets one polished link and you never play email-forwarding traffic cop. If your portfolio and your client work overlap, the builder's-portfolio angle is worth a read too.

Make the handoff the easy part

The work was the hard part. The handoff shouldn't undo it. Group the deliverables, send one link, and let the client see a finished project instead of a to-do list.

Send your next handoff as one link → · or see why we built collections.

Working out what each deliverable should look like? There's a guide per artefact: send a client report as a link, send a proposal as a web page, and build a client portal page.