the sixty million dollar no was hiding on slide eleven
how do you talk about a deal you turned down in a pitch deck? a logistics founder walked away from about $60m a year. his deck told it two ways.
this morning i taped with a founder building an ai operating layer for global shipping. an industry that still runs on email, whatsapp and paper.
he's been in logistics for sixteen years. he started a freight brokerage in his second year of computer science. and he lost six hundred thousand dollars of his own money to the exact problem he now solves... demurrage fees, lost containers, customs overcharges, currency swinging while a container sat missing for weeks.
he doesn't call it a loss. "i call it a nice tuition fee... i finance this problem. i didn't just discover it. i financed."
i love that line. but it wasn't the peak of the episode.
the peak was when i asked him... "you walked away from what like a $60 million a year contract because the infrastructure wasn't ready. can you kind of talk me through that decision?"
an oil boom. a contract to supply gravel. roughly sixty million dollars a year on the table. and the final blocker would have meant custom building a vessel. he said no.
on air it sounds like pure discipline. the kind of story an investor repeats to their partners on monday.
but when i prepped for the show, i found the same story in his deck twice, and the two versions fought each other.
on the traction slide it showed up as "$60m+ inbound demand." on slide eleven it showed up as a refusal.
an investor flipping through hits the big number early and gets excited. eight slides later they find out it never closed. now the first slide feels like a stretch, and they start wondering what else is a stretch.
that's the danger with a deal you turned down. told one way it's your best proof of judgment. told two ways it looks like you're hoping nobody connects the dots.
so if you're wondering how to talk about a deal you turned down in a pitch deck, my answer is one story, told once, told on purpose.
put it where it proves something. for him that's not traction, it's judgment. demand found him before he went looking, and he had the spine to say not yet because the operation couldn't deliver. that tells an investor two things at once. the market pulls. and the founder won't blow up the company chasing revenue he can't serve.
then say what it would take to say yes next time. what infrastructure, what capital, what timeline. now the no becomes the reason for the raise.
it's like a chef who turns down a wedding for five hundred because the kitchen seats eighty. you don't hide that from the next investor. you tell them, and then you show them the plan for the bigger kitchen.
founders bury their best stories all the time because they think anything that didn't close is a weakness. investors read it the other way. they've watched plenty of companies die from taking the wrong deal, and hardly any from turning one down.
the losses work the same way. that six hundred thousand isn't a scar to hide. it's the receipt that proves he knows the problem better than anyone pitching a slide about it.
long term the founders who raise easy are the ones whose deck and whose voice tell the same story. if it sounds great on a podcast and confusing in a pdf, the pdf wins, because the pdf is what gets forwarded.
i put the things i check in every deck before a raise into the founder's fundraising checklist. this one's on it now.
so what's the best no you ever said... and is it in your deck once, twice, or not at all?
the machine economy brief
one email when it matters: bitcoin, ai, robotics, and what founders should do about it. unsubscribe anytime.