Entering India: the playbook

The headline size of India can make almost any plan look sensible. Your commercial market is smaller: organizations that have the problem, can afford the delivered offer, can buy through a route you can serve, and have a reason to act within your planning period.

Start with named accounts and operating context. A national list is rarely the right first unit. Group accounts by industry, city or cluster, ownership, and buying route. Record which proof should travel, who owns the problem, what technical or regulatory review applies, and how the account normally buys from an unfamiliar foreign supplier.

Then define what you will exclude. An account may be attractive but require a local service footprint you cannot support. A sector may be large but regulated in a way that changes the product. A state may add delivery complexity without improving access. Exclusions protect the first quarter from becoming a tour of unrelated opportunities.

Your reachable market is the account set the team can research, approach through permitted routes, and support properly in the next two quarters. Size that set against the revenue plan. If the number only works when every large Indian company is treated as equally available, the entry case is not ready.

“India first” needs a sharper location decision. The right starting city is not automatically the largest or best known. It is where target accounts, relevant partners, available talent, and delivery requirements overlap.

Map the commercial work. Where are the problem owners? Where do procurement and technical teams sit? Does a partner need to install, support, or distribute locally? Will the first hire need access to a specialist talent pool? The answers may point to one city for sales and another for delivery, which is useful to know before signing premises.

Do not spread a small team across several cities to signal national ambition. Travel can cover discovery while evidence accumulates. Choose one primary cluster, one secondary hypothesis, and a clear condition for expanding. This keeps account research, events, partner work, and founder time concentrated enough to learn.

The city choice also informs the setup brief. Hiring, premises, taxable supplies, and state-specific registrations may follow the actual operating footprint. Legal and tax advisers need the real plan, not “we are entering India.”

There is no single Indian buying culture. A founder-led services company, a large industrial group, and a regulated financial institution will not use the same decision process. Build the purchase map from interviews and live accounts.

Expect the commercial owner, technical reviewer, finance or procurement team, and senior sponsor to value different evidence. Your first contact may support the idea but still need an internal case that survives price comparison and implementation questions. Give that person material they can use without you in the room.

Map authority precisely. Who can agree to a pilot? Who can approve a supplier? Who controls the budget? Who can stop the decision? Titles alone do not answer those questions. Record what happened in each opportunity and update the map weekly.

Relationship matters because risk is carried by people, not because rigor is optional. A warm introduction can open a door, but the value case, delivery plan, and follow-up still have to work. Treat access as the beginning of qualification.

A foreign product is not automatically a premium product. Your prospect may compare it with a local provider, an internal workaround, a global incumbent, or doing nothing. The value case must survive the comparison the account actually makes.

Start with the cost or constraint the account already recognizes. Show how your offer changes it, what adoption requires, and what evidence can be checked. Remove home-market assumptions about labor cost, process maturity, regulation, or willingness to pay. If the result depends on a condition the prospect does not have, say so early.

Separate the core offer from the delivery wrapper. The core may transfer unchanged while implementation, support hours, payment terms, integrations, or training need a local design. This is localization even when the language stays English.

Do not create a stripped-down “India version” before you know what matters. Lower scope can remove the very proof or service that makes the purchase safe. Test the full decision and let repeated objections show what to change.

An Indian subsidiary, branch office, liaison office, and project office do different jobs. A liaison office is a communication channel and cannot undertake commercial activity or earn income in India. Branch and project offices have defined permitted activities and approval conditions. A locally incorporated company is a separate route again.

Company presence is not the only question. A foreign company that establishes a place of business in India has prescribed Registrar of Companies filings. GST follows the taxable-supply facts and can require a non-resident taxable person to register before business begins, with registration connected to the relevant state or union territory. Permanent establishment is a tax-nexus analysis under Indian law and the applicable treaty, not another name for company registration.

Brief advisers with the operating facts. Who will negotiate, sign, deliver, invoice, hire, and work in India? Where will each activity happen? Will goods cross a border, software be accessed remotely, or services be performed on site? The answers determine which questions become live.

Do not select a structure from a generic comparison table. Ask qualified Indian legal and tax advisers to test the actual first-client route, then revisit the answer as the plan changes.

The first pipeline can combine direct access, partner introductions, relevant events, existing client networks, and inbound demand. Choose routes based on the account set rather than habit.

If direct work is part of the plan, define how contact data will be sourced, what channel will be used, and which Indian privacy and telecommunications rules apply to the exact activity. The requirements depend on the data, recipient, message, and channel, so live execution needs qualified review. Do not build a forecast on a contact database before that work is done.

Events are useful when the target accounts and buying roles will be present and the follow-up owner is already named. A large footfall number is not an access plan. Set the account meetings before travel, prepare the proof needed for those meetings, and schedule the follow-up before the team leaves.

Existing clients can help when their Indian operations face the same problem or when they can make a relevant introduction. Ask for a specific connection with a clear reason, not a general announcement that you now serve India.

A distributor can provide contracting, stock, service, or access. A referral partner may only introduce. An implementation partner may influence the decision without owning the commercial relationship. Define the missing job before selecting the label.

