Deep tech innovation is often stalled by an execution gap. While many founders excel at pivoting — the art of shifting narratives to secure the next check — few are prepared for the operational reality of scaling within complex city systems.
To move from a prototype to a multi-city deployment, a deep tech founder must transition from a “tourist” mindset to that of a systems architect. Many deep tech startup teams disappear in pilot purgatory: they lack many green flags you as an ecosystem builder could pay attention to. The following is for you if you are tired of “exploratory meetings” that lead to nowhere.
Here are some Mid-Execution Founder Questionnaire tips..
for the scale-up ecosystem enablers and deep tech venture studios among our readers to filter out founders who view cities as mere markets.
Find those folks who understand the world’s fastest growing cities as integrated infrastructures. By shifting the focus from basic demographics to deployment bottlenecks and ecosystem dependencies, we can identify the mid-execution deep tech founders ready for high-stakes partnerships.
You want to ask questions that a “pivoter” founder cannot answer without exposing their lack of traction.
The “Execution-Only” Questionnaire
1. What stops their deep tech pilot from going multi-city
Question: “Identify the single non-technical barrier (regulatory, structural, or ecosystem-based) that is currently preventing your pilot from scaling to a multi-city deployment.”
The Logic: A founder “mid-pivot” will talk about product-market fit or user feedback. A founder “mid-execution” will talk about specific grid-interconnectivity standards, municipal procurement cycles, or supply chain friction.
- Green Flag: Mention of specific anchor entities or systemic blockers.
- Red Flag: Vague answers like “we need more marketing” or “fundraising.”
Ideally, your questionnaire shouldn’t just ask “What is the barrier?” it should also ask “Who specifically at [Utility X] told you ‘no,’ and what was their exact reasoning?” Filter for relational data, not just technical jargon.
2. Look for founders who have mapped the budget cycle of the cities they target
Question: “In your current or upcoming pilot, what is the specific, contractually-defined KPI that triggers an automatic transition to a commercial roll-out?”
The Logic: This tests for High-Integrity Partnership Design. If they don’t have a trigger, they are in “Pilot Purgatory” and could use your help — but they must at least recognize that the lack of a trigger is a problem.
- Green Flag: “We have a Letter of Intent contingent on [X] metric.”
- Red Flag: “We’re just trying to get our foot in the door and see what happens.”
NOTE
In deep tech — especially with municipal stakeholders — contracts are often intentionally vague, to protect political interests. A founder demanding a “hard trigger” might actually be less experienced in the nuance of government relations than one who understands that commercial rollout is often a series of soft hand-offs rather than a binary switch. Alternative: Look for founders who have mapped the budget cycle of the cities they target, not just a KPI of their pilot.
3. Ecosystem Dependency Mapping: a partnership of labor versus a partnership of power
Question: “List three ‘Collaboration-Ready’ stakeholders (beyond the end-user) whose infrastructure your technology must integrate with to function at scale.”
The Logic: Deep tech doesn’t exist in a vacuum. If they haven’t mapped the ecosystem dependencies (e.g., the utility provider, the data regulator, the hardware OEM), they aren’t ready for a Strategic Co-Pilot; they still need a basic business consultant.
- Green Flag: Identification of specific archetypes (e.g., “Tier 2 Telecom Providers in Southeast Asia”).
- Red Flag: “Anyone who wants to innovate.”
By positioning yourself as a “Co-Pilot,” you risk attracting “High-Execution” founders who are actually burnt out. A true “mid-execution” shark often doesn’t want someone in the cockpit; they want someone to clear the runway.
Consider if your value-add is “Shared Control” (Co-Pilot) or “Systemic Clearance” (The Tower). One implies a partnership of labor; the other implies a partnership of power.
4. The “Judgment” Requirement
Question: “Describe a recent ‘Pivot vs. Persevere’ decision where you chose technical integrity over a faster path to revenue. Why?”
The Logic: This tests if they value taste and judgment. You want to be looking for founders who realize that “scaling the right way” is different from “scaling fast.”
- Green Flag: Sacrificing a short-term lead to maintain long-term architectural standards.
- Red Flag: Any answer that implies they take every check offered to them.
Yet.. is judgment really about picking integrity, or is it about knowing when to ship “good enough” to survive? A founder who never compromises might be a visionary –but those are rarely scalers. You may want to filter for practical compromise — the ability to identify which “technical debts” are worth taking on to hit a commercial milestone.
Comparison: Who You Are Actually Filtering
The Pivoter/Tourist | The Mid-Execution Founder |
Focuses on Features and Vision. | Focuses on Infrastructure and Integration. |
Views cities as “Markets.” | |
Needs “Advice” to feel better. | Needs “Judgment” to move faster. |
Seeks a Consultant to do the work. | Seeks a Co-Pilot to share the cockpit. Or someone to clear the runway, in the case of mid-execution sharks.. |
Move From Discovery to Diagnosis
Many deep tech ventures die in pilot purgatory: they lack many elements that you want to look for as an innovation ecosystem enablers in your city. If you are tired of “exploratory meetings” that lead to nowhere, it is time for a Diagnostic Stress-Test.
At 5,000 Cities, we don’t offer general business consulting.
