Skip to main content
Pods of two to six. Assistants, a lead, and an operations manager.

Hire a Virtual Assistant Team in India That Only Works for You

One assistant covers a person. A team covers a function. This page is about the second thing.

You get a small group of assistants in India who sit inside your systems, follow your written procedures, and answer to you or to a lead you appoint. We recruit them, employ them, run their payroll and statutory paperwork, cover them when they are ill, and find you somebody new if one of them leaves. Seats start from $960 a month, and Rita will send you the full rate card in about a minute.

Just One Assistant? Start Here
$960
Entry seat, monthly
48h
Shortlist in your inbox
160h
Per full-time seat, monthly
30 days
Free replacement window

The week one assistant stops being enough

Almost nobody starts here. You hired one assistant, it worked, and for a while the only problem you had was wishing you had done it sooner. Then something shifted. The moment is usually easy to date, because it feels like the opposite of progress: you got help, and you got busier.

Four signals show up, usually in this order. Watch for the second one in particular. People misread it as a performance problem when it is really a structure problem.

Work queues instead of clearing

Requests that used to turn around the same day now sit for two. Your assistant is not slower. There is simply more arriving each morning than one person can finish before they log off, and the overflow compounds every week.

You became the answer desk

Count the hours you spend each week responding to your assistant with clarifications, approvals and links. When that number passes four, you have quietly created a second job for yourself. A second assistant does not fix this. A lead does.

One illness stops a function

Your assistant has a fever on the day payroll needs approving, and three client invoices go out late. Nobody else knows where the file lives. This is where a single seat stops being a convenience and starts being a risk you are carrying uninsured.

The work has split into different jobs

Inbox and calendar want a careful, calm person. Listings and data want somebody fast and repetitive. Chasing customers wants somebody who enjoys chasing. You have been asking one person to be three different temperaments.

The trigger for a team is not a volume of tasks. It is that second signal. As long as every question routes back to you, adding people makes your day worse, because each new person arrives with their own stream of questions. The whole point of a pod is that somebody other than you answers most of them.

Here is a quick test. If your assistant went quiet for a week, could anybody else pick the work up from written instructions alone? If the answer is no, you do not have an assistant problem. You have a documentation problem, and it will follow you into every hire you ever make. There is a section on that further down, and it matters more than the price does.

Who is actually in a pod, and what each person owns

Four levels, and you rarely need all four at once. Every seat is full time at 160 hours a month unless you ask for part time, and every seat is exclusive to you. Nobody in your pod is answering another client between your tasks.

Level What sits with them Typical experience You add this level when
Virtual Assistant Inbox triage, calendar, data entry, listings, CRM hygiene, research, document prep. Executes written procedures and flags anything outside them. 2 to 4 years You have repeatable work somebody can learn from a written card.
Senior Virtual Assistant Owns a whole area rather than a task list. Writes the procedure the others follow, handles exceptions, and does the work nobody has documented yet. 5 to 8 years The work needs judgement, or nothing is written down and somebody has to write it.
VA Team Lead Runs the daily queue and the standup, checks quality before it reaches you, answers the questions you were answering, holds the escalation rules. 6 to 10 years You hit three or more assistants, or you are spending four hours a week answering them.
Operations Manager Owns the outcome, not the queue. Reporting, capacity planning, process redesign, hiring input, and the weekly conversation with you about what to change. 8 years and up The pod has become a department and the person running it should not be you.

Specialists sit at the assistant and senior levels rather than in a separate track. If your pod needs somebody who lives inside Amazon Seller Central, or somebody who knows what a comparative market analysis is, we recruit for exactly that. Property teams have a page of their own: real estate virtual assistants covers that work in detail, and this page will not repeat it.

The lead is the level people skip, and skipping it is the most expensive decision on this page. Adding a lead costs you one seat. Not adding one costs you the checking, forever, at whatever your own hour is worth. Individual role pages sit under the virtual assistant services hub if you would rather start with a single seat and grow into a pod later.

What does a virtual assistant team in India actually cost?

Seats start from $960 a month. Where your own number lands depends on the mix you pick, and this section is about how to work that out rather than a price list. We send the full rate card, role by role, when you ask for it: tell Rita what you are trying to staff and it comes back with the numbers against your actual shape rather than a generic table you have to translate.

