Build the prototype before making the claim

Our projects page uses plain status labels: live, working prototype, experiment, research, idea. That was a deliberate decision. A visitor can then judge the work for what it is, rather than reading a confident sentence and finding out later that it was a demo.

What building it first teaches you

The Sky Pilot simulator ended up as two separate interfaces on one shared engine, a portrait mobile trainer and a larger desktop lab. That split was not the original plan. It came out of actually flying it on a phone; testing the mobile version showed the control layout needed changing.

The 3D printed work is the same story in physical form. Printing an object, holding it and breaking it reveals things a screen never shows: wall thickness, tolerance, where a clip snaps. That is why the store is described as a development shelf of concepts and prototypes rather than a shop of products ready to buy.

Why this matters for client work

• A small build answers questions that a proposal only argues about.
• Prototypes make it cheap to stop. If a first step shows the idea is weak, that is a good outcome for the budget.
• Honest labels keep expectations aligned, which is easier than managing disappointment later.

How it shows up in the way we work

We prefer to start with one defined practical project, agree the scope and the review points before anything is built, and then decide together whether to stop, refine or continue. The route from first outline to handover is set out on how buying works.