Rapid Prototyping

Try to collect feedback about you product as soon as possible and adjust accordingly. It's normal, that a product idea changes while you are developing and improving it. Reasons are assumptions about the market, the usage, the acceptance, the demand, reservations, dependencies, etc.; that sooner or later turn out to be true or not.

Don't invest a lot of time and money, just to find out in the end, that the product you've built is not the right one or "the time isn't right". The sooner you can reduce the number of assumtions your product depends on, the smaller the risk and the higher the chance for success.

IIS Labs is happy to help you through this phase. Find on this page what IIS Labs can do for you and your product.

It is more important to do something in a small way than to talk big about it.

Willy Brandt



The minimal viable product (MVP) is a product reduced its most essential features. Doing so reduces development costs, tightens release schedules and tests whether the selected features are really the valid and valued ones.

The definition of the MVP determines what features the first version of the product consists of. Based on that it's possible to plan, conceptualize, estimate, implement, etc.; and have a manageable and promptly realizable product.

Info: 1 ~ 2 hours

A paper prototype allows us to have a tool in our hands after very little time. With it it's possible to simulate the program flow, identify missing programm portions and define use cases.

Info: 1 ~ 2 hours

A functional prototype is a (partial) implementation of your idea, that deliberately uses shortcuts, reductions, incompletions, etc.; to get to a testable product in a cost efficient and time saving manner.

The development costs to build a functional prototype are typically a fraction of what it would cost to build the actual product. A functional prototype saves money in the long run and provides important information that's needed for the implementation and certain business decisions.

Info: Costs depend on the complexity of the idea and scope of the prototype

Find out what customers like about your product, what not, what's frustrating and what's missing. The work in this phase depends upon the existance of a product or prototype, as well as the topics (e.g. usage, acceptance, valuation, etc.) that should be screened.

The collected information helps to find adaptions or corrections to your product that matter to the consumer.


Lots of people know what to do, but few people actually do what they know. Knowing is not enough! You must take action.

Tony Robbins