Three shapes cover most small businesses. Pick the one that matches where you are, then read what moves the number.

The pair
Two full-time assistants
  • One owns inbox, calendar and client communication
  • One owns data, listings and back office
  • They cross-train on each other’s two most critical tasks
  • You are still the escalation point

Right when you have 60 to 80 hours a week of delegable work and answering questions yourself has not yet eaten your day.

The pod with a lead
Three assistants and a team lead
  • The lead runs the queue and checks work before you see it
  • You get one daily summary instead of eleven questions
  • Any one person can be off without leaving a gap
  • Procedures get written by the lead, not by you

Right when you crossed four hours a week of answering your own assistants, or work started missing deadlines nobody noticed until a customer said so.

The function
Four assistants, a senior VA and an operations manager
  • A whole business function runs without you inside it
  • Weekly reporting against numbers you agreed up front
  • Two shift windows, so coverage spans your working day
  • Capacity planning happens before you feel the strain

Right when support, admin or back office is a department rather than a chore, and the person running it should not be you.

Want the numbers against your shape?

Tell Rita which of the three shapes you are closest to, your hours and your time zone. You get the full rate card for every level in the pod, plus a monthly total for that exact configuration. It takes about a minute and there is no call to sit through.

What moves your number up, and what moves it down

Pushes it up
  • Seniority. A senior assistant or a lead costs more per seat than an assistant, and both are worth it once the queue needs judgement.
  • Shift premium. Hours outside roughly 09:00 to 19:00 India time carry one, and a full overnight shift carries the largest.
  • Named software skills. Deep experience in a specific platform narrows the hiring pool and moves the rate.
  • Regulated or licensed work, where the screening and supervision burden is heavier.
Pulls it down
  • Team size. Per-seat rates step down once a pod passes three people, because recruitment and management amortise across the group.
  • Part-time seats. Half a seat is often the right way to add a second person before you are ready for a whole one.
  • Working India-friendly hours, which removes the shift premium entirely.
  • Documented work. A role somebody can learn from a written card is a cheaper role to fill than one that lives in your head.

How the engagement is priced, and where our margin sits

Most staffing companies will not tell you what you are actually paying for, so here it is plainly. One monthly figure per seat covers the assistant and everything it takes to keep them employed and working. That is the entire model. There is no setup charge, no recruitment fee at the front, and no separate line for HR or admin later.

The fee is the everything-else. It pays for sourcing and screening the shortlist, running an Indian payroll and the statutory filings that go with it, the HR function that handles leave and grievances and appraisals, cover when somebody is sick or on holiday, laptop and connectivity, workspace where the role needs one, and re-recruiting the seat if the person leaves. Knowing the percentage is more useful than a per-seat number you cannot decompose, because it tells you what happens as your pod grows and what you would be taking on yourself if you tried to run an Indian entity directly.

Covered by the engagement

Salary and every Indian statutory employer cost, recruitment and screening, payroll and compliance, HR, laptop and internet, a monitored workspace where the role needs one, paid cover during illness and annual leave, and replacement recruitment if somebody leaves.

Billed separately, or not at all

Your own software licences, because your team works in your tools on your accounts. Any shift premium for hours outside the standard India window. Ad budgets, subscriptions, courier costs and anything else you would be paying for regardless of who did the work.

The same job, hired where you live

Whatever we quote you, the comparison that decides it is what the same role costs at home. Here is that number with the sources attached rather than a savings percentage, and fully loaded, because the loaded figure is what actually leaves your bank account.

One administrative assistant, hired locally Base pay Employer costs on top Monthly, fully loaded
United States $47,540 median 50.4% of wages $5,958
United Kingdom £34,954 median 15% NI above £5,000, plus 3% pension $4,491
Australia A$91,686 12% superannuation $5,939

