A founder told me last month that he didn't think Detroit could teach him anything about building at scale. He lives in Midtown. He has a real product, a real team, a real customer pipeline. But when he thought "scale" he thought somewhere else — talent in the Bay, capital in New York, advisors in some other zip code.

I sat with that for a minute and then I told him I disagreed.

The city has done this before

Detroit has been doing scale for a hundred and twenty years. Not the kind of scale that gets a TechCrunch headline. The kind that builds things that exist in the physical world, in the kinds of weather that test whether you actually built it well. Then loses most of it. Then rebuilds, in a different industry, with a different posture.

The city has been through everything a founder is afraid of going through. Bankruptcy. Desertion. The slow erosion when your headline industry leaves and you have to figure out what you are without it. It didn't do any of that gracefully — the romance of the comeback story papers over how hard the rebuilding actually is. But it rebuilt. It's still rebuilding. And that's the part that matters for you.

The city as an old founder

Sit with that and the city starts to look like an old founder. The kind who's been through enough to be slower to panic. The kind who knows the difference between what's happening and what only feels like it's happening. The kind who's earned the right to not flinch.

When you're stuck, you don't have to get on a plane to find the answer. You can look out your window. The city outside it has done harder pivots than the one in front of you, on a worse hand. It's available to you, in a real and unsentimental sense, as a coach. (And the capital is closer than founders here assume — plenty of this city got rebuilt on Midwest money that never needed a coastal area code.)

But it doesn't build slow

Here's the half the comeback story misses — and the half I've watched change with my own eyes. Over the twenty years I've been watching this place, and the sixteen I've spent building companies in it, the thing that's struck me hardest isn't the patience. It's the speed.

As we were building StockX from the heart of Detroit — overlooking Woodward and the Detroit River — I watched it go from a handful of us to a company last valued at $3.7 billion, on a timeline that still surprises me to say out loud. That wasn't a coastal story. It happened here, and it happened fast.

And it wasn't the first. The way I see it, Duo Security — started by Dug Song — helped start the snowball: proof that a world-changing company could be built in this region and exit at a scale that made the rest of the country look up. That's the thing about a snowball: once one founder here shows it's possible, the next one believes it faster, raises faster, hires the people who already did it once. The companies getting built here now are bigger and faster than they were — eight- and nine-figure businesses on timelines that would've been hard to imagine when I started, and the curve is still bending the right way. If you came up believing the Midwest is where ambition goes to be reasonable, you've been reading an old map.

Part of that is capital and know-how moving faster than they used to. A big part is that the ecosystem is being built on purpose now. Organizations like GFF, the MEDC, TechTown, and Ann Arbor SPARK are putting real weight behind the scaffolding a founder here actually needs — capital, mentorship, the connective tissue, a path that doesn't require improvising every step alone. Twenty years ago a founder here cobbled most of that together solo. Today it's increasingly there for the using, and it compounds: every founder who builds something big here makes the next one's odds a little better.

There's one honest caveat, and it's about money. Right now, capital is the only lagging indicator. Everything else you need to build to eight and nine figures is already here — the talent, the customers, the operators who've done it before, the will. The money is here too. It just doesn't flow as fast as it does in Silicon Valley yet. I say right now on purpose: a lot of us in the ecosystem are working on exactly this — bringing more awareness to investors, showing them what's being built here and how quickly — so the capital starts stepping on the gas the way everything else already has. The gap is closing, and it's closing because people are deliberately closing it.

So when I say the city is a coach, I don't mean one who tells you to slow down. I mean one who's survived every hard thing and still gets up early to build the next big one — faster than the last.

What the city teaches

Grit is one of the things that sets builders here apart — earned, not advertised. It looks like showing up year after year and building without an audience. The city drills a few things into anyone who sticks with it long enough to listen:

• Resourcefulness as default, not virtue. It shows up in the budget line items, not the keynote slide.
• Customer proximity. Your customers are within a four-hour drive, in industries you can actually talk to, with problems that pay real money.
• Patience without slowness. The discipline to not panic is not the same as taking your time. The builders who do best here hold their nerve and move fast — those aren't in tension.
• Real scale, built faster every year. This isn't lifestyle-business country. The ambition is eight and nine figures, the timelines keep shrinking, and there's now an ecosystem actively working to shrink them more.

