The Southeast Doesn't Need Permission to Build

I've had the conversation enough times that I can finish it before the other person does.

"Oh, you're based in Charlotte?" Yes. "Have you thought about relocating?" I have thought about it. I've decided against it. "But don't you find it limiting?" No.

Here's the version of the answer I usually don't have time to give.

---

The geography argument is a decade stale

The idea that you need to be in San Francisco to do serious work in technology was marginally true in 2012 and is mostly mythology in 2026. The infrastructure that made physical clustering essential — capital concentration, talent density, the serendipitous coffee shop meeting — has been replicated digitally to a degree that makes the coast premium a choice, not a requirement.

Teams are distributed. Capital is mobile. Conferences are hybrid or recorded. The tier-one network that used to require a San Francisco zip code now requires a LinkedIn profile and the willingness to show up, in person or otherwise, when it matters.

What hasn't changed: the assumption that geography is destiny. That assumption is doing a lot of work it can no longer justify, and it costs people real money and real quality of life to believe it.

---

The Southeast corridor is not a consolation prize

Charlotte. Greenville. Atlanta. Nashville. These cities are not aspirationally approaching relevance — they are already producing serious companies, serious capital events, and serious engineering talent. Anyone who tells you otherwise hasn't been paying attention to the last five years of deal flow.

What the Southeast has that the coasts don't: cost of living that allows engineers to build equity instead of spending their entire salary on rent; a talent market that isn't in a permanent war with every funded startup in a three-mile radius; and a genuine proximity to industries — financial services, healthcare, manufacturing, logistics — that are in the middle of meaningful AI-driven transformation and are not going to relocate to SoMa.

I'm not building here because I couldn't make it somewhere else. I'm building here because this is where the problems worth solving are concentrated, and where the operational credibility of having actually worked in those industries still means something.

---

The "flyover" framing is someone else's problem

There's a version of this post that spends a lot of time pushing back on coastal dismissiveness. I'm not particularly interested in writing that version. Whether people in San Francisco take the Southeast seriously is not a constraint on what gets built here.

What I care about is the internal version of the problem: engineers and leaders in the Southeast who have absorbed the idea that where they're building is a limitation to apologize for, rather than a position to lean into. That's the one worth correcting.

If you're building something real in Charlotte, Greenville, Atlanta, or Nashville, you don't need to frame it as "despite being in the Southeast." The Southeast is the frame. Build in it deliberately.

---

Proximity to the unsexy problems is an advantage

The most interesting AI applications right now are not in consumer social. They're in healthcare operations, financial compliance, industrial manufacturing, and supply chain logistics. These industries are headquartered, operated, and — critically — making purchasing decisions in cities like Charlotte, Atlanta, and Nashville.

The practitioner who has spent years inside one of those industries, who understands the regulatory environment, the legacy infrastructure, and the operational reality of the problem — that person has a durable advantage over someone who has never been in the room where the decisions get made.

Geography shapes context. Context shapes credibility. Credibility is what gets you the contract, the partnership, or the offer.

I'm not in the Southeast because I didn't notice San Francisco. I'm here because this is where the context is.