US base pay is the median for Secretaries and Administrative Assistants, excluding legal, medical and executive, SOC 43-6014, covering 1,706,790 people (BLS Occupational Employment and Wage Statistics, May 2025). The 50.4% loading is what US employers pay in benefits and payroll taxes on top of wages for office and administrative support roles (BLS Employer Costs for Employee Compensation, March 2026). UK base pay is the full-time median for personal assistants and other secretaries, SOC 4215 (ONS ASHE 2025, provisional), with employer National Insurance at 15% above the £5,000 secondary threshold and auto-enrolment pension at 3%. Australian base pay is full-time non-managerial employees paid at the adult rate under personal assistants and secretaries, ANZSCO 521 (ABS Employee Earnings and Hours, May 2025), plus the 12% Superannuation Guarantee. Converted at GBP 1.337 and AUD 0.694 to the dollar (US Federal Reserve H.10, 13 July 2026).

Notice where the gap actually comes from. It is not mainly that Indian wages are low. It is that employer costs sit in a different place. A US employer adds benefits and payroll taxes on top of the salary, and for office and administrative roles that loading is 50.4% of wages, higher than the 43% average across all private-sector jobs (BLS, March 2026). In India those obligations are already inside the quoted figure, and they are modest: employer provident fund is capped at ₹1,800 a month, employee deposit-linked insurance adds 0.5% of wages, and gratuity accrues at fifteen days of pay for each completed year.

A second, quieter line item is the one nobody budgets. US employers reported an average cost-per-hire of $5,475 for non-executive roles in 2025 (SHRM 2025 Benchmarking Reports, published October 2025). That is what you spend before anybody has done a day of work, every time a seat turns over. It sits inside our rate rather than on your invoice.

One honest caveat on the direction of travel. Aon in February 2026 and Deloitte India in April 2026 independently project Indian salaries rising 9.1% during 2026. Indian pay is not frozen, and no provider rate can be frozen forever either. We hold your rate for the contracted term, which is a real reason to fix a number now rather than next year. For the wider engagement models, the freelancers versus dedicated remote teams comparison works through the crossover maths in more detail.

Week one is about your procedures, not your assistants

Search around for why offshore assistant engagements fail and you will find a lot of pages blaming the assistants. Our experience, and the research, point somewhere less comfortable. The usual cause of failure is that the buyer had never written down how the work is done, so the first month became an expensive game of twenty questions and both sides concluded it was not working.

This has been studied properly. Dibbern, Winkler and Heinzl looked at six German financial-institution projects offshored to India and published the findings in MIS Quarterly in 2008. They found the extra cost clients carry falls into four buckets: specifying requirements, transferring knowledge, control, and coordination. Every one of those is a documentation cost. It is real, it lands in the first weeks, and pretending it does not exist is why people are surprised by it.

The five-task rule

Do not hand over twenty-five tasks in week one. Hand over five, and pick the five that are boring, frequent, and low-risk if they go slightly wrong. Recurring reports. Calendar scheduling. Data entry into one named system. Inbox triage against rules you define. Chasing something that has a clear deadline.

You are not testing whether your assistants are capable. You are testing whether your instructions are. When a task fails in the first fortnight, the instruction is wrong far more often than the person is.

How the documentation gets built without you writing it

The trick most people miss is that you should not be the one writing the procedures. You should be the one being recorded. Here is the sequence we run.

Days 1 to 3
You record yourself working

You do the task once, out loud, with your screen recording. Ten minutes each, five tasks. No script, no polish, no editing. Talking through your own reasoning is what makes the recording useful, because the reasoning is what nobody can guess.

Days 3 to 5
Your team writes the card

Your assistants watch the recordings and write a one-page card per task: what triggers it, the steps, the systems it touches, what finished looks like, and the rule for when to escalate instead of guessing. They wrote it, so they own it. You edit rather than author.

Days 5 to 8
They do it, you watch

They run the task with you observing. Every question that comes up becomes a line in the card. By the third repetition the card should be good enough for a stranger to follow.

Days 8 to 12
They run it, you spot-check

They work unsupervised. You review a sample rather than everything. When a card holds up under a sample check twice in a row, that task is done and you never touch it again.

From day 12
The next five tasks

Repeat. Most small businesses move twenty to thirty tasks across in the first quarter this way, and by the end the cards are a genuine operating manual that outlives any individual.

The one habit that prevents most of the trouble

