First, Foundations

Cyber-Physical Infrastructure

Why Detroit? Why the Global South? Why Not One Market?

I just landed in Kenya.

I have a 7 hour layover, because there is only one KQ flight that goes to Malawi today. Luckily, the Turkish Airlines Lounge has a shower [shout out, Turkish!] and I was able to freshen up before my next flight to Lilongwe.

I cannot help myself: I am always obsessive about the details. Before I have even fully settled into being here, I can feel how cyber-physical thinking changes the way one looks at a place.

As we were landing, I found myself looking down not just at the beauty of the landscape, but at continuity. I was looking for light. I was looking for the dark patches. I was tracing where electricity seemed to reach and where it appeared to thin out. Since arriving, I have been noticing the fragmentation of internet connectivity too. You feel it very quickly when you move through a place. Some parts flow. Some parts pause. Some parts carry the assumptions of a connected world. Some parts remind you, immediately, that continuity is still uneven.

This is where my mind goes now.

I do not arrive somewhere and only see a city. It’s a curse by now. I see systems. I see reach. I see coverage. I see interruption. I see what kind of environment a future can or cannot comfortably sit on.

That is the thing about building at the layer of cyber-physical infrastructure. It changes your way of seeing.

CPI Revelations

I think it is important to be clear about my posture here.

I am not writing this as a policymaker. I am not writing this as someone claiming responsibility for fixing every foundational failure beneath the systems I want to build. I am not taking on electricity generation, national fiber rollout, or internet affordability as my work.

I am writing as a builder at the layer of cyber-physical infrastructure.

And from that layer, one learns very quickly that advanced systems are revealing. They expose the environment they sit in. The more the system depends on continuity, sensing, feedback loops, physical response, data flow, and coordination across space, the more honestly the environment presents itself.

Cyber-physical infrastructure is revealing in that way.

It shows you where the system holds.
It shows you where it thins out.
It shows you where the environment is ready for continuity.
It shows you where continuity still has to be fought for.

That is where I find myself intellectually right now. I am not jumping ahead. I am holding a mirror to the system through the demands of what I am trying to build.

Africa’s Digital Entrepreneurial Opportunity

Part of why this reflection feels so important to me is because it is not new thinking. It is deeper thinking.

In my research on Malawi’s digital transformation, I was looking at what shapes the creation and adoption of information management systems.

What that work made clear was that digital systems do not emerge simply because people want them to. They are shaped by conditions. Technological conditions. Organizational conditions. Environmental conditions. Individual ability and readiness. These things matter materially. They shape what gets built, what gets adopted, and what gets sustained.

The_Entrepreneurial_Opportunity_in_Malawis_Digita Download

My study found that perceived benefits, innovation, cost, external support, and competitor pressure all played important roles in determining whether systems get created, while perceived benefits were especially important for adoption. That mattered to me then because it showed, quite plainly, that ambition alone is never enough. Ecosystems matter. Infrastructure matters. Support matters. Readiness matters. Environment matters.

So when I think now about cyber-physical infrastructure, I do not feel like I am changing my mind. I feel like I am extending my mind.

If even relatively basic digital systems depend on readiness, environment, support, and structural conditions, then cyber-physical systems depend on them more intensely still. They sit higher up the stack. They make heavier demands on the environment. They ask more of continuity. They ask more of the physical world. They ask more of the institutions and infrastructures that sit underneath them.

So yes, I have read my own research into this moment. It belongs here.

The Question Cyber-Physical Infrastructure Forces

The question I keep returning to is a simple one.

What has to be true for cyber-physical infrastructure to exist meaningfully?

I mean for CPI to exist in earnest.

Building in Africa is hardwork mehn.

Obstacle too much.
— SB (@seyedele) April 14, 2026

For cyber-physical systems to function well, somethings underneath have to hold:

