How do agencies share work in progress with clients?

Between the yes and the launch, the client needs to see the build grow. Share each round on a link that stays the same, get comments on the screen, and see who looked.

On this page

By Kaz Kato · Published 20 October 2026 · Updated 20 October 2026

Give each person on the client side their own link to the build, and keep that link the same while the work changes underneath it. Each new version reaches them on their next visit. They comment on the screen they mean, and you can see who has looked since the last round, before the next call.

This guide is for the weeks between the yes and the launch, when the client needs to see the build grow. It covers sending each round on the same link, getting comments on the right screen, and knowing who has looked. The agency pitch guide covers winning the work first, and agencies shows the whole loop on one page.

How you share it What the client sees Where feedback lands Who has looked Same link each round?
A staging link from your host The build, behind the host’s protection. A Vercel shareable link lets anyone who has it open a protected deployment, through a query string in its address. Shareable links are on every plan. Email, or the host’s own comments. Someone you invite to a Vercel deployment must log in to Vercel to leave a comment, or to open it at all if it is protected. Vercel’s page on shareable links says nothing about an expiry date, or a record of who opened one. Yes
A password on the site The build, behind one password for everyone. Webflow can put a password on a page, a folder or a whole site, one password for each; page and folder passwords need a Site plan. Its help names client prototypes and private demos as uses. Netlify sets site-wide password protection in its dashboard, and it is not available on its credit-based Free and Personal plans. Email Not described on those pages Yes
A screen recording each round You using the build, not the build itself Email, or under the video Loom names a viewer only when they watch while logged in to a Loom account. Anyone else shows as “Anonymous”, with no way to see who they were. No: a new video each round
A room (ours) The build, on mock data Pinned to the screen they meant, with a picture of it Each person by name, round by round Yes

Each line about another tool is from that tool’s own page, and the sources are listed at the foot of this page.

They go wrong in the same few ways. A new link every round, so the client opens last week’s. Feedback scattered across email threads. One password passed round the client’s office. No idea who has looked before the call. And real data sitting in a half-built screen that someone forwards.

  • A new link every round. The client bookmarks one, a colleague has another, and nobody is sure which is current.
  • Feedback in email. “The button on the second page” could be any of three buttons by the time you read it.
  • One password for everyone. It works until someone leaves the project. Then everyone needs a new one.
  • No record of who looked. You walk into the review not knowing whether the finance lead has seen it.
  • Real data too early. A build that reads a live system shows real records to whoever the link reaches. A room runs on mock data, and says so on every visit.

Deploy the new build to the same project. Every link opens it from the viewer’s next page load, and nobody’s link changes. If you want to check a round before the client sees it, send it as a preview only your team can open, then make it live when it is ready.

  1. Deploy the round. Ask Claude to deploy it, or run roomi deploy --commit in the project’s folder. The new build is live at once.
  2. Or preview it first. roomi deploy --commit --preview sends it as a preview instead. You and your team open it with Preview on the project in the app. Viewers keep the live build.
  3. Make the preview live. roomi promote --commit makes it the live build, and every link opens it from its next page load.
  4. Roll back if a round goes wrong. On the project’s Builds tab, choose an earlier build and Roll back to this. Nobody’s link changes.

Pages, next steps, the brand and every link belong to the project, not the build. So none of them changes with a new round. Running a pitch says what changes when the live build does, and the CLI has every flag.

How do I get feedback on the screen they mean?

Let them comment in the room. A comment is pinned to the app and the screen it was left on, and comes with a picture of that screen, with their pin marked on it. You reply from the app, and they read your reply in the room on their next visit, under their own comments.

  • Comment in the room’s header turns on comment mode. They click a spot, or draw round part of the screen, and write what they think.
  • The project’s Feedback tab lists every comment, newest first: who left it, on which app and screen, and what they said. Resolve marks one dealt with.
  • If the demo’s page cannot be pictured, the comment comes with the room’s outline of the stage instead, with the pin still where it was left.
  • Reactions are quicker: a heart, a clap or a fire. The project’s Activity tab lists who put which on, each person by name.
  • Each person sees only their own comments and your replies to them, never anyone else’s.

How do I know who has looked since the last round?

Open the project’s Analytics tab. It shows each build beside the one before: its people, their visits, time per person, who came back and the comments it drew. So after a round you can see who has opened the new build, and who has not been back since the last one, before you call.

  • An email when they open it. Roomi emails you the first time each person opens their link, and again when they come back an hour or more after their last visit. That second email comes at most once a day for each person.
  • Your week, on Monday morning. The weekly summary says who came in last week, who came back and who to call first.
  • Each person’s visits. Their journey shows each visit in order, their time on each app and page, how far they took the tour, and who they passed the link to.

Analytics and the pipeline has everything the room records, and what it does not.

Everyone who should see the work gets their own link: the person who signed, their designer, the finance lead who joins for the last round. A link each keeps every visit and comment under the right name. And when someone leaves the project, you can close their link without touching anyone else’s.

  • Make one per person. Name the person, add their email if you like, and choose when it expires. On the project’s Links tab, or with roomi link "Priya Shah" --expires 30.
  • Have it sent for you. Tick Send this for me, and Roomi emails them their link, once, under the name you chose.
  • A forwarded link asks who they are. A newcomer says who they are, and appears under the link it came from. Make them their own link if they will stay.
  • Expiry for a contractor. A link can close in a week, two weeks, a month, three months, or never.
  • Revoke when someone leaves. It stops working at once, and what they did stays on record.

How to give each client their own demo link walks through it, and sharing has the detail.

Can the room carry the studio’s name?

Yes. On Pro, the room wears your studio’s name and accent colour instead of Roomi’s. On Team, it adds your logo and a theme for the whole room. On Team and Enterprise, the room can also answer at an address of your own, such as a pitch subdomain of your studio’s site.

Brand and next steps shows where each part of the brand appears, and teams covers sharing the work across the studio.

What happens when the work is signed off?

When the client signs off, the room has done its job. Pause it if they may want another look, so every link opens a short page saying you paused it. Or revoke the links to close it for good. Either way, every visit, comment and answer they left stays on record for you.

  • Pause the room from the project’s Settings. Resume it whenever you like, and the same links open it again.
  • Revoke the links from the Links tab, one by one. A revoked link answers “Not found”, the same as one that never existed.

If you built the site in Lovable, handing a Lovable site over to a client covers moving the project, the repository and the domain to them.

Put this week’s round in a room, give each person on the client side their own link on Pro, and let every round after it land on the same one.

Questions people ask

Do clients need an account to comment?

No. On their own link, the first comment or reaction asks once for an email, so you know who it is from. The room says that nothing is sent to it, and it is not checked.

Can my team see a round before the client does?

Yes. Send the build as a preview, which only you and your team can open. Viewers keep the live build until you make the preview live, and then every link opens it.

Can I go back to last week’s version?

Yes. Roll back to any earlier build from the project’s Builds tab. Everyone opening a link gets it from their next page load, and nobody’s link changes.

Sources

About the author

Kaz Kato, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit. More at katosan.co.uk.

One link per person, the newest build behind it.

Deploy it free; private links start on Pro.

Get started freeSee pricing