End every call with a written recap. Not a summary of the call, a list of what was decided and who is doing what by when. Erin Meyer, whose book The Culture Map is the standard reference on this, gives exactly that advice and adds a second half people skip: the recap is the manager’s job as much as the team’s. If you are the one who spoke, you are the one who writes it down.

There is a cultural mechanic underneath this worth naming plainly. On Hofstede’s national data, India scores 77 on power distance against 40 for the United States, 38 for Australia and 35 for Great Britain. In a workplace culture with a gap that wide, a junior person does not spontaneously tell a client their instruction was unclear, and silence reads as agreement when it is not. The complaint you will hear from managers who did not plan for it is always the same: nobody asked any questions, and later it turned out nobody had understood.

The fixes are unglamorous and they work. Ask for the instruction back in their words rather than asking whether it is clear. Make escalating a defined action with a rule attached, not a judgement call about whether the client will mind being interrupted. Give the lead explicit permission to push back on you, in front of the team, so everybody sees it happen once. And take Meyer’s own guardrail seriously: culture sets a range, individuals choose within it. This is about designing a protocol, not about assuming anything about a person.

Whichever way you run it, do the process design while the team is forming. Habits set in the first fortnight and they are considerably harder to change in month four.

How do the hours actually line up with your working day?

Here is the fact competitors write around. Indian clocks sit five and a half hours ahead of Coordinated Universal Time and never move for summer time. Put a normal Indian office day next to a normal American one, nine until five on both ends, and the shared working time comes to zero hours, wherever in the United States you sit. Not small. Zero, on the East Coast and the West Coast, in summer and in winter.

Wherever this industry advertises American overlap, an Indian employee gave up their evening to create it. Nobody gets that for free. So the useful question is not how many hours you are promised. It is which person is awake at 2am to deliver them, and whether their pay reflects it. Ours are, through a shift premium, and that premium is in your quote rather than hidden.

Your market India shift window Your local hours covered Live overlap
UK and Ireland 13:30 to 22:30 IST 08:00 to 17:00 Full working day
UK and Ireland, no evening shift 09:30 to 18:30 IST 04:00 to 13:00 GMT 4 hours
UAE and the Gulf 09:30 to 18:30 IST 08:00 to 17:00 Almost the whole day
Sydney and Melbourne 05:30 to 14:30 IST 10:00 to 19:00 AEST 7 hours
US Eastern, partial 14:00 to 23:00 IST 03:30 to 12:30 EST 3.5 hours
US Eastern, partial and later 16:00 to 01:00 IST 05:30 to 14:30 EST 5.5 hours
US Eastern, full cover 18:30 to 03:30 IST 08:00 to 17:00 EST Full working day
US Pacific, full cover 21:30 to 06:30 IST 08:00 to 17:00 PST Full working day

Client business day assumed as 09:00 to 17:00 local. Offsets are arithmetic from published UTC offsets and hold year-round on the India side, because IST has no daylight saving rule.

Three things to decide before you pick a window

Stagger the pod rather than shifting all of it. In a four-person pod, putting one or two people on your hours and leaving the rest on India hours usually beats moving everybody. The people on your window handle anything conversational. The rest work through the queue while you sleep, and you wake up to finished work. Blanket night shifts cost a premium on every seat and narrow the hiring pool for all of them.

A response-time commitment beats an overlap obsession. For most administrative work, what you actually need is not somebody staring at Slack at the same moment as you. It is certainty about when you will hear back. Put a response window in writing, per channel, and you will feel a thirteen-hour gap far less than you expect. There is no research anywhere behind the popular claim that you need four hours of overlap, and we are not going to pretend otherwise.

Re-base the roster four times a year, not twice. Because Indian clocks never move, every change is yours, and the gap changes with it. American clocks go forward on March’s second Sunday while British and European ones wait until the last Sunday of that month. Coming back, America returns on the first Sunday of November and Britain a week or two earlier, on October’s final Sunday. If you serve both, there are two or three weeks a year when your offsets to New York and London have moved apart, and the rosters need checking four times, not two.

One more scheduling reality nobody mentions until it bites. Indian public holidays barely overlap with yours, several shift with the lunar calendar and are confirmed at short notice, they vary by state, and they cluster: Dussehra falls on 20 October 2026 and Diwali on 8 November 2026. So the contract carries a dated holiday schedule tied to the city your team actually sits in, names the days you need worked whatever the calendar says, and balances those against cover we get back at Christmas and Thanksgiving. Guidance on running the mechanics day to day sits in our guide on managing a remote team across time zones.

