Why we demo every week, and what a demo is not

Every project we run has the same fixed appointment: once a week, you see the product working. Not described, not shown in a deck — opened in a browser or on a phone, clicked through, with the week’s changes visible. It is the one rule we do not relax, and after fifteen years of running projects I think it is the one that matters most.

What goes wrong without it

Software projects rarely fail suddenly. They drift. A requirement is misunderstood in week two and built on for six weeks. A screen that looked fine in a design turns out to be awkward to use, but nobody uses it until the end. The client’s business changes and the plan does not. By the time the “big reveal” happens, the gap between what was built and what is needed has had months to grow — and fixing it is expensive because so much sits on top of it.

A weekly demo catches each of those in the week it happens, when it costs an afternoon to fix.

What a demo is

• Working software, on a link you can open yourself, on real-looking data. If a feature is not finished enough to show, it is not demoed; we show what is done.
• Twenty to thirty minutes. Long enough to use the week’s work, short enough that it happens every week without being resented.
• Driven by you when possible. We would rather watch you try to complete a task than show you how smoothly we can. The hesitations are the feedback.
• Followed by a written note: what was shown, what you asked for, what changes as a result, what is planned next week. Three paragraphs, same day.

What a demo is not

• Not a status report. “We are 60% done” tells you nothing you can act on. A screen you can click does.
• Not a design review. Static mock-ups have their place, early, but they are not a substitute for the real thing. Things that look right often feel wrong.
• Not a surprise. You know on Monday what you will see on Friday. If something slipped, you hear it on Wednesday, not at the demo.
• Not optional. If a week has nothing to show, that is itself the most important thing to show. It usually means something is blocked, and blocked things need a decision from you.

What it asks of you

Thirty minutes a week, with someone present who can make decisions about the product. That is the whole commitment. The projects that go best are the ones where the same person attends every week; continuity on your side matters as much as on ours.

Why we are willing to be seen mid-way

Showing unfinished work is uncomfortable. Edges are rough, there are placeholder labels, something always breaks during the demo. We do it anyway, because the alternative — polishing in private for months and hoping — is how projects fail. A client who has seen the product every week since week one is never surprised at launch, and never has to take our word for where things stand.

If you have worked with an agency before and the first thing you saw was the finished product, you will notice the difference immediately. If you have not, it will simply feel like how it should work.