Power has to hold with enough consistency to sustain sensing, actuation, and computation.
Connectivity has to hold with enough consistency for systems to exchange information across space and time.
Physical environments have to be structured enough to be mapped, modeled, and acted on.
Data infrastructures have to be there. Operational continuity has to be there.

I am not saying every condition needs to be perfect before one begins. If that were true, no one would build anything.

I am saying the more advanced the system, the less romantic one can afford to be about the foundations.

At some point, the system itself starts asking difficult questions of the place you are building in.

The Foundations Are a Continental Question

This is not a hidden issue. It is not as though the continent is unaware of the foundational question.

When I think about initiatives like Mission 300, and when I think about long-standing projects such as Inga III, I see ambition at the level of foundations. I see effort to address power at scale. I see recognition that the question of infrastructure is not peripheral. It is central.

That matters to me, because I do not want this article mistaken for the [lazy] observation that Africa needs infrastructure. Of course it does. This is not news. The continent has not been asleep at the wheel on this. Governments, development finance institutions, investors, utilities, and regional bodies have been wrestling with these questions for years. The scale of the problem is simply that large. The complexity is that real.

Mission 300 reflects an understanding that electricity access is foundational to everything else we keep saying we want. Inga III, whether one looks at it through the lens of promise, delay, or continental ambition, reflects the same truth. Power has always sat beneath the dream.

What I am adding to that conversation is not a policy program. I am adding the view from a builder higher up the stack.

Because from where I sit, one feels these foundational gaps in real time. One encounters their consequences while trying to build systems that depend on continuity. The system tells you, immediately, what kind of environment it is sitting in.

Building in the West vs Building for the World

There is a difference between building in the West and building for the world. I have become increasingly aware of that distinction.

Building in the West often means building on top of assumed continuity. Electricity is there. Internet is there. Cloud infrastructure is there. Data can move. Systems can be tested and integrated in environments where the baseline is strong enough for advanced work to happen without every layer underneath needing to be renegotiated daily.

That changes the pace of building. It changes the nature of the product questions. It changes what kinds of assumptions founders are able to make. It changes what investors are even evaluating.

Building for the Global South is different.

The environment itself is part of the design problem. Continuity may be uneven. Connectivity may be fragmented. Physical systems may be less instrumented. Infrastructure may be present in one pocket and absent in the next. You are not building in a world where the base layer can be taken for granted. You are building in a world where the base layer is often visible because it is still contested.

That is one reason I think the digital conversation can become shallow very quickly. People talk about digitization as though it were simply a matter of putting software somewhere. But meaningful digital transformation depends on much more than access to software. My own research already argued this in the context of Malawi: digital transformation depends on benefits being visible, innovation being possible, external support being present, and technological conditions being sufficient.

Cyber-physical infrastructure sharpens that truth.

Why Detroit

This is one of the reasons I am building Q2 in Detroit. I am deeply grateful that Q2 is being incubated at Newlab, at Techtown, and at Bamboo.

Detroit gives me the conditions to build the stack properly.

It is a city with industrial memory. A city that understands manufacturing, mobility, logistics, systems, movement, production. A city that has lived inside physical infrastructure long enough to know what it means to make things that move the world. That matters deeply when one is building robotics, sensing systems, autonomy, simulation, and infrastructure logic.

Detroit also has the kind of continuity that makes full-stack system building possible. There is enough there for the work to be completed in earnest. Enough infrastructure. Enough technical ecosystem. Enough industrial relevance. Enough institutional seriousness. Enough of a base layer for advanced systems work not to collapse under the weight of its own dependencies.

And then there is the thing I think policymakers around the world should study much more seriously: policy intention.

Detroit is a city determined to rise again.

You can feel it.

You can feel it in the founder ecosystem. In the public-private attention. In the ambition to rebuild. In the insistence that the future is something the city will participate in, not merely observe from the sidelines. That matters. It matters more than people sometimes admit. Ecosystems are shaped by intention. Cities become buildable because of intention. Entrepreneurial possibility is shaped by intention.

