MENTARA
Book a call
Company

Location-flexible, not offices everywhere.

What global delivery means for a firm registered in Hyderabad in July 2026: remote by default, on site where the work needs it, jurisdiction settled up front.

Discuss delivery locations Read the detail

More in Company

What the term usually means

In this industry, global delivery normally describes a specific machine: delivery centres in several countries, a follow-the-sun rotation, and a cost model built on moving work to wherever it is cheapest to perform. It is a genuine capability, and at sufficient scale it works well.

MENTARA does not have that, and will not describe itself as though it does. We are registered in Hyderabad, we hold no overseas offices or operating entities, and the model is location-flexible rather than location-distributed — the work is structured around where it actually has to happen, and that is agreed with you rather than assumed.

What follows is what that means in practice: the questions settled before mobilisation, and the constraints the model genuinely carries.

The position

What is true about where we work.

MENTARA GLOBAL TECHNOLOGIES PRIVATE LIMITED is registered in Hyderabad, India, and was incorporated on 15 July 2026. It has one operating base. There are no offices, subsidiaries or employing entities in any other market, which is why this site carries no map of locations.

The markets we are built to serve are India, the United States, the United Kingdom and Europe, and the Middle East and wider Asia-Pacific. That is a statement of the scope we work in, not a claim about where we already have clients — we have none to point to yet.

Engagements are structured remotely by default, with on-site presence where the work genuinely requires it: workshops, discovery across distributed stakeholders, operational transition, or environments that cannot be reached remotely for good reasons. On-site time is proposed because the work needs it and priced accordingly, rather than assumed as a standing billing line.

Where an engagement requires a local employing entity, local invoicing, or personnel holding a specific right to work, that is a real constraint and we will say so during scoping rather than discover it at contract. In some of those cases the honest answer is that a firm with an entity in your market is the more sensible route — either instead of us, or alongside us.

The model

Six things distributed work has to get right.

Distance removes the ambient coordination that being in one room provides. These replace it deliberately, rather than hoping it re-forms on its own.

01Client-aligned ownershipOne accountable lead, one decision route, and a stakeholder cadence agreed at mobilisation. Distance makes ambiguity about who decides considerably more expensive than it is in a shared office, so it is settled first rather than allowed to emerge.
02Time zones as a design constraintOverlap hours are agreed rather than assumed, and the work is arranged so decisions needing people in two places happen inside that overlap. What falls outside it is made asynchronous by design rather than by accident.
03Secure accessAccess, devices, environments and information handling agreed to your requirements before anyone starts — working inside your identity provider and access regime, rather than asking for credentials to be handed across a boundary.
04Location and legal reviewJurisdiction, contracting, employment, tax and data-residency questions reviewed before mobilisation, with qualified advice taken where the answer is not obvious to us.
05Knowledge continuityDocumentation, pairing and written decision records arranged so the engagement does not depend on one person being reachable across a time difference at the moment they are needed.
06Team shape chosen for the workOn site, remote or blended, selected because the work calls for it. A default of full-time on-site presence bills well and is frequently unnecessary; a default of fully remote is occasionally wrong, and we would rather say which applies.
Before mobilisation

Five things settled before anyone is granted access.

Agreed during scoping and recorded in the engagement. Leaving any of them to be resolved later is how distributed delivery produces its worst surprises.

  1. 01 Where the work is performed

    The locations from which each part of the engagement will be delivered, named rather than left flexible, including any on-site requirement and the purpose it serves.

    • Confirm delivery locations for each workstream
    • Agree the purpose and frequency of any on-site presence
    • Record what changes if a location has to change

  2. 02 Where the data sits and who may reach it

    Which data the work touches, which jurisdictions it may be processed in, whether any transfer outside them is required, and on what legal basis.

    • Classify the data the work will actually touch
    • Confirm residency and transfer requirements
    • Name the individuals who will hold access

  3. 03 Which law and which contracting entity

    Governing law, contracting entity, invoicing arrangement, and any local requirement your procurement or tax position imposes.

    • Confirm contracting entity and governing law
    • Identify local invoicing or entity requirements early
    • Take qualified advice rather than assuming equivalence

  4. 04 How the team is reached

    Working hours, agreed overlap, response expectations, the escalation path outside those hours, and what is explicitly not covered.

    • Agree overlap hours and response expectations
    • Define the escalation route outside working hours
    • State what is not covered rather than leaving it implied

  5. 05 What happens at the end

    Transition, data return and deletion, and documentation handover — defined at mobilisation rather than negotiated at the point the relationship is ending.

    • Define transition and handover before work starts
    • Agree data return and deletion with written confirmation
    • Keep the decision record current so handover means something
