Five Decades of US-India Operating Experience
Reliable Group is a US-headquartered operating company with teams across India. We combine local operating infrastructure with workflow redesign and governed AI implementation. A US company since 1971, operating in India since 1995and building India operations for clients since 2005.
Who Is Accountable, and For What
Named where we can name someone publicly, and described by function and accountability where the profile has not been released yet. We would rather show you the accountability map than pad this section.
Veeral Lakhani
Chief Executive Officer
Leads Reliable Group and the operating design work behind its engagements. Author of Control Compounds, on operational ownership in the AI era. Reviews the diligence and operating-model work personally, which is why his name is on the case-study methodology notes.
Functional accountability
- Diligence and operating design
- Owns the pre-close read and the operating-model output, and signs the methodology note on any case study that carries a figure. Currently the CEO.
- AI architecture
- Owns the reference architecture for governed AI roles: the context store design, the model and orchestration choices per workflow, and the change-control process that pins role versions.
- GCC operations
- Owns the running of the India centers day to day, including service levels, capacity and the operating cadence with each client function.
- Security and compliance
- Owns the security architecture and data-handling documentation published in the Trust Center, and the per-engagement control design agreed with each client compliance team.
- Talent acquisition
- Owns hiring across the six India cities, the technical bar per role family, and the compensation benchmarks that inform a build plan.
- HR, payroll and statutory compliance
- Owns employment administration, statutory contributions and filings, and the documentation trail for both our own entity and client-owned entities we support.
- Client delivery
- Owns the commitments made in an engagement and is the escalation point when they are at risk. Named per engagement rather than centrally, so the accountable person is someone the client already works with.
The Things You Can Check
This section used to hold a modelled EBITDA range with a disclaimer under it. An About page is where a buyer checks who they are dealing with, so it now holds facts about the company instead.
- Founded
- Incorporated in New York as PJL Systems. 55 years as a continuously operating US company, under the same ownership.
- India operations since
- India operations began in 1995, initially for our own delivery rather than for clients. Client-facing GCC work began in 2005. We state all three dates because they are three different things.
- Headquarters
- Reliable Group (formerly PJL Systems, Inc.) is the contracting entity for US clients. India delivery runs through Reliable Group Paragon LLP.
- India cities
- Vadodara, Pune, Mumbai, Hyderabad, Bengaluru and Noida. City capabilities and role depth are on the Locations page.
- Ownership
- No outside institutional ownership. This matters commercially: there is no fund timeline behind our engagement decisions.
- Clients served
- Cumulative across 55 years of the US business, not a current active count. We do not publish an active client number.
Every fact above was last verified on July 28, 2026. Values that would need a modelled assumption to state are not on this page.
55 Years of Building Operations
A US company since 1971, operating in India since 1995and building India operations for clients since 2005.
A note on the dates
Three anniversaries get conflated in this industry and we would rather separate them. 1971 is the founding of the US company, as PJL Systems in New York. 1995 is when India operations began, initially serving our own delivery rather than clients. 2005 is when we began building India operations for clients. So: 55 years as a US company, 31 years operating in India. Anyone claiming five decades of India GCC experience, including an earlier version of this page, is collapsing those dates.
Technical Depth Is the Substrate
Both levers sit on capability built across decades of regulated, multi-industry operations. The technical bench is not new. The AI-native operating layer is what we built on top of it.
Software and platform engineering
Captive engineering teams, full-stack development, QA and test automation, DevOps, cloud infrastructure and data engineering across six India cities.
Regulated operations
Pharmacovigilance, regulatory affairs, clinical data management, revenue cycle, claims, KYC, AML, trade reconciliation and financial controls, each operating against the relevant control requirements.
AI-native operating layer
Governed AI roles scoped to specific workflows, with durable context inside your data boundary, a compute ceiling agreed before launch, and an audit trail your compliance team can query.
Compliance infrastructure
Working within HIPAA, SOX, 21 CFR Part 11 and GDPR requirements alongside client compliance teams, plus the statutory filings that come with operating across two jurisdictions.
Talent and hiring
Recruiting across six India cities, with the technical bar set per role family and compensation benchmarks maintained by role, level and city from our own hiring.
Entity and operating setup
Incorporation, banking, payroll, facilities, IT and security. The mechanical work that turns a hiring plan into an operation without your team having to become experts in Indian labour law.
From PJL Systems to Two Levers
Reliable Group was founded as PJL Systems in New York in 1971. India operations began in 1995, run for our own delivery for the first decade. In 2005 we began offering that capability to clients, helping American companies set up and own operations in India. We built engineering teams, ran payrolls and hired across regulated functions. That technical depth is still the business. What changed is the operating layer on top of it.
Two things shifted in the 2020s. The work that benefits from technical scale stopped being only software engineering and started including pharmacovigilance, regulatory affairs, financial controls, claims and the long tail of regulated knowledge work. And the operators we work with stopped asking for more headcount and started asking for an operating design that handles more work without it.
We did not pivot from offshore to AI. We absorbed the AI layer into the same operating company that has been running since 1971, and the technical bench that powered that company is what makes the AI layer credible rather than a claim. We are still privately held, still headquartered in New York, United States, with India leadership that has been in place for years. Our job is to work toward your independence, not to make our revenue depend on your continued reliance.
How We Think About This Work
We are operators, not consultants.
Firms will produce a report about what your AI-native org chart could look like. We hand over the chart, the role specifications, the offshore team plan, the unit economics, and an office with employees in it. The distinction matters at exit: a vendor relationship is a dependency a buyer prices into a discount, and an owned operating capability is an asset.
We run on what we recommend.
We run governed AI roles across recruiting, finance, legal, marketing and market-signal detection inside our own business. The compute economics, the governance controls and the context architecture were designed against our own failures first, which is why the published control framework names failure responses rather than just controls.
The people belong to your organization.
Everyone we recruit joins your team and builds knowledge that stays inside your company. The governed AI roles run inside your data boundary. We handle the infrastructure underneath, and the operating knowledge compounds with you rather than with us.
We build for your exit, not our retention.
Engagements are structured so your dependence on us decreases. The COPO model, Company-Owned and Partner-Operated, puts the entity, the team, the data and the AI workflows on your books. A client reaching the point of not needing us is the intended outcome, not a failure of account management.
Where We Operate
Headquartered in New York, operating across Vadodara, Pune, Mumbai, Hyderabad, Bengaluru and Noida.
Which city suits a function depends on role depth at the seniority you need, the competitive set for those roles, time-zone overlap and operating risk, rather than on a generic ranking. The city-by-city view, the comparison and the client-visit process are on the Locations page.
Compare the citiesEntities, Obligations and What We Will Not Claim
Which legal entity holds which obligation, stated here rather than left to be inferred from a contract.
- Contracting and delivery entities
- US clients contract with Reliable Group (formerly PJL Systems, Inc.). India delivery is performed by Reliable Group Paragon LLP. In a COPO or BOT engagement, the client's own Indian entity is the employer of record for the team; we name which entity holds which obligation in the engagement documentation rather than leaving it to be inferred.
- Statutory compliance in India
- India centers operate under local labour and statutory requirements, with the filing and contribution records available for review under NDA. Where a client entity is the employer, those obligations sit with the client and we support rather than assume them.
- Certifications
- We hold no SOC 2, ISO 27001 or CMMC certification, and HIPAA has no certification regime. We publish reviewable security architecture and data-handling documentation in the Trust Center instead of badges.
- Data and IP ownership
- In an owned-entity engagement, the operating data, the process documentation and any IP created by the team belong to the client entity. This is written into the engagement rather than described on a web page.
On compliance claims
We do not publish a compliance-failure record, because a claim of that kind is only meaningful with a defined period, a definition of materiality and an auditor attached, and we have none of the three to offer. What we do provide is the control documentation for a specific engagement, reviewable by your compliance team.
Read the Trust CenterContracting entity: Reliable Group (formerly PJL Systems, Inc.), New York, United States. India delivery entity: Reliable Group Paragon LLP.
What We Run On
Get it done
We measure ourselves by outcomes. Did the role reach production. Was the team hired to spec. Did payroll run accurately. Did the audit pass. Everything else is conversation.
Fire
When a client needs fifteen engineers by Q2 we open the requisition queue that afternoon rather than scheduling a discovery workshop. Urgency is a standing value here, not a response to being behind.
Sharp
The details matter more here than people expect. A payroll error erodes trust. A missed filing creates exposure. A badly structured prompt burns the compute budget. In operations the small things are where problems start.
Humbly confident
We know what we are good at and where our expertise ends. We will tell you which is which, including when something falls outside what we should be doing.
Do the right thing
Especially when it is expensive or inconvenient. This business runs on trust spanning oceans, time zones and now compute boundaries. We do not cut corners on compliance, bury problems in monthly reports, or tell clients what they want to hear.
Ready to Talk?
Both levers, scoped together. Three to five weeks.
The Blueprint produces the org chart, the governed AI roles, the offshore team plan inside your entity and the joint unit economics. It is a paid engagement and the deliverable stands on its own.