What happens after the demo

Building software has a dirty little secret. The part everyone gets excited about, the demo that looks like the finished product, is often the easy 20 percent. The remaining 80 percent is the quiet, unglamorous work that decides whether the thing survives contact with real people.

Nobody demos that part, because it does not photograph well. But it is the part you are really paying for, so it is worth knowing what it involves.

Testing that tries to break it

A demo shows the software doing what it is supposed to do. Real users do things it is not supposed to do, constantly and creatively. They paste a spreadsheet into a name field. They click submit three times. They lose their connection halfway through.

Proper testing is someone deliberately trying to break the thing before your customers do it by accident. It is dull, it is essential, and its absence is exactly why some software feels solid and other software feels like it is held together with hope.

Security that assumes someone is trying

In a demo, everyone is friendly. In the real world, some visitors are bots probing for a way in, and they never sleep. Security is the work of assuming that and closing the doors: protecting the data, checking that people can only see what they are allowed to see, keeping secrets out of places they can be read.

You will never see this work. You will only ever notice its absence, and by then it is a headline.

Handover, so you are not held hostage

Here is a question worth asking early. If the people who built this vanished tomorrow, could someone else pick it up? Software with no documentation, no clean structure and no handover is a lovely thing right up until you need to change it and discover you cannot.

Good handover means the software is yours, not a black box you are permanently renting from whoever made it.

Support, because software is never finished

Real software meets real users, and real users surface things nobody imagined. A launch is not a finish line, it is the start of a conversation. The question is whether there is a plan for that conversation or whether you are on your own the moment it goes live.

Why this matters to you and not just to engineers

You might reasonably say this is all under the bonnet and none of your concern. It is not, for one simple reason. Every one of these things is invisible when you buy, and extremely visible when it fails. The invoice for skipping them does not arrive at launch. It arrives a quarter later, usually at the worst possible time, and it is always bigger.

So when someone shows you a demo, enjoy it, then ask what happens after it. The answer tells you far more about what you are buying than the demo ever could.