Test actual account overlap. Ask for the named industries and roles the partner reaches, the people who will work your offer, and the competing priorities those people carry. Inspect technical capacity and after-sale reporting. A partner with relationships but no follow-up process will create meetings that never become a managed pipeline.

Agree opportunity ownership before launch. Who qualifies the problem? Who prices and proposes? Who invoices? Who handles implementation and renewal? Which information can be shared, and how will consent and confidentiality be managed? Put the answers in the working agreement, not only the legal contract.

Run a bounded test with selected accounts. Review the underlying opportunities every week. If the partner will only provide an aggregate number, you cannot learn enough to plan the market.

The home-market price is only one input. The Indian prospect sees implementation, local taxes, duties where relevant, support, currency, payment terms, and internal adoption effort. Your company sees the cost of partner margin, travel, localization, compliance, and collections.

Build a delivered-price model for each route. A cross-border contract, local distributor, and Indian entity can produce different economics and responsibilities. Qualified advisers should validate the tax and invoicing treatment. The commercial team should validate whether the scope remains understandable and comparable.

Set a price corridor. The floor protects viable delivery. The target reflects the normal scope. Complexity above that is priced through named additions such as sites, integrations, or service levels. Do not discount against vague pressure. Exchange scope, timing, payment, or commitment for the change.

Collection terms are part of entry risk. Define credit approval, milestone evidence, invoice ownership, and escalation before the first proposal. Revenue that cannot be invoiced or collected through the chosen route is not a complete market-entry win.

The first budget buys learning and a working route. Fixed cost should rise only when evidence justifies it.

Include leadership time and travel. If product, finance, and delivery leaders cannot support qualification and proposal work, the entry team will collect questions it cannot answer. That delay should be planned, not discovered.

The first credible client route should clarify more than revenue. It shows who must contract, where delivery happens, which support is expected, what tax and registration questions apply, and which capabilities need to be local.

This does not mean accepting any first deal. A heavily customized project outside the target market can build the wrong operation. Qualify the first-client candidate against the market thesis: does it represent the accounts you want more of, use a repeatable offer, and produce learning relevant to the next ten accounts?

Bring advisers in before commitments harden. Give them the proposed statement of work, people plan, invoicing path, and locations. Ask for the risks and required steps in sequence. A setup memo written against a real route is more useful than a generic catalog of entity types.

When the route changes, update the advice. A remote pilot, local employee, physical delivery, and national rollout do not create the same facts.

In month one, our senior India commercial lead sets the account, city, proof, route, partner, and delivered-price hypotheses. The team behind that lead researches accounts, builds the buying maps, produces the first materials, and briefs qualified advisers against the proposed activities. The client reviews finished work and answers product and delivery questions.

In month two, our team runs the approved access routes, qualifies partners through live work, manages response, and turns objections into revised proof and scope. The weekly review inspects accounts and next actions, not activity totals.

In month three, evidence decides where to concentrate. The team may narrow the cluster, change the value case, increase a working partner route, or stop an assumption. The first live opportunities also provide the facts for a hiring or footprint brief.

The goal is not to declare a national launch. It is to know what job the next investment must do and why.

Define stages with observable exits. A researched account is not engaged. A meeting is not qualified pipeline. Qualification requires a recognized problem, fit, an understood buying route, and a next step accepted by the account.

Review direct and partner opportunities in the same system. Record stage, source, value basis, age, next action, owner, and the assumption being tested. If a partner’s number cannot be traced to accounts and actions, exclude it from coverage.

Watch concentration. A pipeline dominated by one relationship or one unusual project may not prove the wider market. Watch delivery fit too. An opportunity can be commercially active while teaching you to build an operation you do not want.

Every week, decide what the evidence changes. A stage report that produces no change in account choice, proof, route, or next action is administration rather than market learning.

India treated as one territory. A small team spreads travel and partner work across unrelated cities and sectors. Choose a primary cluster and a condition for expanding.

A relationship mistaken for a route. An introducer opens senior doors, but nobody owns qualification and follow-up. Define the operating job and inspect next actions.

Price reduced before value is understood. The team assumes India only buys cheap and removes the support or proof that makes the decision safe. Build the delivered value case first.

Entity selected from a headline. Incorporation, GST, foreign-office permission, and permanent-establishment analysis are collapsed into one choice. Brief qualified advisers with the actual activities.

One local hire asked to do everything. The salesperson researches the market, rewrites the proposition, recruits partners, and carries a target. Give the market a senior owner plus the people who produce the work.

Do not enter yet if the product depends on an assumption that target accounts do not share, if delivery requires local capacity you will not fund, or if the reachable account set cannot support the revenue expectation.

Pause if the only access is one individual’s network and the company cannot observe or repeat the route. Pause if no internal leader can support technical qualification and contracting each week. Pause if legal, tax, or regulatory advice shows that the proposed first deal creates obligations the economics cannot carry.

Another market may offer stronger proof transfer, a simpler first route, or faster learning. India can be strategically important and still be the wrong first international move now.