What People Publish

Proof-of-Concept Demo

Definition

A proof-of-concept demo answers one question: can this be made to work? Not can it scale, not is it secure, not would anybody pay — only whether the mechanism holds together well enough to be seen. In practice it tends to be a single page with the logic running in the browser, increasingly generated in an afternoon from a prompt, with sample data written in and the awkward parts faked. That is entirely legitimate, so long as everyone watching knows which parts are real. Technically it is usually a single-file web app: one HTML file carrying its own markup, styles and script, with nothing behind it.

Why It Matters

The gap between describing an idea and showing it is enormous. A meeting where three people picture three different things just ends; a link they can click ends in agreement or in a clear objection. Speed is where the value sits, so a proof of concept should cost hours rather than weeks — one that takes a month has quietly become the product, built badly. The opposite risk is worse: a convincing demo gets mistaken for a finished thing and somebody puts real data into it. Saying plainly on the page which parts are real and which are faked is not modesty, it is what keeps the demo useful.

How It Works

Build it as static files and put it behind a link, because prototype hosting of this kind needs nothing else — no server, no database, no deploy pipeline. Keep state in the browser with localStorage if the demo has to remember anything between clicks, and accept that it is per-device and will vanish; that is fine for a demo and unacceptable for a product, which is exactly the distinction to say out loud in the room. Put it behind a password-protected link when it is going to a client or an investor, so an unfinished build is not sitting in public with your name on it. Add a visible note at the top — prototype, sample data, not for real use — rather than relying on an email that gets forwarded without it. And give it an end date: take it down once the decision it was built for has been taken.

Real-World Example

A two-person team pitching a scheduling tool builds the core interaction in an afternoon and publishes it at rota-demo.99helpers.site behind a password. It is one HTML file holding a fortnight of invented shifts, with no way to save anything. In the meeting the prospect drags a shift, watches the conflict warning fire, and the argument about whether the idea works is over in under a minute. The demo comes down a week later, and none of its code survives into the real version — which was always the plan.

Common Mistakes

  • Leaving the demo public and unlabelled — somebody finds it, assumes it is the product, and judges you on a build that was never meant to be seen
  • Faking the part that was actually in doubt — if the hard bit is hard-coded, the demo has proved nothing
  • Letting it become the codebase — the shortcuts that made it fast are precisely the ones you cannot live with later

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →