Design a soft-landing week for international startups visiting a new market (worked example: UAE)

A soft-landing week should test market assumptions, not imitate a trade mission. This worked example uses the UAE as a planning context and combines orientation, customer discovery, ecosystem conversations, compliance signposting and a final go/no-go decision without promising incorporation, visas or sales.

### Use this when Use this when a startup is considering a new market and needs structured learning before committing significant time or money. The week is for testing assumptions about customer need, routes to market, local support and operating requirements. It is not a substitute for legal, tax, immigration or regulatory advice. For UAE planning, the federal government portal says free zones can provide services such as company set-up and licensing, visas and immigration support, premises, and ongoing administrative support, with services varying by zone and sector. [1] That is useful orientation, not a guarantee that a particular startup qualifies or that one free zone is right. Verify current requirements with the relevant official authority. ### The outcome The team leaves with a documented market hypothesis, a set of evidence-backed customer and partner conversations, a list of unanswered regulatory or operational questions, and a decision: continue research, run a defined pilot, appoint local advisers, or pause. The week does not need to produce a sale to be useful. ### Before you start **Inputs:** product and customer brief, target use case, current market assumptions, questions for customers, company documents requested by advisers, travel and accessibility requirements, and a budget owner. Define what would count as evidence for each assumption. **People:** startup team, local programme host, customer-discovery lead, ecosystem lead, and qualified legal, tax or licensing advisers where relevant. Ask hosts to introduce possibilities, not guarantee access. **Time:** plan at least two preparation calls, one week of visits, daily debriefs and a final decision session. Keep customer meetings protected from ceremonial activity. ### Step by step 1. **Write the visit hypothesis.** Complete: “We believe [customer/use case] in [market context] has [problem], and we could test it through [route].” List five assumptions about customer, buyer, regulation, distribution and support. 2. **Set evidence rules.** For each assumption, define what you need: a customer interview, a qualified adviser’s view, an official page, a partner conversation or a product test. A general introduction is not evidence of demand. 3. **Prepare a market-safe brief.** Explain what the product does, who it is for, what you are not claiming, and what questions you want answered. Remove confidential data that is unnecessary for an initial conversation. 4. **Day one—orientation and boundaries.** Cover geography, business culture as relevant to the team, meeting logistics, public and private information, and the difference between an exploratory conversation and formal advice. For UAE-specific licensing, immigration or tax questions, create a referral list to current official sources and qualified advisers. 5. **Day two—customer discovery.** Run short, consistent interviews. Ask about current behaviour, buying authority, procurement route, timing and constraints. Do not pitch through every question. Record the customer’s words separately from the team’s interpretation. 6. **Day three—ecosystem and route-to-market conversations.** Meet potential programme, channel, corporate, research or public-sector contacts. Ask what a credible first step looks like, what evidence they require and who else should be consulted. Do not call an organisation a partner until it has agreed a role. 7. **Day four—operating options.** Compare routes such as remote testing, a local pilot, a distributor or a licensed presence. Use the UAE government portal as an orientation source for the types of services free zones may provide, then verify the relevant zone and sector requirements directly. [1] 8. **Day five—decision workshop.** Review each assumption as supported, weakened or unanswered. Choose one of four decisions: continue discovery, design a pilot, seek specialist advice before deciding, or pause. Assign owner, date and evidence needed for every open item. 9. **Send a responsible follow-up.** Thank contributors, correct factual misunderstandings, and state only the next steps actually agreed. Do not imply that a meeting created market access or a government relationship. 10. **Store learning for the next team.** Keep a dated visit brief, anonymised learning notes, official links, adviser questions and decision record. Separate confidential information and personal data from the reusable programme learning. ### Templates **Soft-landing week grid** | Day | Purpose | Conversations | Evidence to capture | Owner | |---|---|---|---|---| | 1 | Orient and set boundaries | Host, adviser referrals | Questions and constraints | Programme lead | | 2 | Test customer problem | Prospective users/buyers | Current behaviour and buying route | Discovery lead | | 3 | Test ecosystem route | Channels, programmes, corporates | Credible first step | Ecosystem lead | | 4 | Test operating options | Qualified advisers, relevant authorities | Requirements to verify | Operations lead | | 5 | Decide | Team and host | Supported/weakened/open assumptions | Founder | **Conversation opener:** “We are here to test whether [specific use case] merits a next step. We are not asking you to endorse the product or promise access. Could we ask about your current process, constraints and what evidence you would need?” ### Common mistakes Do not schedule a week of speeches and call it soft landing. Do not treat a government or free-zone webpage as personalised advice. Do not promise visas, licensing, customers or investment. Do not ask one person to interpret every local rule. Do not let hospitality displace customer discovery. Do not record personal or commercially sensitive information without a clear reason and consent. ### How to tell it worked Every original assumption has a status and evidence note. The team can explain what it learned from customers rather than only from hosts. Regulatory and operating questions have named sources for verification. The final decision has an owner and date. The visit produced a smaller, clearer next step—or a justified pause. ### Using LINKK for this Use LINKK’s Partner directory to identify relevant ecosystem organisations before the visit, then check whether profiles are claimed or verified. Post a clearly scoped Need for market-entry or programme support rather than asking for generic introductions. Use accepted introduction requests for private follow-up and keep public Event or Resource posts factual. ### Sources [1]: https://u.ae/en/information-and-services/business/Doing-business/doing-business-in-free-zones/accessing-services-for-free-zone-companies "UAE Government: Accessing Services for Free Zone Companies" ---