Access, passwords, and what you should never hand over

The question every buyer asks eventually, usually late, is what these people will be able to see. Competitor pages answer it with the word NDA and move on. An NDA is a remedy after the damage; access design is what stops the damage. Both matter, in that order.

The rule is simple and it does not change with team size. Grant the narrowest access that lets the task be done, grant it through a system you can revoke centrally, and never grant it by sending a password.

Reasonable to grant
  • Delegated mailbox access, so nobody ever holds your email password
  • A named user account per person, never a shared login
  • Shared vaults in a password manager, with entries hidden from view
  • CRM, helpdesk and project tools at the permission level the role needs
  • Read-only access to accounting where the job is reconciliation, not payment
  • A company device, or a managed browser profile on their own
Keep for yourself, always
  • Payment authority in any banking or card platform
  • Super-admin or owner on your Google Workspace or Microsoft 365 tenant
  • Your domain registrar and DNS
  • Payroll approval, and the final release step on any outbound payment
  • Anything that can delete data irreversibly or export it in bulk
  • The second factor on accounts that hold customer data

Offboarding, which almost nobody publishes a policy for

People leave. That is not a disaster if the leaving is designed. What turns it into one is discovering three months later that a former assistant is still in a shared inbox because nobody kept a list of what they had. Ours runs to a checklist, and you should hold us to it.

Within one hour of the last shift

Every named account disabled, sessions terminated, device wiped or returned, and the password manager vault access revoked.

Same day

Any shared secret they could have seen is rotated, whether or not we think they saw it. Rotation is cheap; assuming is not.

Same day

File and document ownership transferred to a named person still on the team, so nothing is stranded in a dead account.

Within 48 hours

You receive a written access report listing every system that person had, the date access was removed, and who now holds it.

At handover

Their procedure cards are reviewed and reassigned by name. The knowledge stays with you, because it was never in one head to begin with.

Where you actually stand legally

India has more law behind this than most buyers realise. Under section 72A of the Information Technology Act 2000, a service provider who leaks material it reached through a lawful service contract is committing a crime, not merely a breach. Very few countries put a criminal penalty behind exactly this scenario, and it sits above whatever your own agreement says.

There is a statutory privacy regime behind that as well. India’s Digital Personal Data Protection Act took assent in August 2023, the Rules that operate it were notified two years later in November 2025, compliance is phasing in across eighteen months, and a failure to maintain reasonable security safeguards can be penalised up to ₹250 crore.

European and British buyers should check one detail carefully, because plenty of providers fumble it. Brussels has never granted India an adequacy decision, so EU personal data travels there on the European Commission’s Standard Contractual Clauses. British data is a separate instrument again: either the ICO’s International Data Transfer Agreement, or those same European clauses with the UK Addendum bolted on, since the European set does not cover a British transfer by itself. A transfer risk assessment goes alongside either route. Any provider who waves the European clauses at your UK data has skipped the ICO guidance.

Sick days, resignations, and the assistant who is not working out

Three different problems that get treated as one. They need different answers, and only one of them is an emergency.

Somebody is off for a day or a week

This is the easy one, and it is the single best argument for a pod over a solo assistant. Every person in your team cross-trains on the two most critical tasks belonging to somebody else. Not everything, because that is theatre and nobody retains it. Two tasks each, refreshed quarterly, and named in writing so there is no confusion about who steps in.

In a pod of four, one person being out means a documented handover and a slightly longer queue. With a single assistant it means a function stops. That difference is the product.

Somebody resigns

Let us deal with the attrition question honestly, because you will hear a number thrown around. In Indian business process work, attrition is genuinely higher than in software: Genpact put its 2025 figure at 24% in the company’s own annual filing, and WNS reported 31% for financial year 2024. We are not going to pretend those numbers are small.

