Customer discovery for an incubator program rarely stops at one city. Allocators who fund permanent capital vehicles need interview designs that force founders to contrast two markets side by side. City pair analysis does exactly that: it treats each conversation as a controlled comparison so capital decisions rest on evidence rather than local cheerleading.
Why Two Cities Beat One Story in Discovery Calls
A single-market founder pitch often sounds airtight until the same product faces a second regulatory climate, talent pool, or buyer habit. Allocators therefore open interviews by naming two concrete hubs and asking the founder to rank friction points between them. This move instantly surfaces whether the team has done more than airport research. When the pair is Tel Aviv and Austin, for example, questions about laboratory space costs or early customer procurement cycles reveal real operating knowledge. The method also protects Foundation cohorts from over-weighting the loudest local anecdote.
Teams that cannot name trade-offs between the chosen cities usually lack the market depth required for later capital deployment. Allocators record those gaps without judgment, then circle back later with sharper probes. The practice keeps discovery light yet rigorous and aligns with the broader guidance found in How It Works.
Building the Pair List Before Any Interview Starts
City selection begins with capital flow data rather than personal travel history. Allocators pull recent startup density figures, patent filing volumes, and cross-border deal counts to shortlist five to seven candidate pairs. A climate hardware team might be tested against Copenhagen-Boston or Singapore-Rotterdam because those pairings highlight supply-chain differences that pure domestic markets hide. Public data sets from the World Bank innovation pages supply baseline innovation metrics that keep the list honest.
Once the shortlist exists, the allocator discards any pair that shares the same legal system or language if the goal is to stress-test localization risk. The remaining pairs receive a one-page brief that the founder receives twenty-four hours before the call. That brief never coaches answers; it simply names the two cities so preparation time is fair. Documentation of this step later helps portfolio committees understand why certain founders advanced.
Interview Scripts That Force Explicit Trade-Off Talk
Generic “tell me about your customers” questions produce rehearsed monologues. Pair-based scripts instead open with a forced ranking: “If you had to launch first in City A versus City B tomorrow, which three constraints flip your decision?” Follow-up probes then drill into hiring velocity, pilot procurement rules, and IP filing routes. When founders mention patents, the allocator can reference the searchable databases maintained by the US Patent and Trademark Office to verify claim breadth without leaving the conversation.
A second block of questions examines capital access differences. Founders are asked how angel density, government matching grants, and bank lending standards diverge between the two cities. Answers that stay abstract get a third round that requires named programs or actual term-sheet anecdotes. This layered design prevents surface-level replies and generates the comparative data allocators need for later stage gates.
Scripts also incorporate a short role-play in which the founder must pitch the same product to a fictional buyer in each city. Observing language shifts, pricing adjustments, and risk disclosures in real time supplies qualitative texture that pure survey methods miss. Foundation interviewers keep the entire exchange under forty-five minutes so fatigue never dilutes signal quality.
Scoring Matrices That Stay Neutral Across Ecosystems
After the call, two independent scorers rate the founder on six dimensions: regulatory literacy, customer access realism, talent acquisition path, capital pathway clarity, IP strategy coherence, and adaptation speed. Each dimension receives a 1, 5 score for City A and again for City B. The absolute scores matter less than the gap size; large unexplained gaps flag either overconfidence or genuine market asymmetry worth deeper diligence.
Scorers must cite at least one verbatim founder statement per dimension. This citation rule blocks impressionistic grading and creates an audit trail useful when permanent capital partners later review the file. Teams that score high on both cities often receive invitations to specialized tracks described in For Builders. Low dual scores trigger a short feedback note rather than silence, preserving founder goodwill.
Calibration sessions occur every ten interviews so individual scorer drift stays minimal. During calibration, anonymized transcripts are re-scored and discrepancies discussed until consensus stabilizes. The process mirrors the transparency standards expected by institutional limited partners who monitor incubator deal flow.
Linking Pair Findings to Sector Maps and Capital Structure
Raw interview notes become useful only after they feed larger mapping exercises. Allocators overlay city-pair insights onto sector universes so climate, health, or infrastructure theses gain geographic texture. A useful companion resource is the Sector Universe Mapping for Climate Startups: Global Market Comparison piece, which shows how multi-city data changes portfolio construction.
Capital structure decisions also shift once pair analysis is complete. Founders who demonstrate clear preference and capability in one of the two cities may receive staged capital that first unlocks the stronger market. Those who handle both markets evenly may qualify for dual-hub support packages. Permanent capital partners value this precision because it reduces the probability of capital stranded in the wrong geography; more on that expectation appears in What Founders Should Expect From a Permanent Capital Partner.
External macro context remains essential. Allocators cross-check interview claims against recent IMF publications on labor mobility and fiscal incentives so that founder optimism about one city is not contradicted by published economic outlooks. The same habit applies when founders claim superior SME support networks; the OECD SME and entrepreneurship materials provide independent benchmarks that keep internal scoring honest.
Common Design Flaws That Distort Pair Results
The most frequent error is pairing cities that are too similar. Comparing San Francisco with Seattle rarely stresses a founder’s ability to navigate unfamiliar regulation or culture. A second flaw is allowing the founder to choose the second city after hearing the first; that sequence invites self-serving selections. Allocators therefore lock both cities before the invitation email leaves the system.
Another distortion arises when interviewers reveal their own preferred city early. Founders quickly mirror the preference, collapsing the comparative value of the exercise. Neutral phrasing and randomized question order reduce that social-desirability bias. Finally, some programs skip the scoring matrix and rely on post-call gut feel; that shortcut reintroduces the very locality bias city pair analysis was designed to eliminate.
Legal and disclosure hygiene also matters. When founders discuss prior fundraising, interviewers confirm that any private placement details stay within the bounds monitored by the US Securities and Exchange Commission. Clean notes protect both the incubator and the founder if later diligence expands to formal securities review.
Turning Insights Into Cohort Placement and Curriculum
Once a wave of interviews closes, the allocator team sorts founders into provisional tracks: dual-city ready, single-city deep, or needs more discovery. Dual-city ready founders enter modules that accelerate simultaneous market entry. Single-city deep founders receive localized legal and go-to-market workshops that still keep the second city visible on the horizon. Placement logic is shared with founders so they understand the reasoning rather than feel sorted by mystery.
Curriculum designers then pull the most frequent knowledge gaps and convert them into short workshops. If three-quarters of founders mis-estimated laboratory permitting timelines between the paired cities, a new session on permitting maps is scheduled. This continuous loop keeps program content fresh and directly tied to observed founder weaknesses rather than generic startup theory.
Cross-border benchmarking techniques developed in scientific founder tracks further refine the curriculum; see the companion discussion in Go To Market Basics for Scientists: Cross-Border Benchmarking Methods. Additional infrastructure and real-estate considerations for Middle East hubs appear in the Israel infrastructure real estate collection, giving builders concrete facility references when city pairs include that region.
All of the above methods, scripts, and scoring tools live inside the broader Business Tech archive so new team members can replicate the process without reinventing it. Consistent application across cohorts compounds learning and raises the overall quality of capital allocation decisions that Foundation supports.
See also Israel infrastructure real estate.
Related Foundation reading: What Is the Application Process Like and Recruiter Networks for Specialized Roles: Technical Deep Dive for Oper.
Timeless Value. Perpetual Legacy.
