top of page

What is a Client Specification?

Customer requirements specification are precise, detailed instructions from the client to the vendor that address all characteristics related to the project. The quality of the vendor is determined by how accurate they can meet all of the customer specifications. Before commencing any formal project, it is required for the client to complete a CRS (Customer Requirements Specification Document); with the aid of the project management team.

 

In our world of internet business development, we’re most interested in matching the business and operation requirements with the market needs and will stress this when assisting you with the CRS

 

.

What's the point?

 

The customer requirements specification document (CRS) should contain absolutely everything that is in your vision; including both front-end and administration portals. The customer requirements specification document (CRS) should not miss out a single function (no matter how small) and should not leave anything up to common sense or interpretation.

 

A customer requirements specification document (CRS) generally has eight categories of requirements:

  • Colours and Branding

  • Business Idea / Executive Summary

  • Target Market

  • Operational Requirements

  • System Requirements

  • Sales Text Copy

  • Website Features and Functions

  • Overall Website Functionality

 

 

 

 

 

 

What's in it?

Similarly with the functional specification document, the CRS (customer requirements specification) is not typically the most exciting task of your project, however is one of the most important. For a vendor to completely understand your vision, it is requested that all clients explain in detail how they foresee the project; leaving nothing up to interpretation. A well written customer requirements specification document will ensure that the correct technology is picked and there are no unforeseen additions mid-project which can prove very costly.

 

The main purposes of the specification should be:

  • Turning the customer requirements into functional documentation.

  • Turning the customer requirements into functional documentation.

  • A point of synchronization for the project team.

  • A basis for building a master plan and schedule with instructions to web developers on what to build.

  • A baseline for change control.

 

 

bottom of page