Choose the Right Ownership Path for Your India GCC
FLEXI, COPO and BOT solve different starting conditions. Compare who owns the entity, employs the team, controls the data, funds the setup and carries operating responsibility.
Three ownership paths. One operating model underneath.
Every team we build runs Virtual Employees alongside the human operators from day one. The difference between Flexi, COPO, and BOT is who owns the entity. The operating model, AI-native, governed, with persistent memory and auditable outputs, is constant.
Trace stays on as the measurement layer, so improvement is demonstrated, not asserted.
Trusted by industry leaders
Three Paths to the Same Destination
Every model is designed to preserve client control and optionality. Choose the ownership structure that matches your risk appetite, timeline, and ambition.
Five Questions. One Model.
The first two questions resolve most situations. The remaining three are the ones that change the answer when a transaction, a regulator or a balance-sheet constraint is involved.
Does your board or legal team require the India entity in your company's name from day one?
COPO is your model
Your entity from day one. We operate underneath.
Continue to question 2 below.
Do you need to prove the model internally before committing to a full build?
FLEXI is your starting point
Start with 5 to 10 people. Upgrade when ready.
BOT gets you there fastest
90 days to operational. Full transfer in 24 to 36 months.
Start FLEXI, convert to COPO
Prove the model first, then register your entity with confidence.
Who should carry the setup and early operating risk?
This is the real difference between COPO and BOT, and it is a balance-sheet question as much as an operating one.
Is there a transaction, exit or refinancing in the next 24 to 36 months?
A transfer negotiated under diligence pressure is expensive. If a deal is in view, the transfer terms belong in the agreement on day one.
How constrained is the data? Residency, regulator or client contract.
Where the constraint is hard, the entity boundary is the control that satisfies it, and that points to ownership from the start.
What is true across all three models, and what depends on advice
The comparison above covers structure. These are the dimensions that decide whether a structure actually works for your situation.
- IP and work product
- Yours under all three models, assigned to your company rather than licensed to you. The difference is which entity employs the people producing it during the engagement.
- AI workflow ownership
- Virtual Employee specifications, prompt and policy libraries, evaluation sets and accumulated institutional memory belong to you in all three models. Under COPO they sit inside your entity from day one; under BOT and FLEXI they are specified to transfer with the team.
- Data residency
- India-resident by default, in your systems where you own the entity. Where a regulator, a client contract or a residency rule constrains this, the constraint is designed for before hiring starts rather than reconciled afterward.
- Tax and permanent establishment
- How an India operation is treated for tax, and whether it creates a permanent establishment for your parent, depends on structure, activity and treaty position. This is a question for your tax adviser on every model, and the answer can differ between COPO and BOT.
- Employee transfer
- On conversion or transfer, employment moves with continuity of service, benefits and seniority preserved. The mechanics are jurisdiction specific and are documented in the agreement before the first hire, not at handover.
- Sector restrictions
- Foreign ownership is open for most services activity and carries conditions or approval requirements in some sectors. Applicability is confirmed with counsel during the Blueprint rather than assumed.
Entity structure, foreign investment treatment, tax residency, permanent establishment and employee-transfer mechanics are jurisdiction and sector specific. Nothing here is legal or tax advice. Reliable Group works alongside your counsel and tax advisers, who own those opinions.
FLEXI vs. COPO vs. BOT
A detailed comparison to help you choose the model that matches your situation.
| FLEXI | COPO | BOT | |
|---|---|---|---|
| Best For | Companies exploring India for the first time who want to prove the model with a small team. | Companies whose governance or IP requirements mean the entity needs to be in their name from the start. | Companies that want a functioning GCC without managing the setup themselves. |
| Entity Ownership | Not required. Use Reliable's infrastructure. | Yours from day one. | Reliable initially; transfers to you at a predetermined point. |
| Virtual Employees from Day 1 | Yes. Operator-led design within our infrastructure. | Yes. Designed inside your entity. Full IP ownership. | Yes. Designed inside our entity. Transfers to you with the team. |
| Who Runs Operations | You select which operational services Reliable handles. | Reliable, under a services agreement. | Reliable, until the transfer date. |
| Team Hiring | Reliable recruits on your behalf. Employment can sit under either entity. | Reliable recruits; employees are hired under your entity. | Reliable hires under its entity, then transfers employment contracts. |
| Typical Timeline | 30-60 days for initial services. | 90 days to operational. | 90 days to operational. |
| Transfer/Exit | Upgrade to COPO or BOT when ready. | No transfer needed. The entity is already yours. | Full transfer after 24-36 months. |
| Starting Investment | Lowest. No entity costs. Monthly per-seat pricing. Start with as few as 5 people. | Moderate. You fund entity registration, office setup, and initial hiring directly. Reliable charges a per-seat operational fee. | Highest upfront (entity setup + infrastructure + team build included in the engagement). Lowest execution risk because Reliable carries the operational burden until transfer. |
What We Run Underneath
Every model uses the same operational backbone. Six services that take an India operation from incorporation to mature, running 24/7. You direct the team. We handle the building.
GCC Setup & Entity Registration
Incorporate your Indian subsidiary in weeks. MCA filings, DIN, DSC, PAN, TAN, GST, and bank accounts done before the first hire walks in.
Learn moreTalent Acquisition
Recruiting across six India cities. Sourcing, screening, technical interviews, offer management, calibrated against your bar.
Learn moreHR, Payroll & Compliance
India labor law handled monthly. PF, gratuity, professional tax, POSH, Shops & Establishments, every state-level filing your team should never have to learn.
Learn moreWorkspace & IT Infrastructure
Move-in ready offices in six cities. Redundant internet, biometric security, enterprise IT, full facilities management.
Learn moreScale & Transform
Grow beyond the first 20 people. Process automation, India-based leadership, retention programs, Virtual Employees for workflow optimization.
Learn moreGCC Operating Advisory
Fix the existing India center. Move from Level 2 to Level 4 on the Maturity Index without rip-and-replace.
Learn moreWhere AI Inside the Entity Quietly Breaks
Whichever model you pick, the Lever 1 layer running on top has the same three failure modes. We have scars on each. We built our patterns against our own operations before we shipped them to clients.
Token costs
Compute bills double on the wrong prompt structure. Every Virtual Employee runs inside a unit-economics model we built against our own operations. You see the bill before it surprises you.
Governance
Who approves what the Virtual Employee does. Who audits the trail.
Who answers when it gets something wrong in a regulated workflow. Designed inside our own operations before we shipped to clients.
Persistent memory
A Virtual Employee that holds your business context across months of work is a system. One that starts from zero every morning is a chatbot.
Getting memory right is where most AI efforts quietly break. We run ours on a memory architecture we use ourselves.
Frequently Asked Questions
Under the FLEXI model, your team can be operational in 30-60 days using Reliable Group's existing infrastructure. Under BOT, a fully operational center with your own entity is typically ready in 90 days. COPO provides entity ownership from day one with operational support from Reliable Group.
In a BOT (Build-Operate-Transfer) model, Reliable Group builds and operates the center, then transfers full ownership to you at an agreed point. In a COPO (Company-Owned, Partner-Operated) model, you own the Indian entity and employees from day one, and Reliable Group operates the infrastructure underneath. BOT is better for companies that want zero upfront setup risk. COPO is better for companies that want immediate ownership and control.
Under FLEXI, you can start with as few as 5 people. There is no minimum for BOT or COPO, but most clients start with 10-25 people in the first phase and scale from there based on results.
Yes, and the conversion path is written into the agreement before you start rather than negotiated later. We build a FLEXI team as if it is going to become your GCC from day one, so converting to COPO or BOT is a structural change rather than a rebuild. Timing depends on when you have the evidence you need.
You do. In all three models, the work product, code, data, processes, and institutional knowledge belong to your organization. Reliable Group never claims ownership of client IP.
Not Sure Which Model Fits? Start with the Blueprint.
Three to five weeks. Both levers scoped together. The Blueprint produces the entity structure recommendation alongside the AI-native org chart, the Virtual Employee roster, and the joint unit economics.