Presentation and Demo/ Proof of Concept


Presentation and Demo

Typically following the proposal stage, we will prepare for a presentation and demo of the proposed software.
The software may be tailored to some extent, audiences do need to appreciate however that it will be quite generic, since it would not be practical for us to highly reconfigure the software for every presentation.
One courtesy we would ask from prospects to which we present, is that they try their best to get ALL key personal that may be impacted by the proposed system to attend. Also we typically need 3 to 5 hours for such presentations, this may seem a long time but we feel that for such systems, which whole organisations may have to live with for 5 to 10 years, such an investment of time is essential.
To help ensure a valuable and relevant presentation, it helps if we can obtain scenarios the prospect would like to see, a week in advance. Also the more interactive the sessions are the better.

Proof of Concept


In some instances prior to large and complex implementations we will run workshops.
During the workshops our consultants will spend time with users, mapping and documenting their key business processes. This process assists with the education process on both sides and helps to ensure that any proposed solution is a good match for the organisation's requirements.
Knowledge gained from workshops will often be used to develop specific and detailed demos of the proposed software. During the normal sales process the amount of specific configuration and tailoring that is possible is more limited; therefore users need to make judgements based upon generic type demos.
Workshops are chargeable, some of this expense however helps towards a faster and smother implementation should the customer progress to the next stage, which they typically do.

Trial /Pilot Systems

In some instances we can obtain trial software keys for use on proof of concept / trial systems.
It is difficult to properly assess a system unless it has been properly configured to meet the user’s requirements, so if we agree to a proof of concept then we will also insist on significant consultancy - to ensure that it may be installed and configured, so that there is a reasonable chance of a fair evaluation. Going down this route will naturally result in a larger total cost and lengthened total time of implementation.

Comprehensive Proposal

Typically following several consultations and meetings we will have a reasonably good understanding of requirements we then typically prepare, free of charge, a comprehensive Proposal document which will cover:
  • Our Understanding
  • Specifications and Scope
  • Proposed Solution
  • M4 / Microsoft background
  • Product descriptions
  • Project Management methodologies
  • Full Details on all costs involved
  • License terms
  • Terms and Conditions
  • Service Level Agreement terms
The document is intended for several audiences and to cover all major issues up front so that realistic expectations are set this helps prevent misunderstandings and supports our goal of an excellent long-term relationship with all of our customers.