|
We can partner with our customers using a very flexible approach to suit their business and project needs. This approach can be based on:
|
Onsite/Offshore Model
Under this model, depending upon the specific set of services involved and scale of the project, we shall put in place a combination of onsite and offshore technical resources that will become a virtual extension of the customer's team. On an average, 70% of the total effort is done offshore and 30% at the customer's site.
Typically, an onsite coordinator or a small team from Esika will be located at the customer’s site to synchronize between the offshore team and the customer.
| 
Click to enlarge
|
|
Offsite/Offshore Model
In this model, we will have our own office close to the customer’s site. A team of engineers from this office will coordinate between the customer and the offshore team.The onsite/ offshore model have by far been the most successful one among the various models that have emerged.
| 
Click to enlarge |
The simple reason being unlike in the case of the pure offshore model, you have the satisfaction of coordinating and discussing requirements and deliverables with an onsite team, while at the same time enjoying the offshore cost advantage.
|
Pure Offshore Model
Under this model, the entire project is carried out offshore. We will not have any onsite presence. The customer interacts directly with the offshore team.
| 
Click to enlarge
|
Our Pricing Philosophy
Fixed Time & Price basis
Time & Material basis
Risk/ Reward sharing basis
Depending on the nature of the project, we can operate either on a fixed-bid basis or on a time and material basis. Our objective, as much as possible, is to give a clear estimate of potential costs on any project to customers, ahead of time. However, it has been our experience that it is not always possible to give an exact estimate until we have clear and detailed requirements that are signed off by the customer.
If clear and detailed requirements are not available, we follow an approach as follows:
To start with, we put together potential pricing for each phase of the project based on the initial information provided to us. Once this is approved, we proceed forward to clearly understand and document the requirements in a detailed manner. This requirements document is typically supported by a prototype – either in the form of an HTML wire-frame or screen designs with flow documentation. At the end of the requirements specification phase, we revisit and freeze the estimate for the rest of the project, since clear requirements become available now. In our experience, the numbers do not change much from our original estimates.
In case of continuous requirements like enterprise applications maintenance where a dedicated team is required for the project on an ongoing basis, we can price for the team on a monthly basis.
|
|
|
