A process in which you know what you are paying for at every stage

Details

Why we split projects into stages

An IT project bought “as a whole” has one serious flaw: you only see the result for the first time at the very end. If the assumptions were wrong, the cost of fixing them is as high as it gets.

That is why we split implementation into stages and launch the system after the first milestone. Users start working with real data, and we add further features based on what they have learned. Meeting deadlines remains the priority — the schedule is created together with the quote, in the analysis document.

What the pre-implementation analysis includes

• a description of the process as it is now and as it should be,
• the functional scope divided into stages,
• a quote for each stage and for the whole project,
• a work schedule with milestones,
• risks and technical assumptions,
• a plan for developing the system as the company grows.

The analysis is a separate, self-contained stage. After receiving it, the client can withdraw from the project — and keeps a document that retains its value regardless of who eventually carries out the implementation.

Support after launch

Already during the needs analysis we look at which direction the system may develop in. Good planning leaves room for expansion. After launch we offer full support: staff training, ad hoc help with problems and developing the system as your company changes.