Home    |      About Us     |      Services     |      Process        Contact Us 
 
 
 
 

1. Initial consultation

In the initial meetings, Mebron Technologies will discuss with the client the general needs and purpose of the project. There is no charge for this consultation. It is intended to discover the scope of the project, to assess if the goals are achievable, and if Mebron Technologies and the client can come to a suitable business arrangement.

Naturally, at this point the client should provide as much detail as possible so Mebron Technologies can plan and advise properly. However, this stage can be accomplished without 100% complete specifications.

2. Drafting of estimate

Once the initial consultation (1.) has been concluded, Mebron Technologies will assess the proposed project, explore different avenues to successfully achieve its goals and estimate the costs involved. This will be a range of prices depending on how precise the details given in the initial consultation (1.) were and on how many optional requirement were discussed.

Estimates can be presented to the client by email (preferred), fax or hard copy by mail or courier.

3. Approval of estimate / discussion of project requirements

If the client is comfortable with the estimates provided (2.), Mebron Technologies will discuss possibilities with him or her to formalize the structure and function of the software to be developed. During this stage the client will indicate which features are required and any preferences he or she has about their implementation.

4. Production of specifications (specs) and final quotation

Based on the discussion of project requirements (3.), and in coordination with the client, Mebron Technologies will produce a document outlining the precise details of how the proposed solution will work. In this document, Mebron Technologies will indicate cost breakdowns for each section of the project as well as delivery times.

Because the specifications serve as the "blueprint" for the final software product, it is important that they be as complete and precise as possible. Mebron Technologies staff will help define the specifications by carefully discussing options with the client. However, it is ultimately the responsibility of the client to provide Mebron Technologies with the details of what they want the software to do.

An example of a good specification is:

  • Mebron Technologies will provide a search feature to select members from the database based on information in the state, country, type of school, and grade level fields.

An example of a less appropriate specification would be:

  • Mebron Technologies will provide a search feature to select members from the database.

Specifications and quotations can be presented to the client by email, fax (preferred) or hard copy by mail or courier.

5. Formal agreement / payment of deposit

The client indicates his intention to proceed with the project by signing a copy of the specifications and final quotation (4.) and returning it to Mebron Technologies either by fax (preferred) or in hard copy by mail or courier. A deposit is required before development can begin. Typically the deposit is 50% of the total cost for small projects (less than US $1,000). For projects with larger total costs or that will be in development for a month or more, multiple payment deadlines may be specified by Mebron Technologies.

6. Development

After the formal agreement and deposit is received, Mebron Technologies will develop the software solution based on the detailed specifications (4.) and test the code on a sample site (where possible). Mebron Technologies will adhere strictly to the deadlines for delivery specified in the formal agreement (5.).

7. Final payment / installation of software

Upon completion of the software the client will pay any remaining balance to Mebron Technologies. When final payment is received Mebron Technologies will install the software to the client's network (if required).

8. Follow-up testing

After installation Mebron Technologies will consult with the client to ensure the software meets the stated project goals and functions properly in a normal working environment.