The Resume Nobody Would Touch — and the Company It Eventually Built

Marcus Hale kept a list.

Not a self-help exercise. Not a journaling habit recommended by a therapist. A literal, handwritten list in a spiral notebook — every job he'd lost, every contract canceled, every partnership dissolved, every investor meeting that ended with a polite email saying they were going in a different direction. He started the list when he was twenty-six. By the time he turned thirty-nine, it had forty entries.

Forty.

Most people would have stopped. Most people would have found something stable — a middle-management position somewhere, a predictable salary, the quiet comfort of not failing publicly anymore. Marcus thought about that. He genuinely considered it. And then he looked at the list again.

What a Firing Actually Teaches You

The first few dismissals were straightforwardly humiliating. Marcus was twenty-three, fresh out of a state university in Georgia with a business degree and the kind of confidence that comes from never having been seriously tested. His first job lasted eleven months. His second lasted seven. His third — a sales role at a mid-size logistics company — ended when he was let go in a round of cuts he was almost certainly in because his manager didn't like him.

He was twenty-six and had already been fired three times. He started the list.

At that point, the lesson was simple and not particularly useful: sometimes organizations are dysfunctional, and sometimes you're the one who pays for it. That's true. It's also not actionable.

The more useful education came later, when the failures started to be at least partly his fault.

His first entrepreneurial venture was a catering company he launched at twenty-eight with a friend from college. It folded in fourteen months. The postmortem, when Marcus was honest with himself, was that he had been terrible at managing the relationship between what the business needed and what he wanted it to be. He'd made decisions based on excitement rather than cash flow. He'd hired too fast. He'd avoided a difficult conversation with his business partner until it was too late to have it productively.

Entry four on the list. Lesson recorded.

The Pattern in the Wreckage

Here is the thing about forty failures: at some point, if you're paying attention, they stop being random and start being instructive.

Marcus was paying attention. It was, arguably, the most consistent thing about him. Every time something collapsed, he did the uncomfortable work of figuring out what had actually happened — not the version where external forces were responsible, but the version where he had made choices that contributed to the outcome.

By his mid-thirties, he had a working taxonomy of his own failure modes. He tended to move too fast in the early stages of a venture and too slow once problems emerged. He was good at selling ideas and less good at managing the operational reality that followed. He trusted people quickly and was slow to revise that trust when evidence accumulated that he should.

None of this is the kind of thing that appears in a business school curriculum. You can read case studies about companies that failed for similar reasons. But there's a difference between understanding a failure abstractly and having lived through it, having felt the specific weight of a conversation where you have to tell three employees that payroll isn't coming, having sat with the particular shame of a public stumble in a small industry where everyone knows everyone.

Marcus had all of that. Forty times over.

The Idea That Survived

The company that eventually worked — a supply chain transparency platform that he launched at thirty-nine, shortly after the fortieth entry went into the notebook — was not a dramatic departure from everything he'd tried before. It was, in a sense, the distillation of everything he'd learned.

The idea came from a problem he'd encountered repeatedly across his various failed ventures: companies, especially mid-size ones, had almost no real visibility into what was happening in their supply chains until something went wrong. By then it was always expensive and often public.

He had seen this from multiple angles. He'd been on the vendor side when a client's supply chain collapsed and took his contract with it. He'd been on the operator side when a supplier he'd trusted turned out to be unreliable in ways he hadn't caught early enough. He'd watched, from the outside, as larger companies dealt with the same problem at scale.

The solution he built was not technically revolutionary. The technology existed. What didn't exist was the specific combination of features, the particular user experience design, and — critically — the pricing model that made it accessible to companies that weren't Fortune 500 operations.

That pricing model came directly from his failure history. He knew what small businesses could actually afford because he had run small businesses into the ground. He knew what features actually mattered in a crisis because he had been in those crises. He knew what the sales conversation needed to sound like because he had been on both sides of it dozens of times.

The Pitch That Finally Landed

The investor meetings for the new company were different from the ones that had come before. Not because Marcus was a more polished presenter — though he was — but because he had something most founders don't bring into a pitch room.

He brought the list.

Not literally. He didn't hand investors a spiral notebook. But he talked about his failures directly, specifically, and analytically. He didn't apologize for them or minimize them. He explained what each one had taught him and how those lessons were embedded in the decisions he'd made building the new company.

Investors are used to founders who treat their failure history like a liability to be managed. Marcus treated his like a credential. The forty entries on the list weren't a record of incompetence. They were evidence of a specific kind of education — expensive, uncomfortable, and completely unavailable in any classroom.

The first institutional check came in six months after launch. The company crossed a million in annual recurring revenue before Marcus turned forty-one.

The Notebook Is Still Around

He hasn't added anything to the list in a while. That's not because failure has become impossible — it hasn't. It's because the company has stabilized enough that individual setbacks don't feel like the whole story ending.

But he keeps the notebook. He's mentioned it in interviews a few times, always with the same caveat: he doesn't recommend the path. Forty failures are expensive. They cost money and time and relationships and, for stretches of it, his sense of himself as someone capable of building anything that lasted.

What he recommends is the practice underneath the path. The habit of looking directly at what went wrong, without flinching, and writing it down. The discipline of treating your own mistakes as data rather than verdicts.

The long odds, in his case, weren't just about the external obstacles. They were about surviving yourself — your own bad habits, your own blind spots, your own repeated tendency to make the same category of mistake in slightly different circumstances.

Forty times, he failed. Forty times, he wrote it down. The forty-first time, he built something that lasted.

The notebook is still in the desk drawer. Just in case.