What is an anxious founder?
An anxious founder rarely looks needy. Under stress, a capable founder turns sharp and controlling whenever the bond with a co-founder feels uncertain. Paired with an avoidant co-founder, who pulls back under the same stress, each reaction makes the other worse. You can learn to catch it early.
What does anxious attachment look like in a founder?
It looks like high standards. Underneath, it is often alarm:
- Criticism switches on fast: Tone corrections, "why didn't you", replaying small details.
- Control expands: More approvals, more insisting on being looped in, even outside your area.
- Flooding: More messages, more context, more requests to "just talk quickly."
- Small fights: A fight at least forces contact.
None of this makes you toxic. Handled well, the same sensitivity means you notice drift first.
What is the anxious-avoidant loop?
One of you reaches for contact under stress, the other reaches for distance, and each move sets off the other. This is the pursue-withdraw cycle.
You push for a quick call. Your co-founder goes quiet. You read silence as abandonment and push harder; they read the push as intrusion and pull back further. See the avoidant founder's side.
Each move makes sense to the person making it. Together, they lock the loop.
"Ten messages in an hour feel like care to you and like pressure to them."
The company pays in slow decisions and workarounds. If the loop is already a standing fight, start with cofounder conflict resolution.
What are the early warning signs?
Catch the feeling before the behaviour, and pause there:
- Rehearsing messages: drafting replies in your head
- One more clarification: the urge to add a bit more context
- Scanning reply times: reading meaning into how fast they answered
- Irritation out of scale: a reaction bigger than the event
What should an anxious founder do?
Keep the sensitivity. Stop relying on your co-founder's reply speed to calm you.
- Make one clean ask, then stop: "I'm unsure where we stand. Can we do 20 minutes tomorrow?" Then wait.
- Split repair from decisions: Repair asks "are we okay?" A decision asks "who owns this call?" Hold them in separate conversations.
- Agree a return point: "When you need space, say when you'll come back. When I'm wound up, I'll make one ask and wait."
- Treat the pattern as trainable: Patterns are learned, so they shift with practice.
If one disagreement keeps reopening, a Conflict Session has each of you write your side alone first.