A demo you can click beats a status report

Once a week, on every project, the client gets a link they can open and click. Not a percentage. Not a summary of what got done. Something running.

I started doing this because I noticed how easy written status updates are to write. You can say a module is eighty percent complete and mean it sincerely, and be wrong, because the last twenty percent is where the states nobody thought about live. A demo cannot be eighty percent. Either the flow works when you click it or it does not.

It protects the client

Drift shows up in week two instead of week seven. Someone opens the demo, sees a form field they did not expect, and says so while it costs an hour to change. The version of this project where they see it at handover costs days and a difficult conversation.

It also means nobody has to trust me. Trust is a nice thing to earn and a terrible thing to require, especially from a client who has been burned by an agency before. A weekly demo replaces trust with evidence.

It protects me too

On a fixed-price project, quietly falling behind is the failure mode that hurts most, because it compounds silently and then arrives all at once near the deadline. A demo every seven days makes that impossible to hide from myself. If Friday comes and there is nothing new to click, I know on Friday, not three weeks later.

Anything that can be reported can be reported optimistically. A running demo cannot.

The rule I keep

The demo goes out even when the week went badly. Especially then. A week with one small thing working and an honest note about what took longer than expected is a better message than a week of silence followed by a reassuring update.

Clients have never once reacted badly to that. They react badly to not knowing.