Pitch and deck

How pattern matching works, and why it hurts weird companies

Investors pattern-match to move fast, which can punish non-obvious startups unless the founder translates the company clearly.

Jun 27, 20267 min readPitch and deck

A founder I will call the spec walks an investor through a tool that lets factory maintenance teams write inspection reports by talking to their phone. Real pilots, real renewals, a buyer who pays out of a line item that already exists. Twenty minutes in, the partner says the thing that ends most of these meetings: "Interesting. It feels a little niche for us. Keep us posted as you grow." The founder leaves convinced the pitch was unclear. It was not. The investor heard the pitch fine. What happened is that nothing in the story matched a shape the partner had a slot for. No consumer-app curve, no developer-tool adoption motion, no horizontal SaaS land-and-expand. The company was good and the pattern was absent, and absent the pattern, the partner had nowhere to file it.

This is the part founders misread. A pass on a weird company is usually not a verdict on whether the company is good. It is a verdict on whether the investor can recognize the company as a member of a class they already believe in. Those are different judgments, and confusing them sends you into the wrong fix: you sharpen slides when the problem is that you handed the investor a shape they could not catalog.

What founders do, and why it fails

The instinct after a pattern-miss pass is to add. More market detail, more validation, a longer demo, a denser appendix. The founder assumes the investor did not understand, so they explain harder. But the investor understood the words. What was missing was a reference class, and you cannot fix a missing reference class by adding facts inside a class that was never invoked.

The second instinct is to get indignant. "They just don't get it. They only fund what looks like the last winner." That is half true and useless. Pattern matching is not laziness or cowardice, even when it produces lazy passes. It is the rational response to a job where you see far more companies than you can deeply diligence, most of them fail, and your returns come from a handful of outliers you had to commit to before the evidence was conclusive. An investor who refused to pattern-match would have to run full diligence on every deal and would miss the round on the ones that matter. So they compress. They build a library of "things that looked like this and worked" and "things that looked like this and died," and they match incoming companies against it in the first few minutes.

The failure mode for you is not that pattern matching exists. It is that you are treating a compression artifact as if it were the investor's real opinion of your company, and then negotiating with the wrong thing.

The framework: fit, reframe, or reroute

Once you accept that pattern matching is doing the work, a weird-company rejection collapses into three responses, and your only real decision is which one this specific investor calls for.

Fit. The pattern is close and the gap is presentation. Your company genuinely belongs to a class the investor funds, but you described it in your own internal language instead of theirs. A founder building scheduling software for home-services contractors who pitches "we're reinventing how tradespeople run their day" is asking the investor to invent the category. The same company described as "vertical SaaS for a fragmented services market, land with scheduling and expand into payments" lands in a slot the investor already funds. Nothing about the company changed. You stopped making them do the filing.

Reframe. No existing pattern fits, so you build a bridge from a pattern that does. This is analogy work, and it is real strategy, not spin. You are not claiming to be the analog company. You are giving the investor a known curve to reason about yours. "Shopify for X" worked because it imported a believed adoption and monetization curve into a market the investor had not studied. The danger is the lazy analogy that imports the wrong economics ("Uber for lawyers" implies a liquidity model that may not hold). A good reframe names the one mechanism you share with the analog and is explicit about where the analogy stops.

Reroute. The pattern you need is not in this investor's library and will not get there in one meeting. Some investors have funded enough of your shape to hold the pattern natively. Others never will, and educating them is a quarter of work for a maybe. Rerouting is not giving up. It is spending your limited meetings on people whose past deals prove they already carry the pattern your company needs, instead of trying to install a pattern in someone whose whole portfolio argues against it.

The mistake is applying the same response to every pass. Fit-energy on an investor who needs reroute burns your calendar. Reroute-energy on an investor who only needed a reframe throws away a live lead.

Example: the same company, three translations

Take the factory-inspection company from the opening. Here is how each response actually reads.

Founder's native pitch: "We help maintenance teams document inspections by voice so they stop losing knowledge when senior techs retire."

Fit: "Vertical workflow software for industrial maintenance. We start with voice-to-report capture, the wedge, and expand into the compliance and scheduling stack around it. Bottoms-up adoption, paid out of an existing maintenance-software budget." Same company, now filed under vertical SaaS.

Reframe: "Think of the early Toast motion, but for industrial maintenance instead of restaurants. A single painful workflow gets us in the door, daily usage makes us sticky, and the surrounding operational stack becomes the expansion. The mechanism we share is wedge-then-platform in a fragmented, under-software vertical. Where it differs: our buyer is a plant manager, not a restaurant owner, so the sales cycle is longer and the contract is larger." A known curve, with the seams shown.

Reroute: You stop pitching the generalist consumer-leaning fund that has never done industrial and route to the three funds whose portfolios already include field-service, manufacturing-ops, or vertical-SaaS deals. To them, the pattern is not weird. It is Tuesday.

Notice that fit and reframe did not change the company, the metrics, or the honesty of the story. They changed which mental shelf the investor reaches for. Reroute did not change the company either. It changed the room.

The artifact: the pattern-match translation worksheet

Before your next set of meetings, run your company through this once. It forces you to name the pattern problem explicitly instead of discovering it live in the room.

FieldYour answerWhy it matters
Native pitchHow you describe the company to yourself, in your own wordsThis is the version that triggers the "niche / not for us" pass
The pattern you trigger nowWhat shape, if any, an investor files you under on first hearingOften the answer is "none," which is the actual problem
The pattern you wantThe reference class whose believed curve helps you (vertical SaaS, dev tool, marketplace, etc.)You cannot aim a reframe without naming the target
Fit translationYour company in the target pattern's own language, no new claimsUse when the gap is vocabulary, not substance
Reframe analogy"Like [known company] but for [your context]" + the one shared mechanismThe analogy must import a curve, not just a vibe
Where the analogy breaksThe dimension where you are explicitly not the analogStating this builds trust; hiding it gets caught in diligence
Reroute signalWhat in an investor's past deals proves they already hold your patternPast portfolio is the only reliable proof of pattern fit
This investor's verdictFit / Reframe / Reroute, decided before the meetingOne response per investor, chosen on purpose

A decision rule to go with it: if the investor's portfolio already contains two or more companies in your shape, you are in fit-or-reframe territory and should invest in the translation. If their portfolio contains zero and their stated thesis points elsewhere, reroute, and spend the saved hour on someone whose history says yes-shaped things.

Where this connects to running the round

The hard part of this is not writing the translations. It is knowing which investor needs which response, and that judgment lives in their history: what they have funded, what they have passed on, what they say their thesis is versus what their portfolio actually shows. Most founders carry a flat list of names and a vague sense of "good fit," then discover the pattern mismatch in the meeting, which is the most expensive place to find it.

This is the work RoundOS is built to make routine. It pulls your investor context from the sources you already have, your spreadsheet, LinkedIn exports, past notes, into a view that shows each investor's actual deal history alongside your company's shape, so the fit / reframe / reroute call is made before the meeting, not during it. The reroute decision in particular runs on data you should not be eyeballing one tab at a time: which investors have funded companies in your pattern, and which never have. That is a query, not a guess, and it is the difference between ten meetings that start warm and thirty that start with you trying to install a pattern.

Translate the company without flattening it.

Use RoundOS to remember which investor pattern each conversation exposed and route the next pitch accordingly.