What we will do is put them next to the domestic benchmark nobody publishes. TTEC, a US-headquartered customer experience operator with around 51,000 employees, disclosed overall employee attrition of 57% for 2025 in its own annual report, improved from 64% the year before. If you have ever staffed an administrative or support function domestically, you already know turnover in this kind of work is a fact of the work, not a fact about India.

The Indian notice period cuts in your favour here. Statutory notice is typically thirty days, and technology and services contracts commonly set longer, with legal guides putting the practical range between fifteen and ninety days. That is a far longer runway than at-will employment gives you. It is slow on the way in and slow on the way out, and for a team you are trying to keep stable, that trade is a good one.

Mechanically: you find out on the day somebody hands in notice, not in the fortnight before their last shift. Recruitment for the backfill starts that day at our cost. The leaver spends their notice period handing over to a named person with their procedure cards in front of them. And if the timing is bad, we cover the gap with an interim from another pod rather than leaving you a hole.

Somebody is not good enough

Say so in week two, not month four. The single most common thing we see is a client who was too polite to complain early and then wanted to end the whole engagement in month three. Replacement inside the first thirty days is free and it is not a negotiation. After that we still replace people, and re-recruitment stays our cost, because keeping somebody in a seat they are wrong for is not a saving.

Be realistic about the cost you carry either way. A replacement is not a like-for-like swap on day one. Expect two to three weeks before the new person is at the level the last one had reached, which is exactly why the procedure cards matter. With cards, that ramp is short and mostly about context. Without them, you are re-teaching from scratch and paying for the privilege twice.

The tools your pod works inside

We do not bring a platform and ask you to move onto it. Your team works in your stack, on your accounts, and when they leave the work stays where it always was. These are the systems our assistants come in already fluent in, so day one is not a training exercise.

Email and calendar

Google Workspace, Microsoft 365, Outlook, Superhuman, Calendly, delegated mailbox access rather than shared passwords

Communication

Slack, Microsoft Teams, Zoom, Google Meet, WhatsApp Business, Loom for recorded handovers

Work and process

Asana, ClickUp, Trello, Monday, Notion, Confluence, and whichever of them already holds your procedure cards

CRM and sales

HubSpot, Pipedrive, Salesforce, Zoho, Close, plus list building and enrichment tools

Support desks

Zendesk, Freshdesk, Front, Intercom, Gorgias, Help Scout

Finance and admin

QuickBooks, Xero, Bill, Expensify, Stripe and PayPal dashboards at read-only where that is enough

E-commerce

Shopify, Amazon Seller Central, WooCommerce, eBay, Etsy, and the marketplace back ends around them

Content and design

Canva, Buffer, Later, Hootsuite, WordPress, Mailchimp, Klaviyo

Security

1Password, Bitwarden, Okta, Google Admin, managed browser profiles, company-issued laptops

An owned pod against the three things you are probably comparing it to

Most people arrive here after trying at least one of the other three. The differences that matter are not about quality of people. They are about who holds the knowledge, who carries the risk, and what happens on a bad week.

  Your own pod in India Hours-based VA subscription Freelance marketplace Local part-time hire
What you buy Named people, exclusive to you A monthly bucket of hours A person, until they get busier elsewhere One employee, one contract
Who holds your process Cards owned by the pod, several people trained The provider, in their system Nobody. It lives in a chat history One person, in their head
Cover when somebody is out Cross-trained teammate steps in Reassigned to whoever is free The work stops The work stops
Ramp-up on a replacement Two to three weeks, cards intact Restart with a stranger Restart from scratch Weeks, plus a hiring cycle
Hours Full or part-time seats, shift of your choosing Capped, with overage rules Whatever they can spare Whatever the contract says
Growing the team Add a seat, per-seat rate steps down Buy another plan at the same rate Find and vet another stranger Another full hiring cycle
Employment risk Ours. We are the employer Theirs Yours, if the classification is wrong Entirely yours
What it looks like on your invoice One monthly figure per seat, itemised A plan price, margin undisclosed An hourly rate plus platform fees Salary plus everything on top of it

Worth knowing what the managed subscription market charges, since it is the option most people weigh against a pod. On published rates retrieved in July 2026: Time etc lists $390 for 10 hours a month, which is $39 an hour. Prialto lists $1,600 a month for 55 hours plus a $250 setup fee on a 90-day minimum. Wishup lists $1,999 and $2,999 a month for its two dedicated tiers. Athena lists $3,000 a month for one full-time executive assistant after a 90-day commitment. Belay publishes nothing at all and routes you to a call.

