When should I send proof of work?

As it happens, not in a summary at the end. An end-of-project summary argues with an impression the client has already formed, while sending each item as it lands builds that impression instead.

Does this help at renewal?

It is often the whole argument. At budget time somebody uninvolved asks what the money bought, and your contact has to re-explain months of work from memory -- unless there is a short record of what changed to point at.

← Back to blog

Proving the Work You Actually Did

August 28, 2026

Some client work is visible immediately: a new page, a redesign, a feature. Much of it is not — a fixed integration, a faster load, a process that now runs without anybody touching it.

Invisible work is where clients quietly conclude they paid a lot for very little, and they rarely say so before deciding not to renew.

Show the mechanism, not the hours

A timesheet documents effort and persuades nobody. What convinces a client is seeing the thing work: the sync running, the form submitting where it used to fail, the report generating on its own.

Thirty seconds of the working system does more than a page of itemised description.

Before and after, where you have both

Record the broken state before you fix it, if you get the chance.
Record the fixed state immediately after, while it is fresh.
Keep them short -- one point each, not a project retrospective.
Name them by the problem the client complained about, in their words.

It is also your renewal argument

At renewal or budget time, somebody who was not involved asks what the money bought. Your contact then has to remember and re-explain months of work, from memory, badly.

A short library of what changed, sent as it happened, means that conversation has evidence in it rather than recollection.

Send them as you go

A summary at the end of a project competes with the client having already formed an impression. Sending each one when it happens builds that impression instead of arguing with it.

It takes minutes per item and it is the difference between being a cost and being visibly useful.

Frequently asked questions

How do I show a client work they cannot see?: Show the mechanism working -- the sync running, the form submitting where it used to fail, the report generating on its own. Thirty seconds of the working system persuades where an itemised timesheet does not, because effort is not the thing they are buying.
When should I send proof of work?: As it happens, not in a summary at the end. An end-of-project summary argues with an impression the client has already formed, while sending each item as it lands builds that impression instead.
Does this help at renewal?: It is often the whole argument. At budget time somebody uninvolved asks what the money bought, and your contact has to re-explain months of work from memory -- unless there is a short record of what changed to point at.

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 →