Systems

Prototypes you can actually click.

The design range shows how a site could look. This shows how a system behaves — availability, approvals, statuses, and what the owner sees when a customer does something. Open one and use it.

Interactive system prototype

These run in your browser and reset when you reload the page. They have no database, no accounts, no notifications and take no payment — so they are prototypes, not finished products. Every business, customer, vehicle, applicant, product and supplier in them is invented, no real person is depicted, and nothing you click creates a real booking, sends a message or stores a document. There is nothing to type: every choice is a fixed option, so none of your own information can end up in them.

Booking · job workflow · quotation approval

Car workshop booking and job tracking

A customer books a car in and picks a drop-off slot. The workshop sees it immediately, inspects, and sends a quotation. Nothing proceeds until the customer approves it — and the slot stays taken.

Availability that is a rule, not a picture
One job, two views — customer and counter
A quotation gate before any work starts
Status that moves through a real workflow
A first visit and a returning customer, handled differently
Data the workshop cannot have yet, handled honestly

Open the prototype →

Recruitment · screening queue · shortlist

Applicant tracking and shortlisting

Forty-seven applications for one role. Work the queue, decide in bulk, then send a shortlist to whoever makes the call — a client if you are an agency, a hiring manager if you are hiring for yourself. Every fact about a candidate shows where it came from, because most of what an applicant tracking system holds is reported, parsed or guessed, and only some of it has been checked.

Volume handled in bulk, not one form at a time
Every field carries its provenance — reported, parsed, guessed or checked
A CV that did not parse says so, instead of inventing a number
Undo, and why sending a message takes it away
Agency and in-house: the client view is never sent what it should not have
No match score anywhere, because the best candidates score worst

Open the prototype →

Retail · stock ledger · two locations

Stock control across two locations

A shop floor and a store room, and five different numbers that a simpler system collapses into one called "stock". Count something and watch the figure change without ever being edited. Move goods and watch them belong to neither location on the way. Then look at what the website is allowed to sell, which is not what is on the shelf.

On hand is summed from the ledger — nothing on the page can edit it
A count posts a variance, so the gap stays explained afterwards
A transfer is two movements, with the goods nowhere in between
What the website may sell is Available, never On hand
On order and In transit belong to no location at all
Why a count came up short is reported, never established

Open the prototype →

Not every business needs one built

A prototype is easy to be impressed by, so here is the honest version. Plenty of businesses are better served by a good enquiry form, or by setting up software that already exists. Custom is worth it when your workflow genuinely does not fit anything off the shelf — and I will tell you which of the three you are, before you spend anything.

Web apps & automation →

Have a workflow that nothing fits?

Describe how it works now. I'll tell you what's worth building.

First conversation is free, and "you don't need custom software" is a normal answer.

Message me on WhatsApp