We've analyzed roughly 30 founding teams at this point. That's not a massive dataset — I'm not going to pretend it is. But it's enough to notice something: the same patterns keep showing up.

Not vaguely similar patterns. The same ones. Different companies, different industries, different founders — and yet the team risk profiles cluster into a handful of recognizable shapes. Once you've seen them enough times, you start to spot them before the data even comes back.

Here are the three we see most often.

Pattern 1: The Mirror Team

This one is the most dangerous because it feels like a strength.

Two cofounders who think alike, communicate the same way, and agree on almost everything. In interviews, they finish each other's sentences. They present beautifully together. Everyone walks away thinking, "wow, those two are really aligned."

They are aligned. That's the problem.

We ran an analysis on a founding team where both cofounders scored high on extroversion, high on collaboration, and high on adaptability. On paper, they looked like a dream team — strong presenters, great chemistry, clearly liked working together.

But the data also showed something less obvious: neither of them scored high on analytical thinking or independent decision-making. They were both consensus-seekers. They were both relationship-first operators. And neither was naturally inclined to challenge the other's assumptions.

What does that look like in practice? It looks like a fundraising pitch with compelling energy and no stress-tested financials. It looks like a product roadmap built on enthusiasm rather than data. It looks like two people who agree their way into bad decisions because disagreeing feels uncomfortable.

The investor working with this team saw it immediately. He'd already suspected the gap existed — he just didn't have structured data to confirm it or a framework for addressing it. When he saw the report, his reaction wasn't surprise. It was validation.

The chemistry is real. But chemistry without friction is how you build a company that feels great and executes poorly.

The fix for a mirror team isn't breaking up the partnership. It's recognizing the gap and filling it — either by adding a team member who thinks differently, or by deliberately assigning one cofounder to play devil's advocate before major decisions. The chemistry is real. But chemistry without friction is how you build a company that feels great and executes poorly.

Pattern 2: The Silent Fault Line

This is the pattern that traditional assessments almost never catch — because in an interview, everything looks fine.

We assessed a cofounder pair where one person was highly independent and technically driven, and the other was highly adaptable and relationship-focused. On the surface, that sounds complementary. One builds, the other sells. Classic pairing.

But when we ran the team simulation, a specific risk emerged: the adaptable cofounder was so conflict-averse that they would quietly absorb frustration rather than raise it. And the independent cofounder was so heads-down that they wouldn't notice the tension building. We called it the "Nice Guy vs. the Lone Wolf" — a dynamic where one person swallows problems to keep the peace, and the other person doesn't realize there's a problem until it explodes.

The studio operator working with this team told us the analysis "feels directionally accurate" and that they were already working through some of those exact issues. That's what the silent fault line looks like from the inside — you can feel it, but you can't always name it, and you definitely can't see it in a resume or a reference check.

We've seen a version of this pattern in another team, where we flagged a time management bottleneck in a CTO who'd been working with his cofounder for years. The CEO's reaction wasn't denial. It was relief. He told me he'd been managing around that exact issue for eight years. The team had unconsciously built systems to mask it — workarounds, compensating behaviors, adjusted expectations. The risk was real but invisible. It would never have surfaced in an interview or a personality test. It only became visible when we looked at how the two people actually operated as a unit, not as individuals.

The silent fault line doesn't mean the team is doomed. It means there's a specific pressure point that, if left unaddressed, will crack under stress.

Naming it early is often enough — because once both cofounders see it, they can build explicit agreements around how to handle it rather than dancing around it indefinitely.

Pattern 3: "We Don't Have Any Team Issues"

I almost called this one "The Missing Piece Nobody Sees." But honestly, the more teams I analyze, the more I realize the real pattern isn't a missing skill — it's the conviction that nothing is wrong.

This is the one that's hardest to talk about, because founders don't want to hear it.

We ran a debrief with a founding team where our analysis had flagged that the cofounders were both highly collaborative and might struggle to challenge each other's assumptions — particularly around financial projections and fundraising strategy. During the debrief call, both founders pushed back. Hard.

One of them said he would never accept unfavorable terms and that his financials were thoroughly stress-tested. The other said the risk wasn't on his radar. They questioned the methodology. They questioned where the predictions came from. They aligned with each other against the findings — quickly, instinctively, as a unit.

Here's the thing: the report had specifically predicted that this team's default behavior under pressure would be to band together, reinforce each other's assumptions, and resist outside challenge. And that's exactly what happened on the call. The investor observing the session noticed it. He told me afterward that their behavior during the debrief was, in itself, confirmation of the risk we'd flagged.

The founding team later said the analysis might be worth $100. The investor, who had already lost $80,000 on a previous hire that didn't work out, saw it differently.

I don't share this to embarrass anyone. Both founders were smart, driven, and clearly committed to their company. But the pattern is real, and it's common: the teams most at risk are often the ones most convinced they're fine. They don't see the gap because they're standing in it.

This is why team diligence has to be done by the investor or studio operator — not by the founders themselves. Founders are too close to their own dynamics to see them objectively. That's not a character flaw. It's human nature. The whole point of structured assessment is to surface what the people inside the team can't see from the inside.

What To Do About It

Every studio I talk to has a version of these stories in their portfolio. They've seen the mirror team that couldn't close because nobody pushed back on a weak pitch. They've felt the silent fault line in a founding pair that slowly stopped communicating. They've watched a team insist everything was fine right up until it wasn't.

The patterns are real. They're also addressable — but only if you look for them before committing capital and resources.

Three things that help:

  1. Assess at the team level, not just the individual level. DISC and Predictive Index will tell you who someone is. They won't tell you what happens when two specific people try to build a specific company together under real pressure. The interaction is where the risk lives.
  2. Look for the risk you hope isn't there, not just the strengths you want to confirm. Confirmation bias is the enemy of good team diligence. If the only question you're asking is "can these people do the job," you'll miss the question that actually matters: "what's going to go wrong between them when things get hard?"
  3. Track your outcomes and feed them back in. Every team decision is a data point. Did the risk you flagged actually manifest? Did the hire you recommended work out? Studios that track this build a compounding advantage — a proprietary dataset that makes every future prediction more accurate for their specific portfolio.

The studios that start doing this now won't just avoid expensive mistakes. They'll build something nobody else has: real data on what team configurations actually work, calibrated to their own track record. That's an asset that compounds, and it's one that no amount of gut instinct can replicate.