The agent produced it. Deliver it under your name.

The last mile is the part the agent cannot do

The situation is now ordinary: an agent produces the SEO audit, the performance report, the campaign dashboard, the prototype, and the substance is genuinely good. What it cannot produce is the handoff. Paste a chat link or a raw artifact URL into a client email and the client sees another vendor's chrome around your work, styling that looks like every other chat export, and a page anyone with the URL can open. You billed for judgement and finish; the delivery should not undercut both.

The fix is not to retype the work into a deck. It is to treat the agent's HTML as the deliverable and give it the same last mile you would give anything else: polish, access control, your name. Each of those is one step here, and the agent can drive all of them.

Polish: from output to deliverable

Agent output tends to be structurally right and visually generic. The design pass closes that gap in one click: it rebuilds the page to a finished standard, same content and same link, and shows you a preview before anything changes, so a page that already has a design identity is left alone. It is on every plan, and agents can request it at publish time, which means the report can arrive already looking like it came from a studio rather than a chat window. What the pass does not edit is the prose; sentences that read machine-written are still your red pen to wield.

Gate it like client work

Every page starts private: an unguessable URL, roughly 128 bits of entropy, never listed or indexed. On top of that base you choose the gate that fits the engagement:

• A passcode, typed once by the client. On every plan, all three free pages included. Details on password-protecting a page.
• An email-domain gate, where viewers verify a work address on the client's domain by magic link. Nobody creates an account; access follows the mailbox, not a forwardable secret. From Solo.
• Per-recipient share links, one per stakeholder, each recording its own opens, each individually revocable and cappable. Free on every plan, and the honest answer to "did the CFO open it".
• An expiry, so the link ends with the engagement, or burn-after-read for a one-look handoff.

The client's side of all this is a link that just opens: no account, ever.

Your name on it: domains and client spaces

From Solo, pages serve from your own custom domain, so the URL in the email reads reports.youragency.com and no paid page carries any Stacktree badge; the badge exists on free pages only. Deliver to the same client more than once and a client space goes further: one address per client, acme.youragency.com, where every deliverable you file collects behind a single inherited gate the client passes once. The portal page generates itself from what you publish, newest first, so recurring delivery stops being a stream of new links. Solo includes one space, Studio ten, Firm unlimited, and clients are never seats.

Let the agent do the delivery too

The same agent that produced the work can hand it over. Claude Code, Cursor, Codex, and the rest publish over MCP with one install, and Claude.ai connects as a connector at https://api.stacktr.ee/mcp, so "publish this for Acme, passcode on, under their space" is a sentence, not a workflow. When the agent re-runs next month, update_site replaces the content behind the same URL, which is how a link sent in March is still current in June. There is even an anonymous path, no account, for a 24-hour page when you just need to see the flow work. The developer-worded version of this rail lives on hosting AI reports and publishing over MCP.

Where a link is the wrong medium

Honestly: if the contract promises editable source files, the client gets the Figma file or the repository, not a rendered page. And if the engagement is collaborative, with the client editing alongside you, you want a shared workspace, not a deliverable. A private link is for the moment the work is finished and changes hands, which for most agency engagements is the moment that decides how the work, and the fee, are judged. For prototypes and demo builds specifically, hosting a client demo site covers the pre-finish version of the same handoff, and sending a report as a link covers the recurring one.