You directly get in touch with one of our software architects. We leave the sales manager at home. Our architect will of course tell you something about HybrIT, but he mainly wants to discuss the IT issues that play a role within your organization. What ambition do you have with your company? What problem is there that you would like to see solved? Or which digital service do you want to realize for your customers and / or suppliers? Or are your IT systems simply not growing with the intended business growth? Based on what is going on within your organization, the architect will guide you through a suitable solution in understandable language. A conversation with HybrIT is without obligation and therefore always yields something.

If our contact gives rise to a follow-up, ie we both believe in a successful collaboration, the requirements gathering starts. Or in other words; we will clarify the wishes and requirements together with committed employees. What should the new system be able to do? What does the current system landscape look like? Which applications, databases, internal and external links are there? By whom and how will the system be used? What functional extensions do you foresee in the future? All information that gives us a good idea of the current and desired situation. In which we of course also take the technical aspects of future expansions into account.

The feasibility check, or the feasibility test, answers the question of what is needed to build the desired system. In theory we can build anything, but at what cost? A new system must be proportionate to the business value it delivers to you. Because we are an entrepreneur ourselves, we also translate the feasibility of the project with those thoughts. Which existing systems and / or components can we reuse? What data can we make available via external links? Which tools and frameworks do we use to be able to develop quickly? In short, we aim for maximum results at the best price.

In case of a mobile app or portal, we make a demo; a translation of (part of) the desired functionality into a “clickable” design. This demo gives a realistic picture of the end product that you can also use to inform internal colleagues. When one wishes to have a B2B portal, we often build a prototype (or proof of concept – POC). We go a step further with a prototype. We then build the desired functionality based on the actual system environment. We notice that on the basis of a clickable demo and / or prototype, the wishes & requirements are often further refined.

We work according to Scrum in which you or a colleague takes on the role of product owner. In 2-week sprints we build functionality translated into user stories that have been coordinated with the product owner in advance. Our focus in the construction is on the MVP: Minimum Viable Product. Once this is up, you have the option to go live. We then continue to build on the project so that we can add extra functionality in sprints. Every sprint ends with a demo where you are more than welcome to participate. This is because we like to keep you involved in the construction. Our developers not only enjoy this very much, but above all it results in a close collaboration that contributes to the best end result.