Buying the software was the easy part
Most software that gets abandoned was never badly chosen — it was badly rolled out. Data never migrated cleanly, nobody was trained, and within three months the team was back on spreadsheets. We do the part that decides whether it sticks.
How a rollout runs
1. Scope and data audit
We look at what you have now — spreadsheets, Tally exports, an old system nobody likes — and work out what actually needs to move. Most failed rollouts fail here, not later.
2. Configuration
Salary structures, GST rates, approval workflows, user roles, leave policies. The unglamorous work that decides whether the system fits how you already operate.
3. Migration
Historical data moved and reconciled, with a parallel run so you can prove the numbers match before you switch off the old process.
4. Integration
Connecting the new system to what you already run — Tally, biometric devices, WhatsApp, payment gateways, your website.
5. Training and handover
Role-specific training for the people who will use it daily, plus written documentation. Then thirty days of hand-holding while the habits form.
What you get
- A fixed-price quote before we start
- A named person accountable to you
- Parallel run before you switch over
- Written documentation you keep
- Role-specific training sessions
- Thirty days of post-launch support
Questions
Do you only implement software you recommend?
No. We will implement whatever you have chosen, including something you bought before you found us and including products we did not rank first. Our recommendation and our implementation business are kept separate on purpose — otherwise the advice would be worthless.
How much does implementation cost?
It depends almost entirely on data migration volume and how many integrations you need. A straightforward HRMS rollout for a fifty-person company typically runs ₹25,000 to ₹75,000. We scope and quote a fixed price before starting.
Why not just use the vendor's own implementation team?
Often you should, and we will tell you when that is the right answer. Where we add value is when you are moving between systems, integrating with something the vendor does not support, or when the vendor's team is stretched and you need someone accountable to you rather than to them.