Build, measure, learn loop

Validate before you build

Get feedback early, improve your idea, validate again and learn what brings the most value to your customers.

Lean principles outsourced.

The process

This is how we approach building a new product:

1. Draw the first prototype

The first step is to identify 3-5 of the riskiest elements of the idea, the parts on which everything depends ("leap of faith" assumptions). We then start building a mini-product that has these features, is not fully functional yet, but can help us get it in front of an audience for feedback.

2. Show it to real people

As soon as possible, we show our first prototype to several individuals from the target market. They can be total strangers, recruited via Facebook ads, or a list of contacts coming from you, or a subset of users of an existing "mother" product.

3. Learn from their behaviour

We observe how they use it and what their feedback is. We are shooting for measurable data that validates our "leap of faith" assumptions. We also try to find out:
- does the product generate enough value for its users?
- are they interested to try it again after we improve it?
- is there something that we should remove or add?
- would they pay for such a product or service?

4. Update the prototype

Based on the feedback gathered, we need to take a decision: Persevere or Pivot? Do we improve the current prototype and continue, or do we need to re-think things? Sometimes the findings suggest that we need to make a radical change in scope (without changing the vision).

5. Re-test it with real people

With a new (and better) prototype ready to be showcased, we select a mix of new prospects from the target market with some of the ones that already participated in step 2. and show them the improved product concept.

6. Gather more insights

We collect a fresh new set of valuable data from our experiment at step 5, and measure how their interest evolved over time (are we doing well?). This again leads to another Pivot or Persevere decision.

7. Build a clickable prototype

Now that we have enough info, we can go ahead and create a more real and interractive prototype. Usually it's a set of pages that allow you to explore the product by clicking on different elements.

8. Test it with the early adopters

The people that have shown interest in this product are recalled for another round of testing.

9. Last round of learnings

Because the product looks and acts like it was real, we can now collect a more detailed set of observations that would increase the user experience with the product. We also collect a list of people that have committed to pay for the product, when it comes out. This helps a lot with the seed funding for implementing the actual product.

10. Final MVP design

At this step, all that is left is polishing the final design and writing down the requirements for development. You now have all you need to develop the MVP (minimum viable product) that has increased chances of success, already built-in. You may decide to implement it with us, or have someone else do it. It's up to you.

Today's market is uncertain

Modern entrepreneurs increase their chance of success by following the Lean methodology. Are you using it?


  • For Low Budgets
  • - Rapid Prototyping
    - Learnings Report

    Max. 10 screens

UX/UI Pack

  • For Product Managers
  • - Rapid Prototyping
    - Learnings Report
    - Polished Design

    Max. 10 screens

Product Pack

  • For Startups
  • - Rapid Prototyping
    - Learnings Report
    - Polished Design
    - Detailed Requirements

    Max. 10 screens


  • For Everyone Else
  • Tailored to your needs.


Here's the list of deliverables that you will receive:

Learnings Report

Learnings Report

You will receive a complete report of all the data gathered from the target group.

Final Design

Complete Design

Not only is the user experience optimized, but the design we make is truly beautiful and stands out.

Clickable Prototype

Clickable Prototype

If you have the wireframes, the developers will work a lot faster, so you save both time and money.

Requirements Document

Requirements Document

The written detailed requirements, translated into "programmer speak" are a must, if you decide to go ahead with development.

What are you waiting for?