L o a d i n g
how we do it

Sales Process

1
Initial Meeting

Gather high-level information in order to accurately quote the Discovery Phase. No charge.

2
Discovery Phase

Gather specific requirements in order to scope out the project in detail. This billable project usually takes 2-10 business days depending on the scale of the project.

3
Statement of Work

An SOW is a document that outlines the requirements and functionality of the project in great detail and separates them into manageble modules and features. This is the result of the Discovery Phase.

4
Proposal

The final quote to do the work including timelines and payment terms. 25% of the Discovery Phase amount is discounted from the final project cost if the client proceeds. Otherwise, the client is free to shop the SOW around for other quotes.

how we do it

Development Process

1
Database Design

The PM & entire development team whiteboard the database schema before implementation.

2
Work Flow Design

The PM & entire development team whiteboard the application framework and UX design.

3
Development

One team gets to work on the back-end and the other gets to work on the front-end.

4
Server Setup

A Network Engineer builds all necessary cloud servers and implements required security measures and database backups.

how we do it

Quality Assurance Process

1
QA Testing

Developers should never test their own work, so QA engineers thoroughly test the module or feature to make sure it works as expected without errors or bugs.

2
Bug Fixes

Bugs are reported back to the developers to fix and then repeat the QA testing process until the module or feature passes error-free.

3
Client Testing

Once the client signs-off on a tested module or feature it is considered to be complete. Changes beyond this step will require a Change Request, which could be subject to additional costs. (To be quoted separately)

how we do it

Deployment Process

1
Go Live

Merge code and deploy on the production server. This usually happens over-night for major updates in case something goes wrong.

2
QA Testing

QA testers ensure that the deployment was successful. There are differences between development and production environments, so what works in development may not necessarily work in production.

3
Standby
The entire team is on standby in case something goes wrong and we have to revert the new changes.

Have a project in mind? Let’s get to work.