Project Discovery

In this stage, we get to know each other. In an interview, it will be clear what your company does and looks like, what the core of the application is and what target group(s) and objectives are involved. In the requirement analysis, we establish global outlines, so that we can focus on the parts that provide you with the most value.

Based on the requirement analysis, we select the appropriate project discovery program, create an action plan for the project discovery and, if desired, sign a non disclosure agreement, so that you are sure that your idea remains your own.

Developing a custom application is expensive. That is why it is important to make clear what the application will bring you.

• Are there earnings models in the application and, if so, what is a realistic forecast of the income?
• How much manual work does the application save your company and as a result how much labour costs are saved?
• Can the number of customers or customer lifetime value grow through this application?
• Are errors or mistakes prevented that currently cost the company?

By making these questions clear, a good estimation is made of what the application will bring your organization financially.

The functional design forms the blueprint for the new application. In the functional design, the functionalities are described in a non-technical way so the possibilities of the application are getting clear.

Components that are described in the functional design are:

• The objectives and target groups of the application.
• A functional list, organized on priority.
• A page list including navigation (flow).
• A detailed description per page.
• Important design and usability aspects.

The functional design clarifies the priorities and expectations and allows the development team to get involved in the project.

The prototype is the best part of the project discovery process. In this stage, the functional design is transformed into a visual prototype.

No matter how well a functional design is written, it only gets real when the application becomes visual. A clickable prototype is designed that contains all pages and functionalities from the functional design. The corporate identity, layout and flow of the application are thus visible.

In practice we see that this stage really makes the project come alive and creates more dynamics and a better cooperation.

The technical design follows after the prototype. The technical design maps the required technology and preconditions, so the application will be reliable, fast and scalable.

The components that are present in the technical design are:

• The programming languages ​​and technology with which the application will be created.
• Which data is stored and how it can best be processed.
• Whether external software is involved and, if so, how this is operating.
• Which testing will be used, so that the application will keep working well and stable.
• Which hardware (e.g. servers) is needed.

An easy question with a difficult answer. That is why we make a clear estimation based on the functional design, the prototype and the technical design.

We define the required roles, the hours and the costs. This makes it clear for each component how much time is required and what the costs are. We then discuss our estimation and work together towards a good approach.

• Are we going to work with a fixed price or is that not possible?
• Does the size of the project have to be adjusted to make it financially feasible?
• What is the construction and completion time of the project?

And then just one question remains: Are you going to realize your project?