Slow down or die
“We'll get to know each other on the job.”

It's the line I hear most often from founders who've just found each other. It sounds pragmatic, almost wise. Why spend weeks wondering about the other person when you could already be building, testing the market, landing a first customer? At the early stage, time is your scarcest resource, and every week spent “getting to know each other” feels like a week stolen from the product.
I get the reflex. I've had it myself, once, when I mistook wanting to move forward for being sure I'd found the right person. But I see what it leads to too often to keep calling it pragmatism.
The baby comes before the wedding
Teaming up is a bit like an arranged marriage where the baby shows up right away. Two people who barely know each other are suddenly bound by a company that demands everything, immediately: energy, decisions, short nights. The arrangement itself isn't the issue. Plenty of arranged marriages hold up just fine. What goes wrong is that you skip the period where you learn how the other person operates when things go badly. And you skip it because, at the start, nothing is going badly. Everything is new, everything's moving, and the excitement papers over the gaps.
That's the paradox. The only time you can talk calmly about tension is when there isn't any. How you react under pressure. What you do when you disagree: do you go to war, or go quiet? What signal will tell me you're at the end of your rope? These questions feel abstract, almost out of place, when everything's humming along. By the day they become concrete, nobody has the bandwidth to answer them.
The market had said yes
This summer, I worked closely with two cofounders who had met in an accelerator program. They didn't know each other before. They clicked, and their profiles seemed to fit together: one more on the sales side, the other more on product. Six intense months building the company, and a result plenty of people would have envied: a first customer signed on a pilot, real traction. I mentioned them in the manifesto, to make the point that market fit isn't enough. This time, I want to look at what happened earlier.
When it was time to deliver, they hit a wall over how to execute, then over the product vision itself. Nothing unusual so far. Two cofounders who disagree is everyday life at a startup, and often a good sign. What broke wasn't the disagreement. It was that they had no way to work through it. Instead of opening the conversation, one of them abruptly pulled back, to the point of leaving her cofounder alone with the customer on the first delivery call. A few weeks later, she left the company. The other is carrying on alone, with almost everything to rebuild.
I'm not telling this story to point fingers. There isn't really anyone to blame. Those six months of launch had burned them both out, and when the conflict hit, neither had the patience or the energy a hard conversation takes. The signals, though, had been there for a while. Nobody raised them. You tell yourself you'll talk about it when things calm down, things never calm down, and the day it comes out, it all comes out at once.
What could have changed the outcome
Nothing spectacular, which is exactly what makes the story so frustrating. Taking the time, at the start, for each of them to take an honest look at themselves: how they handle risk, money, conflict, how they make decisions. Then comparing those profiles, with a cool head, to spot where things were likely to grind. They would probably have seen the execution disagreement coming, because those differences in how people operate aren't born the day of the pilot. They're there from week one, just invisible.
Above all, they could have agreed on one very simple rule while everything was going well: we tell each other things early, even when it's uncomfortable, even when we're exhausted. A flag raised at 20% frustration gets resolved over coffee. At 90%, it gets resolved by someone leaving.
What slowing down actually looks like
Slowing down doesn't mean six months of soul-searching before you write a line of code. We're talking about a few hours to answer honest questions about yourself, a few frank conversations about how each of you handles pressure, and a trial run on a real problem, under real constraints, before you sign anything, founders' agreement or equity split. A few weeks, not a few months.
Compared with what it costs to skip it, the math is quick. Our two cofounders lost six months of work, a relationship, and maybe a company that had found its market.
So the choice isn't between slowing down and speeding up. It's between slowing down now, when it costs a few hours, or stopping later, when it costs the company.
That's why Ally or Die's first tool starts with the simplest and most overlooked step: looking at yourself before you look at the other person. The questionnaire takes about ten minutes. It's the first stage of what we call the Cofounder Cycle, which we break down here.
Start with you
About ten minutes to find out what kind of cofounder you are, and the profile that complements you.
Take the test