Calidad Infotech

    Services · GCC Enablement

    Your capability center.
    Without the guesswork.

    Stand up, scale and optimize a Global Capability Center in India — grown pod by pod, so every hire is backed by work that already ships.

    • Pilot pods
    • Team scaling
    • Governance
    • AI productivity
    • India hub · global clients

    Last reviewed by Calidad Infotech

    Most capability centers fail on distance, not talent. We design yours to share headquarters' context, tools and quality bar from day one.

    Grown pod by pod

    Start with one pod. Grow a center.

    Every new pod joins work that already ships.

    The challenge

    Why this is hard.

    01

    Standing up a GCC from scratch carries real ramp-up risk and cost.

    02

    New teams take too long to learn the domain and become productive.

    03

    Time zones and distance turn every question into a day's delay.

    04

    Quality varies between headquarters and the new center.

    Our approach

    A phased path to scale.

    Each phase earns the next. Headcount follows proven output, never the other way round.

    01

    Seed one pod

    A small senior pod takes a real workstream from headquarters and sets the working norms everyone after it inherits.

    02

    Scale teams and governance

    Add pods with the operating model, reporting and quality standards that keep delivery consistent.

    03

    Optimize with AI

    Embed AI across engineering and quality, with engineers accountable for everything that ships.

    Capabilities

    What we deliver.

    Seed engineering pods

    A senior pod proves the model on real work before you commit to scale.

    Team scaling

    A structured path from a single pod to multiple teams, with managed capacity and SLAs.

    Governance frameworks

    Operating models, reporting and quality standards that hold as you grow.

    AI-augmented delivery

    AI speed across engineering and quality, built right by experienced engineers.

    Built in India, run from anywhere

    Teams in Ahmedabad and Bengaluru, working in step with headquarters in the US, UK, Europe, Singapore or Africa.

    Outcomes

    What changes for you.

    Lower ramp-up risk

    The model is proven on live work before major investment.

    Faster time to value

    The first pod ships while the rest of the center is still being hired.

    One quality bar

    The same rituals and release checks at home and in the center.

    Room to grow

    Scale pods up or down as priorities change. No long-term lock-in.

    The details

    How it works, what it costs, who owns what.

    Definitions

    GCC pod, micro GCC and BOT, in plain words.

    Global Capability Center (GCC): an offshore unit that a company owns and runs to do its own work, such as engineering, data or operations.

    GCC pod: a team of 4–8 engineers in India that works only for one company. It is often the first unit of that company's GCC.

    Micro GCC: a small GCC, usually 15–100 people, with a narrow focus. Also called a nano GCC. Companies often start one through an employer of record (EOR) or a BOT partner, then move it to their own entity.

    Build-operate-transfer (BOT): a partner hires and runs your team, then you take the team over in your own Indian company.

    Each Calidad pod is an AI engineering pod: engineers use AI coding and test tools inside your repos and stay accountable for what ships. See AI agents and automation.

    Who it's for

    Who a GCC pod is for.

    A GCC pod suits companies that want a dedicated development team in India, from one pod of 4–8 engineers up to about 200, and do not yet have an Indian entity.

    • Companies that tried outsourcing and want people who work only on their product
    • Companies planning their own GCC that want to prove the model with one pod first
    • Companies that want the option to own the team later, without committing to it now

    Teams of 50–200 people work the same way: we add pods as you grow, and BOT stays an option.

    If you already run your own center with 200+ people, you probably don't need BOT. We can still add pods to your center.

    How it works

    How a GCC pod works, with an optional build-operate-transfer (BOT).

    You start with one pod, with no Indian entity. You can add a BOT option at any point, which gives you the right to take the team over later.

    1. Build: first engineer in 8–12 weeks

    We agree the pod's scope, roles and hiring bar with you. Most senior engineers in India have 60–90 day notice periods, so a new hire usually starts in 8–12 weeks and a full pod takes about 4 months. To avoid waiting, we can start the pod with Calidad engineers already on our payroll while new hires serve their notice. The pod works in your GitHub or GitLab, your Jira, your SSO and your cloud accounts from day one.

    2. Operate

    The pod takes a real workstream from your headquarters, not test projects. You set the goals and the backlog. Calidad's pod lead manages the team day to day, and Calidad stays the employer for hiring, reviews, pay and exits. This keeps tax and employment lines clear until you take the team over.

    Working hours: pods work shifts that give 4–6 hours of overlap with your team, in US or UK hours.

    3. Take over (optional, when you choose)

    With a BOT option, you can take the team into your own Indian company once it reaches an agreed size or date. Most companies do this at 30–50 people, or 18–36 months in. Below that, the fixed costs of running your own entity are often higher than our management fee. The pod keeps working through the handover.

    Your team

    Who is in the pod, and how we keep it safe.

    • Pod lead: each pod has a lead engineer who writes code and reports to your engineering manager. You interview and approve the lead first.
    • Hiring bar: a coding round, your own system design or take-home round if you want one, and a final interview with you. You can turn down any candidate.
    • Replacements: if someone leaves or doesn't work out, we find a replacement. The contract sets the terms.
    • Security: company-managed laptops with disk encryption, access only through your SSO, removed the same day someone leaves, and background checks on every hire. We fill in your security questionnaire before the contract. Calidad is ISO 9001:2015 certified for quality management.

    Compare

    Staff augmentation vs EOR vs managed pod vs BOT vs captive GCC.

    The ways to build a software team in India differ mainly in who employs the team, who manages it, and when you need your own entity.

    Staff augmentation vs EOR vs managed pod vs BOT vs captive GCC
    FactorStaff augmentationEmployer of record (EOR)Managed podPod with BOT optionCaptive GCC (own entity)
    Who employs the teamVendorEOR providerVendorCalidad, then youYou
    Who manages the teamYouYouVendorCalidad, then youYou
    Time to first engineer2–4 weeks1–2 weeks after you find the person4–8 weeks8–12 weeks for new hires, sooner with existing staff16–24 weeks
    Your India entity neededNoNoNoOnly at takeoverYes, from day one
    You own the team long termNoPartlyNoYes, after takeoverYes
    Upfront cost and riskLowLowLowLow to mediumHigh
    Best forShort-term gapsA few people you hire yourself5–30 people, no plans for an entity10–200 people, entity planned in 1–3 years200+ people, long-term center

    Cost

    What a GCC pod costs.

    Pricing is on request. The cost of a GCC pod in India depends on the number of engineers, their seniority, the city, and whether you add a BOT option. Your quote covers salaries and benefits, seats and equipment, our fee for hiring, HR, payroll, compliance and delivery, and, with a BOT option, the fee for taking the team over.

    You can start with a paid pilot: one pod working on one agreed outcome.

    Invoices to a client outside India are an export of services, so we bill without Indian GST as long as payment comes in foreign currency.

    Transfer

    Taking over the team: what happens at transfer.

    A clean takeover depends on what is set up before the first hire, so we agree the transfer steps, dates and fee in the contract up front.

    • How people move. Your Indian company offers each pod member a job, and people who accept move to you.
    • People. Nobody moves without agreeing. The contract sets out how past service, gratuity, leave and notice periods are handled, and who pays. Provident fund moves with each person's UAN.
    • Your code and IP. Code, tickets, cloud accounts and documents stay in systems you own. Our employment contracts give us the rights to the pod's work, and our contract with you assigns those rights to you, worldwide and for their full term, as the work is created. Our own pre-existing tools are licensed to you, not assigned.
    • Data. For your data, you are the data fiduciary and we act as your processor under a written data processing agreement, including EU standard clauses where GDPR applies.
    • Your entity. Most companies form a private limited company owned by the parent. From tax year 2026-27, India's safe harbour rules accept a 15.5% margin on operating costs for IT services. Some state GCC policies, such as Haryana's 2026 policy, give incentives to your entity after transfer. Check how these apply with your advisors.
    • No-hire. Until transfer, neither side hires the other's staff outside the contract. At transfer, the fee is the only cost of hiring the pod.

    For the entity, director and employee-transfer rules, see Build-Operate-Transfer in India for GCCs. For the setup steps and choosing a city, see How to set up a GCC in India pod by pod.

    We work alongside your lawyers and tax advisors. This page isn't legal or tax advice.

    FAQ

    Frequently asked questions

    What is a GCC pod?

    A GCC pod is a team of 4–8 engineers in India that works only for one company. It is often the first unit of that company's Global Capability Center (GCC).

    What is a micro GCC?

    A micro GCC is a small GCC, usually 15–100 people, with a narrow focus. Companies often start one through an employer of record (EOR) or a BOT partner, then move it to their own entity.

    Do we need an Indian company to start?

    No. Calidad employs the team. You only need your own entity if you take the team over.

    How long until our first engineer starts?

    New hires usually start in 8–12 weeks, because most senior engineers in India have 60–90 day notice periods. We can start sooner with Calidad engineers already on our payroll while new hires serve their notice.

    How much does a GCC pod cost?

    Pricing is on request. It depends on the number of engineers, their seniority, the city, and whether you add a BOT option.

    Can we start with one pod and decide on BOT later?

    Yes. You can start with one pod and add a BOT option later, once you know the team works.

    When should we take the team over?

    Most companies do it at 30–50 people, or 18–36 months in. Below that, running your own entity usually costs more than our management fee. See Build-Operate-Transfer in India for GCCs for how the transfer works.

    Who owns the code and IP?

    You do. Pod members assign their work to Calidad under their employment contracts, and our contract with you assigns it to you as it's created. The code lives in your own repos.

    Can we stop or scale down?

    Yes. You can add or remove pods with the notice set in the contract. If a pod closes, the contract sets out who pays notice-period and exit costs for its members.

    Start with proof

    Skip the pitch.
    See it work.

    A paid pilot: one pod, one outcome, judged on working software — results in days. No long-term contracts.