The report is the deliverable. Send it as a link, not a PDF.

What report_final_v3.pdf costs you

You billed five figures for the thinking in that document, then handed it over in the least impressive way possible. The filename alone gives the game away: report_final_v3.pdf means at least two earlier versions are still out there, and whichever one the client opens is the report as far as they are concerned.

Then the practical failures stack up. A report with embedded charts and imagery gets heavy fast, and a 40 MB attachment bounces off mail servers that cap far lower than that. The interactive chart your analyst built gets flattened into a screenshot, so the client sees a picture of the work instead of the work. And once you press send, silence: you have no idea whether the report was opened the same afternoon or is still sitting unread the morning of the review call.

The link does what the PDF cannot

Publish the report as a web page and every one of those problems disappears. There is one URL, so there is one version, and it is always the current one. Nothing bounces, because nothing is attached; the page loads in the browser like any other page. Charts stay interactive: the client can hover the trend line, filter the table, and poke at the numbers, which is exactly what you want a paying client doing with your work. And because it is a page rather than a file, you can see the read happening.

From file to link in three steps

1. Bring the work in as a page. Ask your AI to produce the report as a single HTML page, or upload the file it already gave you. Charts, tables, and working numbers come along intact.
2. Gate it. Add a passcode, or restrict viewing to the client's email domain so a forwarded link stops at the gate. Set an expiry for the end of the engagement, or burn-after-read for a one-open handoff.
3. Send the link and watch the read. Every plan shows opens and unique viewers. Studio adds time on page, scroll depth, and which sections held attention.

Know it was read, not just delivered

A PDF tells you nothing after it leaves. A page reports back. On every plan you see when the report was opened and roughly how many people opened it, which settles the "did it land" question before you chase. On Studio you also see how long they spent, how far down they read, and which sections held attention, so you walk into the review knowing whether the CFO stopped at the summary or read through to the recommendations. The numbers are aggregate, not surveillance: see how pages get read.

A finish that matches the fee

Serve the link from your own domain, so the client opens reports.yourfirm.com rather than a vendor URL: Solo includes one custom domain, Studio ten. The client never logs in and never creates an account; a passcode or a work-email check is the whole ceremony. When the engagement ends, the link can end with it, on a date you set. And on Studio and Firm the page carries no "Made with Stacktree" footer, so the only name on the report is yours. Plans run Free $0, Solo $19, Studio $79, Firm $249 per month; pricing has the full breakdown.

If you deliver a report every month rather than once, you still do not need a login-walled portal for it: the same link, updated in place, does the job. See the client portal alternative for that pattern.