Our Process

Home > About > Process

RALLP executes its solutions in 12 primary steps. The process may be shortened for a simpler project or a standard solution. Starting with basic understanding of requirements to maintaining the system.

1. Initial connect

In this phase, our sales team learns the basic pain points from the client. The overall business structure of the client is also understood. At the same time, our team will explain in brief the capabilities of our team, and solutions that have been executed in the past. A ballpark estimate of the cost of the solution is also given to the client at this time. If the client feels that RALLP will be able to handle the issue, and the cost will be within budget, we move to the next step.

2. Detailed Study

In this step, we do a deep analysis of the complete process. We work with the base idea given by the client, but explore a few levels deeper. Based on the experience our process team has working on other projects, they are sometimes able to identify deeper issues which can be solved with our solutions. The team also interacts with the frontline employees of the client, who will actually be using the system. By understanding the mindset of the users, the UI design is customised for best user adoption.

3. Preliminary Proposal

Once the detailed study is completed, a preliminary proposal is formulated. This proposal includes solutions for the primary problem discussed in the initial connect, and takes inspiration from the detailed study. The solutions may also include any secondary pain points identified in the detailed study. A clear commercial offer is also submitted at this point.

4. Client Discussions

The preliminary proposal is put in front of the client management. A representative of the frontline employees is also encouraged to attend the technical discussion.

5. Final Proposal

Based on the outcome of the client discussion, sometimes part of the solution is accepted, sometimes the complete solution is accepted. In some cases the client needs additional features. A final offer is built and sent to the client with a commercial offer.

6. Order Placement

After commercial negotiations, the client places an order. In case of smaller businesses, an email confirmation along with advance payment is also considered as a binding order.

7. Execution

On receipt of PO and Advance payment, RALLP begins the execution of the solution. This may vary from a few hours to a few weeks based on the complexity of solution. Some highly complex solutions are also executed in phases, with different teams working on different aspects of the project. The client will always communicate with one contact person (SPOC/ Project manager)

8. Training and Initial Test

Once the solution is ready, the client is provided online credentials (in case of cloud system) or a download link (in case of on-site system). The end users are given training (online or on-site) to use the system. The system is put in test-mode, so any data entered is only temporary. This allows the users to explore the entire system and check all features and possibilities. The test generally lasts for 1-2 weeks. It is expected that in this time, the end users come up with a list of issues or improvements required in the system.

9. Primary Update

While the client team is testing the system, RALLP QA team also tests the system internally. After 1-2 weeks, the points provided by the client and the QA team are merged and handed to the dev team. The primary update is executed and all the points are retested by the QA team. This generally takes up to 1 week.

10. Endurance Test

Once the primary update is patched, the system is purged of the testing data. At this point of time, the system is live. Although the users are encouraged to explore the system, any data they enter is considered as real data and will remain in the system unless specifically removed. The endurance test is carried out for 1-2months during which the client team operates the system normally. Any inconvenience in the system is sent across to RALLP. Generally after a month of operation, the users are expected to get a clear idea of the system and are able to understand better than anyone what change can best improve the system UI

11. Secondary Update : Fine tuning

The points sent across by the end users are evaluated by RALLP with client management, and on approval, the required changes are pushed to the application. This is a live update and is pushed after testing on an alternate server. Even though the update only takes a few minutes, it is generally carried out after 10 PM to ensure minimal impact on normal client operations.

12. Long term service mode (LTSM)

Once the secondary update is complete, it is expected that the system will run smoothly without need for any developer intervention. However, from time to time, the client needs minor changes in the system, such as a new report or a new performance indicator. RALLP carries out live updates to the system while it is under LTSM. Systems under LTSM are also routinely updated for bug-fixes and UI improvements in line with the latest trends.