Honest limits

What this model does well, and what it does not do.

The trade-offs are real in both directions. A supplier who describes only the first column is describing a brochure.

What the model does well

Where location flexibility is an advantage rather than a compromise.

  • Senior people are available to the work directly, with no delivery-centre layer between them and it.
  • Cost is not carrying offices in markets where the work requires no physical presence.
  • Written decision records and asynchronous working are enforced by necessity, which makes the engagement more legible than a co-located one usually is.
  • Team shape can change without a location change, because it was never tied to a building.
  • On-site time is a deliberate cost with a stated purpose rather than a standing assumption.

What it does not do

Stated plainly, because an evasive answer here wastes your evaluation time and ours.

  • No follow-the-sun coverage. We are not in enough time zones to hand work around the clock, and will not describe a rotation we cannot staff.
  • No overseas offices or employing entities. Where local presence or local employment is a requirement, that is a genuine constraint.
  • No two-hundred-person mobilisation at short notice. Scale of that kind is the leverage model's real advantage, and it is not ours.
  • No permanent on-site team as a default. Sustained daily presence in a distant market is something we would need to solve deliberately rather than assume.
  • No claim of in-country data residency beyond what the engagement's actual arrangements support, which is agreed rather than asserted.
Common questions

What buyers usually need to establish.

Can you work in our time zone?

Partly, and the honest answer depends on how much overlap the work needs. A substantial overlap with the United Kingdom, Europe or the Middle East is comfortable from India; with the United States it narrows, and with the west coast it becomes a short window that has to be used deliberately rather than assumed.

What we will not do is claim full working-hours alignment and then staff it by asking people to work permanently through the night. That arrangement degrades within a few months, and the client absorbs the result.

Do you have an entity in our country?

No. MENTARA is a single Indian company with no overseas subsidiaries. Contracting is with the Indian entity unless we agree an alternative arrangement that suits your procurement and tax position.

Where a local entity is a hard requirement, raise it immediately. It may be resolvable through a local prime or partner arrangement, and it may not be — either way it is a first-conversation question rather than a late one.

Can our data stay in our country?

That depends on what the engagement requires and how your environments are arranged, so it is settled during scoping rather than promised here. In many cases the work can be performed entirely within your environment, under your access controls, with no client data leaving it.

Where that is not possible, the transfer, its legal basis and the controls around it are agreed and written into the engagement. We will not accept regulated data on the strength of a general assurance.

Can you put people on site?

Yes, for defined purposes and periods — discovery, workshops, operational transition, or work that genuinely cannot be done remotely. That is proposed with its purpose and its cost stated rather than folded into a rate.

Sustained full-time on-site presence in a distant market is a different proposition, and depends on visas, duration and cost. We would rather work through that specifically than answer yes in a way that becomes heavily qualified later.

How does this differ from an offshore development centre?

An offshore centre is generally sold on cost per hour and staffed through a pyramid, with the client owning coordination between the centre and their own teams. That model is efficient at volume and works well when the specification is stable.

Ours is a smaller, senior-weighted team accountable for an outcome rather than for hours — which costs more per person and considerably less in coordination. Where your requirement genuinely is a large volume of well-specified work at the lowest hourly cost, an offshore centre is the better answer, and we will say so.

07

Where this model fits.

Scope

It works well where the constraint is senior judgement rather than volume, where the work can be performed inside your environment under your controls, and where a defined amount of on-site time solves the collaboration problem that a permanent local team would otherwise solve.

Where a programme needs sustained on-site presence in a market we have no entity in, a large mobilisation at short notice, or genuine round-the-clock coverage, a firm with local presence is better placed. Establishing that early costs you nothing.

See how engagements are structured

Tell us where the work actually has to happen.

Share the business context, constraints and expected outcome. MENTARA will identify the relevant accountable route.

Submit your requirement

One partner. One plan. Measurable outcomes.