The biggest small city in the world

People call Detroit the biggest small city in the world, and they've got it right. It has the scale of a major metro and the social fabric of a small town — you're two introductions from almost anyone, and the people who've already built something want to see you build yours. There's a reason one of the city's unofficial mottos, stamped on a homegrown brand, is Detroit Hustles Harder. The grit isn't a marketing line. It's real, and it pushes people here harder and with more determination than I've seen anywhere else — and then it turns around and spends that same energy on the person next to them.

That's the part outsiders miss. We want each other to win, and we'll do whatever we can to help. I spend real time with people and organizations who back the kind of founder this region produces and share this vision for the Midwest — groups like Venture Builders and a growing number of operators, funders, and builders who can feel the same thing happening here. More and more of us are seeing it, and amplifying it to the world. The snowball isn't only companies. It's a community deciding, out loud, that this is a place where world-changing things get built — and then doing whatever it takes to make that true for the next founder.

Let the city into the company

The founders I've coached here who do best are the ones who let the city become part of their company. Not as branding — not the I-heart-Detroit T-shirt, not the curated industrial loft. As posture. They hire local by default. They put the customer first, because the customer is forty miles down I-75. They keep the resourcefulness in the line items, not the language. And they use the ecosystem that's actually here now instead of pretending they have to do it alone.

I've watched coastal founders drop into Detroit for a panel and leave confused — they came expecting scrappy underdogs and couldn't figure out why the people they met didn't perform that role. The reason is simple. Detroit founders aren't underdogs. They're builders, in a city that already knows what building requires, moving faster than the story about them has caught up to.

Pay attention to where you are. The city has been through everything you're afraid of — and it's building bigger and faster than it ever has. Both are true at once, and together they're the advantage: the nerve to not flinch, in a place that's accelerating. The city is teaching, whether you decided to learn or not.

There's a specific kind of tired founders carry that doesn't get talked about enough. It's not the loud kind. Burnout is loud. This is quieter.

It's the tired you bring with you when you go on vacation. Your body is on the beach. Some part of you is still on the call you didn't take Friday afternoon. You sleep ten hours and wake up still feeling the shape of the thing you were going to think about. The thing isn't what you're working on. It's the fact that the thing exists, and it can fail without warning, and the buck for that failure stops with you.

I see this in the founders I coach. They come in describing it differently. I'm just exhausted. I haven't been sleeping well. I think I need a break. Then they take the break and come back four days later and it's still there. They tell me the break didn't work and they're worried they're broken.

Why the break doesn't work

The break didn't work because the break didn't address what's actually depleting them. They aren't tired the way someone who just ran a marathon is tired. They're tired the way someone is tired when they've been carrying a thing they can't put down — and the carrying is invisible to everyone around them, and they can't tell whether they're allowed to set it down even for a weekend.

The hustle culture answer to this is push through. The wellness culture answer is take care of yourself. Neither one is what the founder needs. Push through assumes the depletion is laziness; take care of yourself assumes it's a self-care deficit you can solve with a meditation app. The actual thing is structural. A thing that can fail without warning is a thing that lives in the back of your head whether you want it to or not.

What actually helps

What actually helps, in my experience, is more pedestrian than either of those scripts. Three things, none of them a hack:

• Someone you can describe the shape of the thing to, who isn't going to try to fix it. Not an investor or a board member or a co-founder — those people have a stake in the answer. A friend, ideally. Or another founder a few years ahead of you who has already carried something like it. The thing gets lighter — not gone, lighter — when another person knows the shape.
• A real fence around the days you don't carry it. Not a rule. A fence. Something physical. Phone in another room. Calendar blocked. The dog walked at the same time every day so the day has a structure that isn't the company. The fence is what makes the day yours instead of a holding pattern between work hours.
• Honesty with the people you do life with with about what you're carrying. They mostly already know. Pretending it's fine for their sake is more depleting than telling them it's not.

The honest version

I don't have a clean version of this. I'm a founder who's been doing this for a long time and I still get it wrong. I take vacations and feel worse on Tuesday. I tell myself I'm fine when I'm not. I optimize my way out of conversations with my family because the company seems more urgent in the moment.

