Instead of rushing into project execution and problem solving, we begin by understanding the nature of the business and challenges that it has. Problem definition is the first step towards the definition of the desired goal. We work closely with our clients to understand the challenges related to their business so we, together, know what to expect from the final solution Only after understanding the problem we can begin to think about options to solve the problem. With our extensive experience we can suggest different option in solving the problem. We go through them thoroughly and create the target for a prototype which is in the next phase. This step is important, since the original idea is often improved already during this stage. There are many details that are often ignored when the idea is pitched to us.

Prototype has two main objectives:

Solution validation

We create a prototype in order to test the idea with the end users. The initial goal is to get feedback and validate our concept with the following simple questions:

• Does our concept really solve the problem which was defined in the previous phase?
• Can the end user imagine himself/herself to use the solution that we presented?
• Would the end user pay for the service/solution? How much?
• How could the solution better serve the end user?

Clarification of the project requirements

Feedback tells us how big pain our defined problem is. Did we just imagined the problem and it does not really exist or it is exactly how we anticipated?

Often, the user gives good ideas to improve our concept. These ideas should be taken into consideration and possibly include to the project.

Continuous development is part of our company’s philosophy.

We do not aim to build the perfect product at once. Instead, we prioritize the functionalities and only develop a product that includes solutions to problems that create the biggest pains. We aim to have a well-functioning product which is pleasant to use.

A project can be a mobile application, a website, a brand identity or a combination of all. The project is done mostly in short development cycles and show the progress to our clients. This way we can avoid misunderstandings and include any new ideas that the client might have. Short development cycles increase the chances to achieve the product that the client and the user want.

After the project is executed, we launch the product to the first user segment. The first users are the ones, which get the most benefit from the launched product. It is important to get users as soon as possible, so that we can get feedback. All possible mistakes are fixed and continues improvement may begin.

To best serve the users, the users need to decide what to develop. We aim to get feedback immediately after launching the first version of the project. The feedback has a big effect in what we develop next and what is the priority. We do not want to create a large and expensive product, which is not used.

We maintain the launched product; therefore, we can react quickly and improve it.