Those are legitimate products and for a founder who needs eight hours a week of executive support, several of them are a better buy than anything on this page. The model stops fitting when you need several people who know each other’s work, who follow your procedures rather than a provider’s, and who will still be there in eighteen months. That is a different purchase, and it is the one this page is about.

Why India for this work, and where the case gets weaker

India is not the cheapest place to hire an assistant and we would not claim it is. What it has is depth in exactly the kind of work a pod does. The Reserve Bank of India reported software and IT-enabled services exports of $204.7 billion for the 2024-25 financial year, with business process services alone accounting for $55.8 billion of it. The United States took 52.9% of the total. The number worth pausing on is that 90.7% of those exports were delivered off-site, from India, remotely. That is central bank evidence, from a survey of 2,206 companies, that this delivery model works at a scale nobody needs to take on faith.

There is a competitive question underneath the country choice, and it deserves a straight answer. For inbound phone work aimed at American consumers, the Philippines has a genuine advantage on accent neutrality and cultural familiarity, and the Philippine industry body puts roughly seven in ten of its North American orders down to that advantage. India’s strength is the written and back-office side: inbox, documents, systems, data, research, scheduling, reconciliation, the work that arrives as text and leaves as text. That happens to be most of what an assistant pod does. If your requirement is high-volume outbound calling to US consumers, tell us and we will say so.

Two practical risks we plan around rather than deny

Home broadband, not power. The stereotype about Indian electricity is out of date: World Bank enterprise survey data puts a typical month at 1.3 outages, and just 1.9% of firms in India rank power as the single biggest obstacle they face. Connectivity is the real one, and it is specific. On Ookla’s June 2026 index India’s median fixed broadband is 63.25 Mbps, ranked 101st, while its median mobile is 129.78 Mbps, ranked 37th and above the global median. The mitigation falls straight out of the data: every person in a pod runs a mobile failover connection, because in India mobile is the faster link.

Localised internet shutdowns. Access Now recorded 65 internet shutdowns in India during 2025, the lowest count since 2017, affecting 12 states and territories. It is a real risk and we treat it as one, by choosing delivery cities against the shutdown map and by spreading a pod across more than one city once it passes four people. India requires shutdown orders to be published, which makes this the rare risk you can audit in advance.

And the honest limit, again, because it is the one that ends conversations later if it is not said early: if you are on US Pacific time and you want people live on your hours all day, somebody in India is working 21:30 to 06:30 to do it. It works, we staff it, it costs a premium and it narrows who will take the job. If your work can be queued and specified rather than discussed, the same gap turns into an advantage, because work handed over at 5pm Pacific is finished before you open your laptop.

When a virtual assistant team in India is the wrong buy

Nobody else on this search results page will tell you this, so we will. There are five situations where we would rather you did not sign, because the engagement will fail and both of us will have wasted a quarter.

You have less than fifteen hours a week to delegate

A pod is the wrong shape for you. One part-time assistant is the right answer, and possibly an hours-based subscription is better still. Come back when the queue is real.

Nothing is documented and you are not willing to change that

Not the fact that nothing is written down today. Almost nobody has it written down. The problem is being unwilling to spend the first fortnight recording yourself. Without that, you will be answering questions forever and you will conclude we sent you the wrong people.

The work needs a licence or a physical presence

Signing legal or medical advice, anything requiring a locally licensed professional, notarising documents, receiving stock, being in the office when the courier arrives. An assistant in Pune cannot do these, and no amount of process design fixes it.

You manage by seeing people online

Managers whose first move is to glance at who shows as available will find a thirteen-hour offset miserable no matter how good the output is. This model needs you to judge finished work rather than visible presence. That is a genuine change in how you manage, and it is not for everybody.

You want the cheapest possible number

There are providers advertising $5 an hour, and they are not lying. At that rate somebody is being underpaid, undertrained, shared across four clients, or all three. When the lowest number is the only thing being compared, one of those providers will make you happier than we will, right up until the quarter it stops working.