The thing I've learned, slowly, is that the tired isn't a problem to solve. It's a feature of the work — the work being being responsible for a thing. The honest move isn't to cure the tired. The honest move is to build a life around it that lets the tired be one input among many, instead of the thing that organizes everything else. Build into the crazy some space that allow a distraction-free pause.

That's a quieter answer than either script offers. I think it's also a truer one.

Founders book time with me to talk about a feature decision, or a hire, or a customer they're "still trying to land." Those are the disguises. They've been here three months. Six months. A year. The thing the conversation keeps circling is the pivot, dressed up as something else.

I've sat in that chair. I've also coached more than a hundred founders out of it. Every meeting opens with what's about to happen, many meetings end with the same thing not having happened.

The pivot isn't usually scary because it's wrong. It's scary because making it forces you to admit the version of the company you've been quietly grieving. The startup you pitched at the beginning. The first three customers you thought were going to be the wedge. The roadmap you spent two months convincing your engineering team was correct. To pivot is to say, that version of the company isn't coming back. That sentence is what founders defer.

The signals

When I look at a founder mid-deferral, there's a pattern. Not an algorithm — a pattern. The signals show up in a sequence I've come to recognize:

• The customer keeps almost-buying. They love the demo. They tell three people about you. They never sign. Or they sign and never use it. After the third we love it, just need to think about it email, you're not negotiating price — you're being told something about the problem you haven't heard yet.
• You're describing the company differently to different audiences and not noticing. Investors get one frame, customers get another, the team gets a third. The company isn't the same company in three rooms. It's three companies trying to fit in one body.
• You're defending the original idea more than building it. The energy has shifted from the work to the explanation of the work. That's the loudest signal, and it's usually the last one you'll spot in yourself. Most founders feel it before they see it.
• You've decided on the customer by only talking with the users. The conversations have only happened with friends or the people who will be using the product. The conversation hasn't happened with the actual customer yet.

When I see two of these, I tell the founder it's time to look at this hard. When I see three, I tell them they're already mid-pivot — they just haven't let themselves write it down.

What's actually scary

The reason most founders defer the pivot, in my experience, isn't strategic. It's identity. The version of you who started the company is in love with that company. The version of you twelve months in has more information than that earlier version ever did. They are not the same person. The pivot is the new version giving the older version permission to stop holding on.

I've pivoted more than once. The companies of mine that worked were the ones where I let the new information win.

The cost of NOT pivoting isn't usually money. Most founders running out the clock have enough for another six to twelve months. It's time and energy — the parts of the founder budget hardest to read and easiest to drain. Every week you defer is a week of your team's energy spent defending a thesis you already stopped believing, and a week of your own time you can't get back.

Talk to your customers

The biggest reason most founders end up pivoting isn't that the original idea was bad. It's that they finally talked to their customers and learned what those customers were actually trying to do — and it wasn't quite what the founder had assumed.

Customer discovery is the engine of the pivot in two directions at once. It tells you whether to pivot — the original problem either holds up to honest conversation or it doesn't. And it tells you where to pivot to — the problem that keeps showing up in the conversations is the new direction. Without discovery, every pivot is a guess. With it, every pivot is following information.

I've had founders come to me, months in, with what they think is bad news. They've been digging into an ecosystem, learning the players, talking to people — and they can't find a real problem to build against. They're disappointed. I reframe it as a win, every time. You're at a spot most entrepreneurs don't reach until they've built a product, tried to sell it, and burned through eighteen months of runway. You found out before building. That's not a failure — that's the work, done in the right order.

Here's the pattern I tell founders, especially the ones avoiding the conversations:

If you can't get to your customer just to ask them about their problems, you have to understand that it's exponentially harder to get to them to buy your product. The conversation becomes that much easier when you know where to find them and you know the very specific problem you're solving.

The how is simple and almost always under-done. Pick fifteen people who match your imagined customer and have a real conversation with each one — not a survey, a conversation. Ask about the last time the problem happened. Ask what they did instead. Ask who else was involved and what it cost them. Don't sell. Don't pitch. Listen for the moment they describe a frustration without your prompting.

