How do I show a client work in progress without giving them access?

Send a recorded click-through of the finished part, in a sensible order, with the unfinished parts left out. It shows the work running without exposing a staging environment, and it does not require a meeting.

Is it dishonest to leave unfinished parts out of a client update?

No -- a progress update is meant to show progress, and choosing what to show is the same editorial judgement you apply to any client report. It becomes dishonest only if you imply the unfinished parts are done.

When should a client get real access?

At sign-off, for testing, and any time they need to do something themselves rather than watch it. A walkthrough is for showing; do not use one to avoid a review that ought to happen.

← Back to blog

Showing a Client Your Work Without Giving Them Access

August 28, 2026

A client wants to see how the work is going. The work lives on a staging server, behind a login, half-finished, with a database full of test data and a few things visibly broken.

Handing over access creates more problems than it solves, and a folder of screenshots does not show anything working.

Why giving access goes wrong

They find the broken parts you were about to fix, and lose confidence.
They change things, and you spend a morning working out what happened.
They evaluate a work in progress as if it were finished.
Credentials spread. Their colleague gets the login too, and now four people are in your staging.

What to send instead

A recorded click-through of the finished part, in the order that makes sense, with the unfinished parts simply not in it.

That is not hiding anything — a progress update is meant to show progress, and choosing what to show is the same editorial judgement you would apply to any client report.

It survives being forwarded

Your client will show this to somebody: a partner, a manager, whoever is paying. A screen share reaches one person once; a link makes the same case to everybody they forward it to.

It also means the update happens without a meeting, which for a client in another timezone is often the difference between weekly updates and monthly ones.

When they do need access

At sign-off, for testing, and any time they need to do something themselves rather than watch it. Do not use a walkthrough to avoid a review that should happen.

The distinction is showing versus doing. Showing is what a recording is for, and it covers most of the updates in a project.

Frequently asked questions

How do I show a client work in progress without giving them access?: Send a recorded click-through of the finished part, in a sensible order, with the unfinished parts left out. It shows the work running without exposing a staging environment, and it does not require a meeting.
Is it dishonest to leave unfinished parts out of a client update?: No -- a progress update is meant to show progress, and choosing what to show is the same editorial judgement you apply to any client report. It becomes dishonest only if you imply the unfinished parts are done.
When should a client get real access?: At sign-off, for testing, and any time they need to do something themselves rather than watch it. A walkthrough is for showing; do not use one to avoid a review that ought to happen.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →