We have development center in Indore, India. New consultation center is shortly coming up in United States.

Yes, There is a local project manager for US clients. 

We use Skype, Zoom Meeting, GoToMeeting, or telephone calls for scheduling the meetings. We provide our customers with the access to our CRM (Customer Relationship Manager) tool, which allows them to monitor the progress of their project at any hour of the day. 

We use Skype, Zoom Meeting, GoToMeeting, or telephone calls for scheduling the meetings. We provide our customers with the access to our CRM (Customer Relationship Manager) tool, which allows them to monitor the progress of their project at any hour of the day.Additionally, to enable sensible and effective communication, we allow customers a 1-hour overlap as per their time zone. During this period, the customer can interact with the entire team or the main resource(s) depending upon t

The number of resources employed for a project depends entirely upon the scale and complexity of the project. For example - we allocate two developers, one tester and a part-time UI designer for a small project. In addition, each project will have a Technical Architect, Business Analyst and Project Manager. We can increase the number of resources depending upon the customer/project requirements. 

We are bound by the confidentiality agreement, and will be unable to share these details. A large number of full-time developers are a part of our pool, working on different in-house and client projects. At different times, the available resources are different and unique. You can be assured that only the best quality, trained and experienced resources will work on your project and meet your requirements. 

This clause is covered in the IP contract, and NDA is also signed between "{domain_name}" and the customer specifying the same. The same clause is also covered in the contract signed between "{domain_name}" and its employees. In addition, we audit our processes and train employees on a regular basis. These efforts ensure that our customers' intellectual property is always secure. 

We use FogCreek Kiln source code and version control repository. In addition, we are experienced with Visual Source Safe, Team Foundation Server, and other popular version control systems. 

A Peer Review practice is a part of our standard development process. Any code developed by an application resource is always verified by another application resource. Only after verification is the software released for testing. This practice is applicable only when the customer hires more than one developer. 

While we feel that providing comments for all public methods is a good habit, we comment only when it is "truly required". For instance, we avoid commenting on codes that have the correct method name. Through this practice, we avoid over-commenting and create codes that are easy on the eyes. 

We provide the SRS documentation to the client. The code will have comments to facilitate easy comprehension. Our documentation is comprehensive and self-explanatory. 

We will provide end-user documentation if the clause is included in the work contract and quoted by "{domain_name}".

We have a standard procedure of handling change requests from our customers. Firstly, we seek their approval for any change request. After the customer approves the request, we do an impact analysis. This allows us to deliver the timelines and cost estimates to the customer. Once the customer approves the estimates, we implement the changes.