Skip to content
Vivanet

An India team, without standing up an India operation first.

We build the team against your spec, run it on our payroll while you direct the work, and transfer it to your entity when you're ready.

Build. Operate. Transfer.

  1. 01

    2 to 4 months

    Build

    We recruit, onboard and ramp the team against your spec. You interview and approve every hire. Workspace, equipment and onboarding handled.

  2. 02

    12 to 24 months

    Operate

    Our payroll, our HR, our compliance, our attrition risk. You direct the work day to day. Monthly reporting on delivery, utilisation and retention.

  3. 03

    At term

    Transfer

    The team moves across to your entity, with documentation, tooling and process handed over clean.

Everything except the direction.

You direct the work day to day. We handle the rest. All of it is included in the engagement, nothing is passed through.

  • Payroll
  • Statutory compliance
  • HR
  • Workspace
  • Equipment
  • Recruitment and backfill
  • Attrition risk

Said plainly, because this surprises people.

In India, transfer typically means the employees resign from Vivanet and are hired by your Indian entity or GCC on equivalent terms.

You need an Indian entity, or to be setting one up before the transfer point.

Without a receiving entity there is nothing to transfer to. We'd rather raise this on the first call than in month twenty.

Who BOT is right for, and who it isn't.

  • A company committed to India for several years
  • Funding in place for at least twelve months of engagement
  • A product roadmap that justifies a dedicated team
  • The intent to have an India entity by the transfer point
  • A single project with a defined end date
  • An uncertain roadmap where capacity needs vary month to month
  • A company just wanting to try offshoring

Start with a delivery pod instead.

What people ask us.

  • What is build-operate-transfer?

    A model where we recruit and ramp a dedicated team to your specification, operate it on our payroll and under our HR and compliance while you direct the work, and then transfer the team to your own legal entity at an agreed point.

  • Do we need an Indian entity?

    Yes, or you need to be setting one up before the transfer point. Without a receiving entity there is nothing to transfer to. We'd rather raise this on the first call than in month twenty.

  • How long before we can transfer?

    The minimum term before transfer is set in the engagement, typically twelve months, long enough for the Operate phase to prove delivery and attrition stability.

  • What do you carry during the operate phase?

    Payroll, statutory compliance, HR, workspace, equipment, recruitment and backfill, and attrition risk. You direct the work day to day; we handle everything else.

  • How is BOT different from setting up a GCC ourselves?

    A GCC means establishing a legal entity, hiring an HR and compliance function, securing workspace and building a recruitment pipeline before you hire your first engineer. BOT lets you have a working team first and build the entity around it.

Thinking about an India team?

One conversation. We'll tell you honestly whether BOT fits, or whether to start with a pod and grow into one.