Detroit is interesting to me because it is rebuilding.

That, to me, makes it far more relevant than a frictionless innovation fantasy. It is a city carrying industrial inheritance and future ambition at the same time. It is a city where one can see what intentional recovery looks like when a place decides it will matter again.

That is worth studying closely.

Lessons from Detroit

I want to be careful here, because I am not interested in lazy comparisons between Detroit and the Global South. I am not saying Africa should become Detroit. I am not saying one geography is the template and another is the copy.

What I am saying is that Detroit demonstrates conditions that more places in the Global South should consider having.

Continuity.
Industrial seriousness.
Policy intention.
Public-private alignment.
Technical support systems.
A density of ecosystem actors who make it possible to build, not simply imagine.

That is what I see in Detroit. And when I ask what the Global South should have, I find myself asking for those conditions much more than for any one particular technology.

Because technology always sits downstream of those things.

That is one reason I would even recommend studying Detroit from a policy level. Study the intention. Study the determination. Study the rebuilding logic. Study what happens when a place with industrial history refuses permanent decline and organizes itself around a future.

That lesson is bigger than Detroit.

Building Q2

I am building Q2 in Detroit because I need an environment where the full system can be completed. As a founder, I have incredible responsibility to make this company work.

I need to be able to build the stack, integrate the stack, test the stack, and understand the stack under conditions where continuity is strong enough for the work to proceed honestly. Cyber-physical systems are too demanding to be built entirely inside fantasy. The loop has to work. The robot has to operate. The sensing has to happen. The data has to move. The simulation has to respond. The environment has to be capable of holding the architecture long enough for the architecture to reveal itself.

I deeply believe that Detroit will let me do that, before we can scale/

And that does not reduce my commitment to the Global South. It strengthens it. Because building the full system properly is part of how it becomes adaptable later.

I build where the stack can be completed.
I build for where the stakes are deepest.

Both can be true. In fact, for me, both must be true.

Why Not One Clear Market?

This is the question most people get to ask me, albeit well-meaning. It is also the question entrepreneurship culture keeps training founders to answer in the same way.

Choose one market.
Choose one segment.
Choose one user.
Choose one geography.
Make the story cleaner.
Make the company easier to explain.

I understand that advice. It has logic to it. Clarity matters. Focus matters. Markets matter. Execution discipline matters. I think to me, it is important to hold the bigger vision, and then layer it for execution purposes.

BI cannot flatten Q2 into one neat market story because the reality the company is responding to is not neat.

The technical environment where I can build the full stack is one thing.

The market that can sustain early commercialization is another.

The geographies where the system matters most over the long term may be different again.

And the places where need is highest are not always the places where markets are strongest.

That is the truth.

So when people ask why I do not just focus on one clear market, my answer is because the system itself does not allow me that luxury. The moment I pretend it does, I start building a simpler story than the reality I am actually working within.

And I must not do that.

The Limits of Free Markets

I am reading Big Bets by Rajiv Shah, and one story in particular has stayed with me.

Rajiv reflects on speaking with a pharmaceutical executive and coming to understand something uncomfortable: even when the need is immense, the market may still not justify the business decision to build another plant. Increasing production would require entirely new manufacturing facilities—expensive, time-intensive investments that only make sense if there is credible demand. And for poorer markets, that demand simply does not exist in a way the market can recognize.

That lands.

Because it reveals the gap between human need and market viability.

Those two things are related, but they are not the same.

A free market does not move simply because something matters morally. It moves because the economics justify movement. Capital-intensive systems especially do not emerge simply because the world would benefit from them. They emerge where returns are visible enough, risks are structured enough, and demand is legible enough for investment to make sense.

This matters tremendously for how I think about Q2.

Cyber-physical infrastructure is capital intensive. Robotics is capital intensive. Deep systems work takes time, patience, and serious build environments. And the places where the need is greatest are often the very places where market conditions are weakest or most fragmented. So if one were to say, “Well, if this matters for the Global South, then why not build only there from the start?” my answer would be simple: because systems also have to survive economically.