And define the customer narrowly first — small business or mid-market, marketing team or marketing agency, consultant or internal lead. The product might end up serving all of them eventually. You can't learn about all of them at once.

The de-risker

If you want one: a self-funded pilot. Not a rebuild. Not a re-pitch. A two-week or four-week pilot where you put a stripped-down version of the new direction in front of three or five customers from your discovery conversations and see if the conversation feels different.

If they're still telling you about the old problem, you stay where you are. If they're leaning forward in a way they never did with the original product, you have your answer. You also have the artifact you need to talk to your investors and your team without it being a confession.

The pivot is rarely as scary as not making it. The founder mid-pivot, even if the new direction turns out to be wrong, has agency. The founder running out the clock on a thesis they stopped believing six months ago is the one I worry about — because every week they wait, they pay in time and energy they can't get back.

If the pivot has been on your table for three months and you keep almost making it: it's already on the table. The decision has been made. The only question is whether you make it visible.

The founder books time with me because they can't get traction or more specifically they don't know how to. They want to talk about pricing, or sales process, or what's wrong with the cold-email cadence, or whether they should be hiring a VP of marketing. Those are the surface symptoms. They've come to me thinking the diagnosis is somewhere in the surface symptoms.

I almost never start there.

One question

I ask one question. What problem are you solving and who are you solving it for? And then I let them talk for as long as they want.

The first thirty seconds of that answer is the diagnostic. Most founders, when you ask that question, don't describe a problem. They describe their solution and then back-derive a problem from it. We're solving the lack of [the thing our product does] for [the audience our product targets].

A person doing a thing they don't want to do

Real problems don't sound like that. Real problems sound like a person, doing a thing they don't want to do, in a moment they remember vividly. The data analyst who exports the same dashboard to a CSV every Monday, cleans it up by hand in a spreadsheet, and re-uploads it somewhere else, because the two systems don't talk and the integration the vendor promised has been a roadmap item for a year. The backend engineer SSH-ing into a production server at eleven at night to restart a service by hand, because the deploy reported success and wasn't, and nothing pages anyone when that happens. The support lead who keeps a private doc of which bugs are actually on fire and the one-line workarounds for each, because the ticketing system sorts by date instead of by pain, so every new hire rebuilds that triage knowledge from scratch. Those are problems.

The dig-deeper exercise

Most founders coming to me for help with traction don't have a problem like that articulated. They have a category of users, a hypothesis about what those users want, and a product they've already built. The problem-shaped hole at the center of all that work is the thing they need to find before any tactical fix matters.

So I run an exercise, and it isn't a clever one — it's the Five Whys, the thing off the Toyota assembly line, except I point it at the founder's problem statement instead of a defect on the line. Take the sentence you just gave me — we're solving the lack of [our thing] for [our audience] — and ask why that's a problem. Then ask why about the answer. Then again. Five times, give or take; you're not counting, you're drilling.

One of two things happens. Either each why drops you somewhere more specific and more human than the last:

Why doesn't the data come out clean? Because the export was built for the accounting team, not the analysts. Why does that matter? Because the analyst can't trust the numbers without re-checking them by hand. Why does that cost anything? Because she spends Monday morning doing that instead of the analysis someone actually asked her for.

And there it is — a person, a morning, a thing she doesn't want to be doing. That's a problem you can build against.

Or — the more common outcome — the whys run out of road in two steps. Why is that a problem? Because people would use the product. Why? Because it does the thing. That's not a chain, it's a circle. If your problem statement can't survive three honest whys, you don't have a problem yet — you have a product looking for one.

There's a second cut to make while you're down there, and it's the one founders skip — which is exactly why I make them answer who are you solving it for? up front. Whose pain did you just drill into, and is that the same person who will pay for it? Users aren't always customers; customers aren't always users. The analyst feeling it on Monday morning doesn't sign the contract — her VP of Data does, and the VP's pain isn't my morning is annoying, it's I can't tell the board whether our numbers are right. Same root, two completely different sentences — and if you build and message for the user when the customer holds the budget, or the reverse, you get warm nods in every demo and a signature in none of them. The exercise isn't finished when you've found a pain. It's finished when you know whose pain it is, what it costs that person, and whether that person is the one who can say yes.

