Build Phase Execution
The build phase is a dependency puzzle wearing a project plan. The entity cannot open a bank account until incorporated; the lease wants a signatory the entity does not yet have; statutory registrations require the office the lease provides; IT infrastructure waits on the premises; and hiring — the thing you actually care about — waits on all of it. Run sequentially by separate vendors, these workstreams consume two or three quarters. Run as one program by an owner who has done it repeatedly, they compress into weeks that overlap.
We execute the build as that single program. Incorporation, capitalisation, and FEMA reporting run in parallel with site selection and lease negotiation; the registration stack — tax, labour, state-specific — is sequenced so nothing waits on anything it does not truly depend on; IT and security infrastructure is built to your global standards with local execution; and the HR framework — policies, contracts, payroll machinery, statutory enrolment — is live before the first offer letter needs it. The milestone that matters is not 'entity exists' but 'first cohort productive', and the program is designed backwards from it.
What this covers
- Entity incorporation, capitalisation, and initial FEMA compliance run in parallel with physical build.
- Office selection, lease negotiation, and fit-out management to your specification.
- IT and security infrastructure: networks, access control, and data protection to group standard.
- Complete registration stack: tax, labour, and state registrations sequenced for zero idle time.
- HR foundation: compliant contracts, policies, payroll, and statutory enrolment ready before hiring begins.
Who needs this
Companies committed to an India center that need it operational in months; global program managers who want one accountable owner instead of nine vendors; and teams whose first-hand India execution experience is limited.
How we deliver
- Single program plan with all workstreams sequenced against real dependencies.
- Entity, premises, infrastructure, and registrations run in parallel by one owner.
- Milestone tracked to 'first cohort productive', not 'entity exists'.
Why A2 Consultants
We have run this dependency puzzle enough times to know where the weeks hide — the build we deliver overlaps workstreams that sequential vendors run in series, and the difference is a quarter of your calendar.
Engagement & what to expect
The build runs as one program with a single owner and a milestone that matters: first cohort productive. Typical timelines run four to seven months from engagement to that milestone — entity and legalisation workstreams starting immediately, premises and infrastructure in parallel, registrations sequenced against real dependencies, and hiring launched as soon as the employment infrastructure can receive offers. Weekly governance keeps your leadership decision-ready without operational burden. The program hands off into operate phase with compliance clean, infrastructure running, and the hiring engine already turning.
Every week the build saves is a week your center is producing instead of pending — parallel execution is where those weeks come from.