You have one finished case study but the portfolio site isn't live yet. Here's how to send that single piece as a private link — without pushing a half-built site or flattening it into a doc.
There's a specific in-between you hit right before a portfolio launch. One case study is done — really done, the kind you'd lead with. The site it's supposed to live on is three weeks of evenings away. And someone asks to see your work today: a hiring manager, a prospective client, a founder who might bring you in.
You have the piece. You don't have the place to put it.
Push the half-built site anyway. You deploy what you've got so there's a link to send. Now the one strong piece sits next to an empty "About" page, a nav with dead links, and a hero that still says lorem ipsum in one corner. The viewer reads the whole thing as your portfolio, because that's what a site is. The finished work gets graded on a curve set by the unfinished work around it.
Flatten it into a doc. You drop screenshots and a write-up into a shared document and send that. It works, sort of. But a scrollytelling case study becomes a stack of stills. An interactive prototype becomes a single GIF. The document's own chrome — the comment rail, the sidebar, the editing toolbar — frames your work as a working note rather than a finished piece. And if the piece had any motion or interaction, that part is simply gone.
Wait until the site is live. The safe answer, and sometimes the right one. But "wait" has a cost when the person asking is deciding this week whether to interview you or hire someone else. The launch timeline and the opportunity timeline don't always agree.
There's a fourth option that fits the actual shape of the problem: give the one finished piece its own private link, and let the full site launch whenever it launches.
Export the case study as a self-contained HTML file — most modern tools, or whatever your AI builder hands you, can produce a single bundle with the styles and scripts inline. Drop that file at a private-link host. You get back an unguessable URL that opens straight to the work.
The viewer clicks it and sees the piece. Not a homepage they have to navigate past. Not a nav bar pointing at pages that don't exist yet. Not a login wall. Just the one thing you wanted them to see, rendered exactly as you built it — interactions, motion, live charts, all intact.
This is the gap a private link is actually built for: a real, sendable URL for a piece of work that has no public home yet. The privacy isn't a lockbox — private here means you decide who gets the link. You send it to the person who asked. It doesn't go on the open web, and it doesn't get found before you're ready for it to be found.
Drop one case study, get the private link, and open it yourself the way the hiring manager will. No account, nothing public, and the file self-destructs after 7 days — about the length of most "can you send me something?" windows.
The thing that makes pre-launch sharing nerve-wracking is the fear of leaking. You don't want a draft of your best case study sitting in search results before the site that's supposed to house it goes live. You don't want a prospective employer's tooling surfacing a half-finished URL with your name on it.
A private link is no-index by default. The slug is unguessable; search engines never crawl it; it exists only for the people you hand it to. When your real site launches, that's the surface you point search engines at — the canonical home for the work. The pre-launch link was always a private courtesy, not a public page, so there's no early-indexing mess to clean up later.
That same default is why this differs from deploying the half-built site. A public deploy is, by nature, public — a candidate for indexing, for being stumbled onto, for representing you before it's ready. The private link inverts that: nothing is visible until you choose to make it so.
The pre-launch link is temporary by design, and you can make it act that way. Set an expiry that lands around your launch date. When the full portfolio goes live, the standalone link closes itself instead of lingering as a stale duplicate of work that now has a permanent home.
On the free plan, links self-destruct after 7 days by default — often enough for a single "send me something before our call" exchange. If your launch is further out, a paid plan lets you pick the expiry date directly. And a link that never expires is on Solo, if you decide the piece deserves its own evergreen URL even after the site is up.
And if you've sent the piece ahead of an interview or a pitch, paid-plan analytics tell you whether it was opened — and re-opened. Three views the night before the call read differently from no views at all. It won't replace the conversation, but it'll shape how you open the follow-up.
A private link is the right tool when the piece is self-contained — it runs in the browser from a single HTML bundle. That covers most portfolio and case-study work: design walkthroughs, front-end builds, interactive reports, prototypes.
It's the wrong tool the moment the piece needs a server behind it. If your case study is a full app with a login, a database, or live API calls that have to run on a backend, that's not a static file — and you should host it where backends live. Vercel and Netlify are built for exactly that, and you'd point your prospect at the running app there. The honest split: if it's a browser-only artifact, a private link gives it a clean pre-launch home; if it needs a server, host the app properly and share that.
For most portfolio pieces, though, the artifact really is just HTML — and the only thing missing before launch is a place to put it. That's a link, not a launch.
If you're sending a CV alongside the work, the resume-link path is the same move for a different document. Built the piece in an AI tool? Hosting an AI artifact covers the export step. And if you want to browse the full set of one-piece jobs a private link handles, the use-case index lays them out.
"Client portal" is one word covering two very different jobs. One of them needs software with logins and permissions. The other one is four links in an email, and buying the first when you needed the second is how a solo practice ends up administering a system nobody logs into.
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.
Freebies, drafts, little tools — as a creator you keep needing a link that reaches specific people and nowhere else. A working guide to private share links for the three things creators send most.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.