I don't say that to be brutal. I say it because solving the wrong problem for the wrong customer is the most expensive friend a startup can have. They give you enough hope to keep building. They give you anecdotal validation. They give you a logo. They never give you the kind of revenue or referral velocity that would tell a board, we have a thing. You spend eighteen months in a slow conversation that won't end and won't grow.

The shift, when it lands, isn't dramatic. It's a founder going home and rewriting their messaging — not because the old messaging was bad, but because they suddenly know what they're actually selling. It's reorienting an outbound list. It's hearing a customer call differently. It's a quieter, more specific way of describing what they do.

Customer discovery: the rules

Customer discovery is the bridge to all of that. Not a survey. A real conversation. The rules I tell founders are simple:

• Ask about the last time the problem happened, not whether it happens.
• Ask what they did instead of using anything.
• Ask who else was involved and what it cost them.
• Don't say what your product does.
• Don't say what you wish were true.
• Listen for the moment they passionately describe a frustration they had.

The founders I see make it past month eighteen are not the ones with the slickest decks or the most disciplined sales process. They're the ones who, before they hired a VP of marketing or rewrote pricing or cold-emailed harder, sat with the question what problem am I solving? until the answer was a person doing a thing.

The traction problem under the traction problem is almost always that the problem under the problem hasn't been found yet.

It's in San Francisco. Or Palo Alto. Or Austin. Or New York City. Or wherever this week's demo day is. Founders pitch from a stage to investors who will see fifty more pitches that day. The energy is electric. The deal flow is real. The terms can move fast enough to make your head spin.

I always thought we could build from Detroit. So did my co-founders at UpTo. So did my team when we built what became StockX.

So we did.

We built our companies overlooking the Detroit River and along Woodward Avenue where the world changing Model T first ran freely.

That's not to say we didn't spend any time on the coasts though. We did walk Sand Hill Road for UpTo but most of our money came directly from Detroit and Midwest-based venture firms. StockX raised its initial capital because those same investors believed in us. StockX has since raised money globally. These investments in both us and the products we built confirmed what I already knew. Detroit has its own grit; we build from where we're at.

Steve Case puts it well: "It's stunning to me what kind of an impact even one person can have if they have the right passion, perspective and are able to align the interest of a great team."

This is what actually builds companies. The pitch circuit doesn't.

That's true on Sand Hill Road, and it's true at the founder pitch contests right here in Detroit — the local circuit has the same gravity, just at smaller scale. Pitch culture rewards vanity metrics: users, growth rate, total addressable market (TAM), "engagement." A customer telling you they wish your product did one specific thing is information. An investor or a judge telling you your TAM looks small is information too, but it's a different kind. None of that is what actually makes a company. Customer discovery does. Getting customers to pay for something that saves them time, money, or energy — that does.

Solve the customer's problem and they will give you money. That's the whole loop. Everything else is performant.

I've coached a lot of founders at this point. The ones I see making the most damaging decisions are usually the ones who build product without talking to customers or who are closest to capital. Not because capital is bad. Because the room rewires you. You start optimizing for the next round instead of the next customer. You start telling the story your investors want to hear, and then — because human beings are bad at holding two stories in their heads — you start believing it. By the time the story breaks, you're well past the point where a smaller, harder pivot would have saved you.

So when a founder in Detroit asks me whether they should move, the honest answer is usually no. Not unless they already have product-market fit and they're tapping into the coasts to scale a thing that's already working. If they're going there to find their business, they'll find an enthusiastic ecosystem that will help them build a great pitch deck for a business that doesn't exist yet. They will be building in a sea of companies that will drown out their voice.

The room I'm not in has a lot to offer. I don't want to romanticize being away from it. There are deals I haven't been in, people I haven't met, momentum I haven't ridden. There is more and quicker access to capital to build and scale faster. That's all real.

But there's also a kind of clarity that comes from building in a place that is rooting you on. That is excited for you and encourages the grit you are fighting with. It isn't watching you build for investors, it's watching you build to change the world, and to solve a problem you care deeply about for the customer you are fighting for. It doesn't have the other noise, it lets you find and focus on your customers directly. The actual market. The thing the company is supposed to be for.

I get to hear them. They get to be heard.

That trade is fine with me.