This is where free markets widen gaps.

They reward the already buildable.
They reward the already instrumented.
They reward continuity.
They reward environments where adoption is easier and less risky.

And that means the places that need foundational systems most are often the places where markets alone will not build them quickly enough.

That is not cynicism. It is systems literacy.

It is also why collective effort matters. Foundational infrastructure has always required more than market logic alone. Public effort, policy alignment, institutional support, and long-horizon investment all matter. They shape what private builders can and cannot do.

Launching Q2 Robotics [QTrax.ai] into Western Markets First

This is also why Q2 Robotics, at launch, will still target Western markets.

That is not me losing sight of the bigger mission.

This is just me understanding market formation.

Western markets offer the continuity, customer readiness, purchasing power, infrastructure conditions, and early commercial viability that a robotics company needs in order to establish itself properly. They offer faster validation. Clearer early revenue paths. More stable adoption environments. A place for the product to enter a functioning market and sustain further development.

That matters because I have moved past building charities. I am now building an infrastructure company.

And infrastructure companies have to survive.

robotics needs more simplification.
build what's necessary, not what's possible.

researchers ask "can we?"
founders ask "who pays for this?"
— emily yu (@emily_yu) April 14, 2026

Launching first into Western markets does not contradict the broader purpose of the company. It supports it. Because the company has to become strong enough, real enough, and economically grounded enough to matter over time. The mission cannot live only as conviction. It has to live as a system that can sustain itself.

So yes, Q2 Robotics launches first where the market can hold it.

That is part of how we earn the right to keep building toward wider relevance.

CPI Makes Missing Foundations Impossible to Ignore

The deeper I go into this work, the more I realize that cyber-physical infrastructure makes missing foundations impossible to romanticize.

One can build lighter digital systems in incomplete environments and still find workarounds. One can route around constraints for a while. One can absorb interruption and still call the experiment successful.

Cyber-physical systems are less forgiving.

They demand continuity from the environment. They depend on the quality of the physical layer. They depend on energy, connectivity, structure, and operational coherence in ways that expose every gap beneath them.

That is why CPI is such an honest layer to build at. It reads the world as it is.

And perhaps that is one reason I am drawn to it. I am drawn to honest systems. Systems that force reality to show itself. Systems that reveal where our ambitions exceed our foundations. Systems that make it harder to perform progress without confronting what actually exists.

Thinking Across Geographies

With Q2, I cannot think in one geography only.

Kenya shows me the gaps in real time.

My research already showed me that digital transformation depends on readiness, support, environment, and perceived value.

Mission 300 and Inga III remind me that foundational infrastructure is already recognized as a continental priority.

Detroit gives me the environment where the stack can be completed properly.

Western markets give Q2 Robotics an early commercial pathway.

The Global South gives the company its deeper relevance.

All of those things are true at once.

And when people ask why I do not just choose one clear market, I find myself returning to the same answer:

Because the problem is not contained to one market.
Because the system spans geographies.
Because need and viability do not sit in the same place evenly.
Because building honestly requires me to hold all of that together.

I cannot focus on one clear market.

I must not.

Build with Me

Here I am, in Kenya, looking out at a system and seeing foundations. Foundations that quite honestly scare me.

I am seeing what cyber-physical infrastructure demands of a place. I am seeing how quickly advanced systems reveal the conditions beneath them. I am seeing, again, why Detroit is the right place to build Q2. I am seeing, again, why the Global South remains central to why the company exists at all. I am seeing, too, why markets alone will never close every gap, and why pretending otherwise only makes the work less honest.

I think that is where I am arriving.

Q2 is being built in Detroit because that is where the system can be completed with integrity.

Q2 is being built for a much wider world because that is where the stakes sit.

And I refuse to shrink that into a simpler story just because simplicity is easier to market.

The system remains what it is.

My responsibility is to build within that reality honestly.