Three Bits Survive the Meeting

I picked up Shannon’s A Mathematical Theory of Communication again last week, on the train back from a round of investor meetings. I had told the same story five times in four days, watched it land well twice, sink without trace once, and get politely misunderstood the other two. By the time I sat down, I wasn’t thinking about entropy in the abstract. I was trying to figure out what had actually happened inside those rooms.

The paper is from 1948 and concerns telegraphs and telephones. After five investor meetings, I read it as an explanation of why a true idea can leave one person’s mouth and arrive in another person’s notes as something else.

I marked the parts that explained where my pitch had leaked.

Information is selection

Shannon’s opening move is the thing everyone remembers but few people take seriously: he strips meaning out entirely. The engineering problem, he says, is that one message gets selected from a set the receiver was already considering, and information is how much that selection narrows the possibility space.

That framing was unforgiving to my deck.

If a wealth-platform CIO hears “AI-powered financial intelligence” and silently files it under another AI vendor, you have transmitted zero bits. The set they were entertaining didn’t narrow. You didn’t show up inside any of the buckets they actually care about (analyst-capacity problem, personalisation at scale, compliant advice automation), so nothing got selected, and nothing got communicated.

The 30-second version of our pitch (“personalised investment advice at scale, without hiring more analysts”) lands inside a problem the buyer already recognises, then narrows it. Give me ten minutes and I start adding language until the useful signal disappears.

Entropy is surprise-per-symbol

Shannon defines the entropy of a source as the average surprise of the next symbol. High entropy means the next thing out of your mouth was hard to predict. Low entropy means it could have come from almost anyone.

“We’re AI-powered, building the future of finance” has near-zero entropy for a fintech investor. Every pitch on their calendar says a version of the same thing. There’s nothing to update on.

“10 signed LOIs representing 500K+ end-users, Liminal-backed, SIX as brokerage partner, SRO coverage across FX, commodities, and digital assets” is high entropy. Very few companies on earth could emit that exact sequence. Every clause changes the posterior.

I now read my own decks with a highlighter, crossing out anything a generic competitor could say word-for-word. What’s left is usually half the length and twice as useful.

Efficient coding matches source statistics

Morse gave “E” a single dot and “Q” a long sequence because E is common in English. Good coding matches the length of each symbol to how often it appears.

Pitches work the same way. Concepts the receiver already processes fluently (fiduciary duty, advice at scale, MiFID) deserve short codes. Lean on them. Don’t re-explain. The listener’s brain autocompletes and you spend nothing.

Concepts the buyer has not already indexed (causal knowledge graph, temporal asset overlay, Mastra runtime) deserve the longer codes. Spell them out, give the example, earn the bandwidth.

The common failure mode is the exact inversion. Founders over-explain what the buyer already knows (the why now for AI in finance, the regulatory tailwind, the market size) and under-explain the part that makes the company different. Swap the lengths.

Redundancy fights noise, but it has a budget

Shannon calculates English at roughly 50% redundant. Which is why you can still read a sentence riddlled with tyops. Redundancy buys you error correction.

Sales and fundraising channels are spectacularly noisy. The buyer is distracted, half-remembers the last call, has three competitors loitering in the back of their head, and will probably re-tell your pitch to a partner in their own words tomorrow morning.

That means you want redundancy across touchpoints: cold email → deck → meeting → follow-up, each carrying the same core message in a different encoding. A good founder story survives any one of those channels dropping out.

What you don’t want is redundancy within a single message: saying the same thing three different ways inside one paragraph. That burns capacity the receiver could have spent on a second point. A lot of decks are full of this. The traction slide says the same number in a bar chart, a logo wall, and a sentence, when it could have used the extra surface area to land the next bit.

The craft is knowing which redundancy you’re currently in.

Only three bits made the train home

This was the note that hurt.

A 30-minute investor meeting has a capacity of maybe two or three bits that actually survive to the partner meeting: [what category are they in], [one differentiator], [one proof point]. That’s it. Everything else is either reinforcing those three or leaking out the sides.

Shannon’s coding theorem says that below capacity you can get arbitrarily high fidelity. You can, in principle, land your message perfectly. Above capacity, no amount of cleverness rescues you. You can’t talk faster around the limit.

So I had to choose which three bits to ship. For Motif right now, the set is [B2B2C wealth intelligence], [causal graph, not RAG/sentiment], [traction plus a regulated path].

Every meeting tempts me to add a fourth. The fourth doesn’t survive. Worse, it elbows one of the first three out of the investor’s notes.

Equivocation tells you what to fix next

After a pitch, the receiver has residual uncertainty about what you actually are. Shannon calls this equivocation: H_y(x), the conditional entropy of the source given what was received.

That residual is diagnostic. It tells you exactly where the channel failed.

The second meeting’s agenda should be whatever the equivocation was after the first, not a re-transmission of what already got through. This sounds obvious and is almost never done. Founders tend to re-run the deck with slightly different adjectives, hoping volume will do what clarity didn’t.

It’s also why a good investor-FAQ doc earns its keep fast. You write it once, and it drives down equivocation on the handful of questions you know come up on every call. Marginal cost: a weekend. Marginal return: every conversation afterward starting one step closer to yes.

The semantic content is “irrelevant”

Shannon’s most provocative line is the one that sits awkwardly on the first page: the semantic aspects of communication are irrelevant to the engineering problem.

That is an ugly sentence when you’re the one pitching. Meaning is the whole reason you built the thing. You did not spend two years on the product so it could be reduced to three bits over a rosé.

The right reading isn’t nihilistic, though. The meaning can be completely intact inside you, fully formed and true, and still not arrive. Sales and fundraising aren’t about having a good thing. They’re the transmission layer for the good thing.

On the train, I opened the deck and removed the fourth bit again. Shannon didn’t tell me what to say. He gave me a less flattering estimate of how much would survive the wire.

Want to chat? X / LinkedIn