Demos

Not telling you,
just showing you.

Six pieces that often end up in a website or application, here as working examples instead of screenshots. Click into them, they really run. Nothing is stored and nothing is sent; it all happens in your own browser.

1

Price calculator

Visitors who can work out a price themselves call less often for an indication, and the enquiries that do come in are better prepared. Drag the size and switch options on: the amount keeps up, including a volume discount that kicks in by itself.

What this is usually used for: Quotes, subscriptions, shipping costs, payback time.

Open
2

Multi-step request

One form with twenty fields puts people off. The same questions in three steps, with a progress bar and a check per step, does get finished. Try clicking through with an empty email field.

What this is usually used for: Quote requests, sign-ups, intakes, fault reports.

Open
3

Dashboard

The figures you now paste together from three systems every month, on one screen. Change the period and hover over a bar for the details. In reality this data comes from your accounting or database, not from the page itself.

What this is usually used for: Revenue, planning, stock, project status, usage.

Open
4

Roles and permissions

Logging in is the easy part. The real work is that everyone sees exactly what they may see, and not one row more. Switch roles and watch what happens to the same table: rows disappear, margins get locked, buttons drop away.

What this is usually used for: Client portals, intranets, team accounts, anything with more than one kind of user.

Open
5

An AI assistant that does not guess

Most AI integrations are a chat window letting a language model guess. Not here: pick a question and see the tool fetching your own data first, and only then the answer. If the assistant wants to create something, that becomes a proposal you approve. Try asking it something that is not in the data.

What this is usually used for: Looking up and retyping that is manual work today, inside software you already have.

Open
6

What a code audit finds

Fourteen lines of code from an AI prototype: it compiles, it works in the demo and it goes live like that. Hit scan and see which three holes are in it; two of them open your entire database to anyone who knows the address.

What this is usually used for: Prototypes from Lovable, Bolt, v0, Replit or Cursor that have to reach production.

Open

Press 1–6 to jump straight to one

What is not in here

The real work sits under these screens.

These six run entirely in your browser: no database, no logins, no integrations, and in the assistant no language model either. That is precisely the difference between a demo and a product. In a real version the price is calculated on the server so nobody can change it in the browser, the role is not in the page but a row in the database, the request goes to your inbox or client portal, and the dashboard pulls its figures from your accounting. That part takes the time, not the screens. If you want to see what that looks like for your process, that is what Discovery is for.

Let's build

Tell me what you
want to build.

A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.

bas@webframer.nl+31 6 47 00 62 07
Bas Voets · Webframer
0:00 / 0:00
Demos · price calculator, roles, AI assistant and code audit · Webframer