Cooperation

Non-binding offer

The first step of development is to get to know the demand and create a non-binding offer. This is a rough estimate of the project price based on the initial information supplied by the client in the inquiry.

In order to create a basic estimate of time and cost, we need at least a rough description of the project and the expected goals.

Analysis

Before the actual development, it is first necessary to familiarize yourself with the project. In most cases, the client does not know the development process of a web application or system and we do not know the core of their business and the problem they want to solve with the application. Therefore, to fill this gap, we have to conduct an analysis that consists of several meetings. It is usually accomplished in the form of a few face-to-face meetings and another 5 to 7 via video calls, depending on the nature and size of the project.

The goal of this analysis is to:

• Understand the client's business
• Understand the client's problem
• Identify risks
• Determine the size of the project
• Devise an assignment based on this analysis
• Price the project more accurately

How is the analysis carried out:

• In a face-to-face meeting, the focus on analysis is much greater than in online meetings, which is why we prefer face-to-face meetings.
• Once we have the first hypotheses, we start validation, either with the target group (people who will use the app) or with the product owner (app owner, business owner).
• We then start creating the assignment during which we liaise with the client and fine-tune it. Somewhere we hit a dead end, somewhere else a feature that wasn't described enough, etc. This part is usually the most time-consuming.
• Once we have the assignment done, we can get down to the design and "click" the model. Again, we are in contact with the client so they can give feedback on the work itself.
• Once the design is complete, usability tests are run with the target audience. This involves clicking through a prototype (usually in Figma) combined with prepared questions (type, click, find, describe, etc.). Usually, 3 tests are enough to reveal major flaws in design or functionality. This part is not necessary and the client does not need to request this testing. However, for larger applications, we recommend it.
• Once the usability tests are completed, the last details in the design are fine-tuned based on the feedback and the analysis is complete.

Important information:

• Analysis can sometimes take a relatively long time, but keep in mind that any time spent on analysis and specification will save a lot of much more expensive development time.
• It's a good idea to think about the MVP version of the app at the beginning. Later on, features can be added based on feedback. It is always better to make an MVP and add features to it than to create a massive system where X features are useless. But you had to pay for them.

Design

The last step before the actual development is the design of the application. Here the client can choose from two options. The first option is the creation of a graphic design by our graphic designer. Although this option is more expensive, it offers the client a wide range of options for how their app will look and how the UX and UI will be built. This option is popular for applications where the target audience is the B2C sector.

The second option is graphics from a pre-prepared graphic template. This fulfills everything you expect from a modern web application. At the same time, it will speed up development and thus reduce the cost of creation. This is especially suitable for the B2B sector, where it does not put so much emphasis on the visual aspect of the project.

Development

We advocate agile development, so during this phase, we communicate regularly with the client, either through the Trello app or on regular status calls via Google Meet. This makes development much faster and, above all, more resilient to any risks that could slow down the project.

We always develop against a tattoo server, so the client can track changes that have been made to the app and give feedback on them.

We then send detailed reports from the application to Clockify at regular intervals. This allows the client to see exactly how much time was spent on what task.

Project completion

Our cooperation does not have to end with the project's completion. We like to work on projects for a long time and are dedicated to their development. At the same time, we will take care of your web application as part of the maintenance to ensure that it does not become outdated and security problems do not occur.