If two or more of those describe you, say so when you talk to us and we will tell you which of them we think is fixable. Turning away work we cannot do well is cheaper for us than doing it badly.

What the first thirty days look like

Every competitor page ends at the words your assistant starts. That is where the difficult part begins, so here is the whole month.

Day 0

The brief

Tasks, hours, tools, time zone, and how many people you think you need. We will argue with the last one if the shape looks wrong, before you spend anything.

Day 2

Shortlist

Profiles in your inbox inside 48 hours, with test results and a recorded English screening call so you can hear each person before you commit to an interview.

Days 3 to 5

Interviews

You meet them on video and you pick. Interviews follow the same question set and the same scoring rubric for every candidate, which is the selection method with the best evidence behind it in the current research.

Day 8 to 10

Start, and access

Accounts created at the permission level agreed, password manager vaults set up, devices issued. Nobody starts before access is designed, because retrofitting it is how mistakes happen.

Days 8 to 20

The documentation sprint

The five-task cycle described above. Five tasks, recorded, carded, run supervised, then run alone. Your lead owns the cards from here.

Day 30

The review

Not a check-in call. A written review of what moved off your plate, what is still bouncing back, and whether the pod is the right size. If somebody is wrong for the seat, this is the meeting where we replace them at no cost.

The wider process, including how vetting works and what happens after the first month, is set out on how it works. If your need is customer-facing rather than administrative, outsourced customer support is the closer fit, and a technical team is covered on hiring a software development team in India.

What buyers ask us before they sign

Two, in most cases, and a lead once you reach three. The honest test is not how many tasks you have. It is how many hours a week you currently spend answering your existing assistant. Under two hours, add a second assistant. Over four, you need a lead more than you need another pair of hands, because the bottleneck is you rather than capacity.

Seats start from $960 a month and your number depends on the mix of levels, the hours, the shift window and the size of the pod. Pricing is one monthly figure per seat, invoiced monthly, and that figure is what pays for sourcing, payroll and compliance filings, the HR function, cover, kit and re-recruiting a seat. Ask Rita for the full rate card and you will get every level priced against the shape you actually want.

Only for you. A full-time seat is 160 hours a month on your work, in your systems, and nobody else buys any part of it. That is the difference between this and an hours-based subscription, where the person handling your request this week may be handling somebody else next week.

Whichever window you pick, and the arithmetic is on this page rather than hidden. A UK client gets a full working day of overlap from a 13:30 to 22:30 India shift. A New York client gets a full day from 18:30 to 03:30 India time, or 3.5 hours from a milder 14:00 to 23:00. On a standard Indian day and a standard US nine to five, the live overlap is zero, which is why the shift window is a decision rather than a detail.

You find out on the day somebody hands in notice, not in the fortnight before their last shift. Recruitment for the backfill starts that day at our cost, the leaver hands over to a named person during their notice period using the written cards, and we cover any gap with an interim from another pod. Indian notice periods run from thirty to ninety days depending on the contract, which gives a longer handover runway than at-will employment does.

You do not send passwords. Mailbox access is delegated rather than shared, every person gets a named account instead of a shared one, and shared credentials live in a password manager vault with the entries hidden from view. Payment authority, super-admin, your domain registrar and the second factor on anything holding customer data stay with you. When somebody leaves, access is revoked within an hour and you get a written access report inside 48 hours.

Indian law criminalises precisely this situation: section 72A of the Information Technology Act 2000 treats a provider leaking material reached through a service contract as an offence rather than a contractual argument. There is a privacy statute behind it too, with Rules operating since November 2025 and security failures penalisable up to ₹250 crore. Cross-border, we sign Standard Contractual Clauses for European data, and for British data either the ICO’s IDTA or those clauses with the UK Addendum, plus a transfer risk assessment.

Yes, and most clients do. Start with one seat, build the procedure cards from day one, and adding the second and third person becomes a week of onboarding rather than a restart. The cards are the thing that makes growth cheap. Without them, every new hire costs you the first month all over again.

Describe the workload. Rita replies with a pod shape and every level priced.

Describe the work, your hours and your time zone. You get a recommended pod shape, every level priced, and a shortlist within 48 hours if you want one. No call to sit through first.