Build your India
operating team.

A Pod is India-based operating capacity that away.center builds and runs for you. It can be one person, one recurring workflow, a small team of two to four, or a full India operating cell. What makes it a Pod rather than a hire is the layer around it: sourcing and vetting, an away.center workspace, WorkOS for tasks and visibility, SOPs, weekly reporting, delivery oversight and replacement support.

Yes, and most clients do. That's a Managed Role - one dedicated person, inside the operating system. You can add roles or convert repeating work into a Managed Workflow later, without restarting the relationship.

A Managed Role is one person. away.center owns hiring, workspace, WorkOS, visibility, reporting and replacement; you own the functional direction and the business outcome.

A Managed Pod is two to four people working as one unit, with a named delivery lead. away.center additionally owns the coordination between the roles and the delivery quality of the agreed scope. It's a bigger commitment on our side, so we're deliberate about when we sell one.

It's work bought as an output rather than as a person. CRM hygiene, outbound account research, founder follow-ups, content repurposing, support triage, AI SEO and visibility monitoring, weekly reporting. We'll only sell one where inputs are known, an SOP can be written, QA is possible and the output is measurable - because that's where we can genuinely take responsibility for the result.

A small India operating cell - typically starting at three people and scaling to five, ten or fifteen. It's the same intent as a global capability centre, at a size that makes sense for a company that isn't a multinational. away.center helps architect the team, hires it, houses it, runs the operating layer and plans the expansion, according to the model in your contract.

You choose. Some clients manage directly and use away.center purely for the infrastructure. Some want away.center's delivery lead running the day-to-day while they set direction and review output. On pods and Nano GCCs there's always an away.center delivery lead involved, because coordination is part of what you're buying. We agree the split in writing before anyone starts.

Yes. Your team works in your tools, on your rituals - WorkOS sits alongside them for role definition, task evidence, SOPs and reporting, rather than replacing your stack. Tool access, approvals and any security requirements are set up during onboarding.

India Standard Time is UTC+5:30, which gives natural overlap with Europe, the UK, the Middle East, Singapore and Australia, and a workable morning overlap with the US East Coast. We agree the required overlap window as part of the role card - shifted hours are possible where the role justifies it and the person has agreed to them.

From an away centre. away.cenetr operates spaces in Bangalore, Vizag and Kolkata; Away Pods currently deploys from Bangalore, with Kolkata and Vizag following as workflows mature. Working from an actual designed workspace rather than a bedroom is a deliberate part of the model, not an add-on.

There's a defined replacement process, and we keep a backup candidate identified on roles wherever we can. Our internal target is a replacement shortlist within seven working days and a completed transition within fifteen, with knowledge handed over and a transition report. The specific replacement terms that apply to you are set out in your agreement.

Role intake, then a job description, sourced and scored candidates, a written communication check, a role-specific assessment, human screening and interviews - then your shortlist and final selection. We score for communication, role skill, reliability, judgement, learning speed, comfort with AI tools, ownership and coachability. You make the final call on every hire.

It depends on the structure you choose, and it's written into your agreement. away is not automatically your employer of record or legal employer. Some clients employ or contract people directly through a platform such as Deel, Rippling or Remote, with away.center providing the hiring, workspace, WorkOS and delivery layer above it. Others take a fully managed arrangement with away.center. We'll walk you through the options; decisions about employment structure should be taken with your own advisers.

Employment, payroll and compliance infrastructure is either arranged by you directly or coordinated through appropriate platforms and partners, depending on the model in your contract. away.center does not provide legal, tax, immigration or compliance advice, and does not hold itself out as a payroll provider or compliance adviser. Where away.center coordinates administration, the scope of that coordination is defined in the agreement.

Yes - we're designed to sit above them rather than compete with them. The platform handles employment infrastructure, payroll and records. away.center handles role design, sourcing, workspace, WorkOS, SOPs, reporting, delivery support and replacement. If you already have one of these, keep it.

Yes - frontend, backend, full-stack, QA and infrastructure support are all roles we can architect and hire for. Engineering is typically bought as Managed Roles or a Managed Pod, because you own the technical direction and the product outcome. We won't sell engineering as a Managed Workflow unless there's a genuinely repeatable, SOP-backed workstream underneath it.

Yes, and support is one of the better candidates for a Managed Workflow - ticket triage, first response, knowledge-base upkeep, escalation handling and support reporting are repeatable and measurable once the rules are clear. It can start as one Managed Role and convert as the SOPs settle.

Yes. AI automation associates, workflow automation engineers, n8n / Make / Zapier specialists and AI QA operators are all roles we hire for. Typical work is SOP mapping, building and maintaining automations, prompt library setup, tool integration and reviewing AI output - the human layer that keeps automations working after they're built.

That's the intended path. Start with a role, watch what repeats, convert the repeating parts into workflows, group them into a pod, and grow the pod into a Nano GCC. Because the role cards, SOPs and reporting exist from day one, each step adds to what's already there rather than starting again.

The diagnostic and architecture usually take days rather than weeks. Hiring time depends entirely on the role- a well-defined execution role moves considerably faster than a senior specialist. We'll give you a realistic timeline for your specific role upfront rather than a headline number, and onboarding runs as a structured 10-day sprint once someone is selected.

You own approved deliverables, per the terms of your agreement. away.center retains its own pre-existing templates, SOPs, tools, systems and WorkOS intellectual property. IP, confidentiality and data-access terms are set out in the master services agreement and statement of work.

For individual roles, pricing is based on the role, city, experience level, workspace and device needs, and how much management sits with away.center. For workflows, pods and Nano GCCs, pricing is based on scope, complexity, volume, SLA and delivery responsibility. It's quoted as one monthly figure in a written proposal, with a setup fee and first month upfront. We don't publish rate cards because the honest answer depends on the role.

Yes - that's the whole point of the Managed Workflow level. But we'll only take output responsibility where the workflow is genuinely definable: known inputs, a written SOP, a QA checklist, a measurable output and an agreed SLA. If the work is still ambiguous, we'll tell you it should start as a Managed Role and convert once the pattern is visible.

Yes. Device and work setup is coordinated as part of onboarding, specified against what the role actually needs - a designer and a support associate don't need the same machine. Device arrangements are confirmed in the proposal.

Yes, and we'd encourage it if you're anywhere near one. away centres run day passes and hourly options, so you or a colleague can see the floor your team would be working on before committing to anything.