In essence we probably work in the same way other suppliers should work, but the difference is in the detail. The sections below outline the way a typical project might progress:

Let’s assume you have contacted us because you think we might be able to help solve a problem related to software. In order to decide whether we can help, it is obviously essential that we fully understand the scope of the problem and how you foresee it might be solved.

Therefore, at no expense to you, we will invest our time to understand the issues, listen to your envisaged scenarios and look at any documents, sample data or other material you can provide that helps us understand the “big picture” of what you are trying to achieve.

Once we are satisfied we fully understand what you are looking for, we will present you with a set of ideas as to how we might be able to help solve your problem. Even if your specifications are fuzzy and subject to change, the ideas we present will include basic estimates of what we might charge and also an outline of how we would go about implementing those ideas.

If you think our ideas will work and might offer good value for money, we will then create what we call a “Project Scope” document. This is a document breaking the project down into various stages and “deliverables”. The Project Scope will include a more detailed breakdown of our charges. However big or small your project we think that creating a simple a statement of what we will do, when we will do it and how much it will cost will hopefully give you a good indication that we are the most appropriate people to help solve your software related problem.

If, once you have seen our quotation, you think we might be good partners for your project, then how we proceed from there, will obviously depend on what has been agreed within the project Scope document. In some circumstances the Project Scope might provide enough detail for us to start work immediately. For most projects we will need to create a more detailed “Functional Specification” document.
In essence the Function Specification document is a comprehensive project plan which details what will get done, who will do what and by when. We will use the Functional Specifications document to help manage and keep track of how your project is progressing.

We use a series of internet based collaboration tools to keep you informed about the progress of your project. We will always be conscious to strike the right balance between eliciting your feedback and respecting your time, but through a series of short discussions, you’ll see steady progress and will have all the information available to follow your project every step of the way.

This evolutionary approach makes it easy for you to give us feedback and confirm that the project is progressing in way in which you approve