Project from A to Z

Our projects are organized in four phases:

Web site development

1. Plan the Internet Site

Assess the goal and scope of the project. Agree on plans and establish contractual agreement.

2. Develop the Internet Site

Incrementally develop the application using our Agile approach. Prepare and launch.

3. Deploy the Internet Site

Set up domain, emails, hosting platform. Launch and make publicly available.

4. Exploit and Maintain the Internet Site

Optional phase aiming to sustain the application: supervising the execution, evolving functions and content, managing the SEO, and keeping the software updated to latest standards in particular to avoid security breaches and threats.


Our way of working


We have embraced the method of Agile Development. What this means in practice is that you are fully involved during the development, from day one until a fully operational application is ready that provides all the functions, the layout and the user experience you are aiming for.

Start with the essentials and evolve

One of the key insights that have led to Agile Development is that change is an essential and healthy component of software development. Essential, since it is extremely difficult – if not impossible – to grasp and formalize all the aspects that you would like to see in the system up front. Healthy, since it allows you to start out with a simple system that only provides the most important functions, and then have the system evolve as your own and your users’ experience grows.

See work in progress

Moreover, you will have access to fully functional versions as the work progresses. This will help you to better understand and prioritize different aspects of how the application should evolve.

Continuous test

Our Agile Development method also puts specific emphasis on automatic testing, that we apply from day one, ensuring a high confidence that the application behaves as it should. This is particularly important when new functions are introduced or when existing functions are modified. Unless you rely on comprehensive testing, changes that impact or even break some existing functions, may go unnoticed until they suddenly appear and maybe create large problems if the system is already in use.