Onboarding
From signed to live in the field.
Onboarding is included in every plan and starts the week you sign. Here is the actual sequence, what we need from you at each stage, and when the old process stops.
single-project rollout
Email + WhatsApp · next-business-day
multi-project rollout
Priority WhatsApp · 4-hour response
dedicated rollout team
24×7 SLA-backed · dedicated CSM
Onboarding is included in the annual fee — never invoiced separately.
The sequence
What happens, week by week
Timings below follow the Growth rollout. Starter compresses this into two weeks on one project; Enterprise extends it across entities and states.
Kickoff and data collection
The agreement is signed and rollout starts the same week. We run a kickoff call with your project lead, agree the first project to go live, and collect what the system needs to exist: your project list, employee list with statutory identifiers, the BOQ for the first contract, and your current vendor list.
- A named project owner on your side
- Project list and employee list
- BOQ for the first contract
Core setup and the first project on attendance
We create projects, users and roles, then put one project onto mobile attendance. Attendance goes first on purpose — it is the smallest change to a field supervisor's day and the input every other module depends on. It runs offline and syncs when the phone finds network, so a project site with no signal is not a blocker.
- One field supervisor available for a 30-minute walkthrough
- Confirmation of who approves what
Daily logs, materials, and the paper register stops
The same project adds daily progress logs and material issues to a routine the field supervisor is already doing on the phone. We run attendance in parallel with your paper register for one cycle, compare the two, and once they agree the paper register stops. Running parallel longer than one cycle just doubles the work.
- One attendance cycle run in parallel
- Sign-off that the two records match
BOQ, billing, and the first progress bill
We import the BOQ, set up rate analysis and the certification workflow, and generate one progress (RA) bill from certified quantities. You compare it line by line against the bill your billing engineer produced by hand. When they match, the retyping step between measurement and bill is gone for good.
- Your billing engineer for two short sessions
- A recent progress bill to compare against
Payroll at a clean cycle boundary
Payroll always moves at a month boundary, never mid-cycle. We run one cycle in parallel, compare gross, statutory deductions and net per employee against your existing sheet, resolve any differences, and then cut over. PF, ESI, PT and TDS are calculated against their slabs as part of the run.
- Finance or HR for the parallel run
- Last month's salary sheet to reconcile against
Remaining sites, then a support cadence
Further projects roll out one at a time, usually taught by the field supervisor who adopted it first rather than by us. From there you are on your plan's support cadence, and we review usage against your plan limits before renewal.
- A project-by-project rollout order
- One internal champion per region
Questions
Onboarding, answered
Moving off spreadsheets specifically? Our Excel migration guide covers what to migrate, what to leave behind, and how to run parallel without doubling the work.
Want to see the rollout plan for your projects?
We will map your current spreadsheets to a week-by-week plan for the first project.