Product development

Make your idea tangible before you invest heavily.

A working first version to test with users, stakeholders or investors — and to find out what works before the big costs begin.

Discuss your project See our approach

When is a prototype the right step?

A prototype is not an intermediate step that costs time. It is the cheapest way to find out that something doesn't work.

You need internal or external buy-in

Explaining an idea takes time and invites debate. Showing something that works convinces the board, customers or investors in a single meeting.

You want to know whether users will really use it

Assumptions about behaviour are rarely entirely right. A testable version shows where people drop off and what they actually need.

You want to avoid the cost of failure

Mistakes that only surface at production or launch are far more expensive than mistakes you find in a prototype.

You want something in hand quickly

An MVP or first working version gives you something tangible within weeks, instead of months of documentation and meetings.

Which prototype fits your question?

Not every prototype has to do everything. The type depends on what you want to prove.

Clickable prototype

Working screens without the underlying technology, to test usability and flow.

MVP or first working version

Software that genuinely works with real data, ready for use by a first group.

Physical prototype

A tangible model or working unit to judge form, size and use.

Technical proof of concept

Proof that it can be done technically, when that is where the biggest uncertainty sits.

Connected prototype

Hardware and software together, including app or dashboard, to test the whole.

Test design and validation

Deciding up front what you want to know and how you will measure it, so testing actually produces answers.

Proven in practice

Prototypes we have already built

Ideas made tangible early, so how they work, how they feel and whether they are technically feasible could all be tested.

Privacy-friendly sensor for holiday rentals

A sensor concept tested on function and privacy before investing fully.

Concept for an automated collection kiosk

A self-service process worked out and tested with drivers, administration and warehouse staff.

PCB development for a new product

From schematic and component selection through prototype and testing.

View all projects

Our approach

A prototype is only useful once it is clear what you want it to prove. That is where the work starts.

Deciding what you want to prove

Is it about usability, technical feasibility, market interest or cost? That determines what the prototype needs to do — and above all what it doesn't.

Defining the scope

We deliberately limit ourselves to the smallest whole that produces a valid answer. Anything beyond that costs more without adding certainty.

Designing and mapping it out

Screens, flows or 3D designs that establish how the prototype looks and works, before anything is built.

Building

A working version in a short time: clickable, software-based, physical or a combination, depending on the question.

Testing with real users

We test with the people who will ultimately use it and collect findings that translate into concrete choices.

Deciding and building on

Continue, adjust or stop. All three are valid outcomes — and all three are cheaper than finding out afterwards.

Frequently asked questions

What is the difference between a prototype and an MVP?

A prototype exists to test something and can be thrown away afterwards. An MVP is a first real version that goes into use and grows from there. Which one you need depends on what you want to prove.

How quickly is something ready?

A clickable prototype can be finished in a few weeks. A working software version or a physical prototype takes longer. After the first analysis there is a concrete timeline.

Does the prototype have to be finished?

No. A prototype does not need to be complete or polished, it needs to answer the right question. Anything that doesn't contribute to that, we deliberately leave out.

Can we develop the prototype further later?

Sometimes. With software we build on a foundation that can grow where possible. If speed matters more, throwaway work is occasionally the wiser choice — we agree that up front.

Do you also make physical prototypes?

Yes. From 3D-printed models to working units with electronics, depending on what needs testing.

What if the test shows the idea doesn't work?

Then the prototype did exactly what it was for. That outcome is considerably cheaper than discovering the same thing after a full development project.

Do you help with the testing itself?

Yes. We establish up front what you want to know, how you will measure it and who you will test with, so the results support a decision.

Is a prototype useful for convincing investors?

Often, yes. Something that works says more than a presentation, and shows that the technical risks have been examined.