Adam and I built Vulpine Creations together from a kitchen table to an acquisition over four years. We never had a serious fight. We never considered dissolving the partnership. We never once questioned whether we’d chosen the right person.
This is extremely unusual. The co-founder relationship is, statistically, the most likely point of failure for startups. More companies die from co-founder conflict than from market failure, product failure, or funding failure combined.
Our partnership worked. Here’s why — and it starts with a conversation we had before we wrote a single line of business plan.
The Values Interview
Before Adam and I committed to building Vulpine together, we spent three hours talking about three things. Not business strategy. Not market opportunity. Not roles and responsibilities. Values.
The three questions:
“What does a successful Tuesday look like for you?” Not a successful quarter. Not a successful year. A Tuesday. The answer reveals what daily life looks like when things are going well. If one partner’s successful Tuesday involves working alone in deep focus and the other’s involves constant collaboration and meetings, there’s a structural incompatibility that no amount of goodwill can resolve.
Adam’s answer: working on product quality, solving a technical problem, ending the day knowing something is better than it was yesterday. My answer: similar enough that the overlap was clear. We both wanted to make things better, not bigger.
“What would make you walk away from a profitable project?” This question reveals non-negotiable values. If one partner would walk away from ethical compromise and the other would tolerate it for revenue, the first major ethical test will destroy the partnership.
Both of us named quality compromise as a walkaway. If maintaining our quality standard became impossible — if the market forced us to cut corners to survive — we’d rather shut down than ship something we weren’t proud of. This alignment was tested during the pandemic when cash was tight and the temptation to cut material costs was real. Neither of us wavered.
“What are the three things you refuse to compromise on?” This question surfaces the hard boundaries before they’re tested under pressure.
I learned this values interview framework from the wreckage of my earlier partnership disaster. That partnership failed because we never had this conversation. The values differences only became visible under stress — the worst possible time to discover them.
The Role Division
After values, the second factor in our partnership’s success was clear, complementary roles.
Adam owned product development and quality control. I owned marketing, sales, and operations. Each partner had final decision-making authority in their domain. Disagreements in overlapping areas were resolved through a simple protocol: present the case, hear the countercase, decide within 24 hours. If we couldn’t agree, the partner whose domain was most affected had the tiebreaker.
We never used the tiebreaker. Not because we always agreed — we frequently disagreed — but because the discipline of presenting a case to someone who might reject it forced better thinking. Most disagreements resolved themselves when both sides articulated their reasoning clearly.
The role division also prevented the owner dependency from concentrating in one person. If I was unavailable, Adam could run the business at 70% capacity. If Adam was unavailable, I could do the same. Neither of us was a single point of failure for the critical functions.
The Communication Structure
We talked every day. Not informally — structurally.
Daily sync (15 minutes, morning). What happened yesterday. What’s planned today. Any decisions needed. No deep discussion — just alignment. If a topic needed more than two minutes, it went on the weekly agenda.
Weekly strategy (60 minutes, Thursday). Deeper discussion of strategy, challenges, and opportunities. Review of weekly metrics. Decisions on anything that had been deferred during the week. This was the meeting where disagreements were aired and resolved.
Monthly review (90 minutes, first Monday). Financial review. Product roadmap assessment. Partnership health check. The health check was explicit: “Is there anything about how we’re working together that needs to change?” The question felt awkward the first time. By the sixth month, it felt natural. And the act of asking it regularly prevented small irritations from accumulating into large resentments.
Why Most Partnerships Fail
Based on what I’ve observed across my own partnerships and the 40+ startups at Startup Burgenland, partnerships fail for three reasons:
Unexamined value differences. Partners who share a business vision may not share personal values. The vision gets them started. The value differences pull them apart under pressure. The values interview prevents this by making the differences visible before they’re tested.
Undefined roles. When both partners think they’re responsible for everything, they spend more time negotiating decisions than making them. When neither partner is responsible for a specific function, that function suffers. Clear, documented role divisions eliminate both problems.
Communication debt. Small frustrations that go unmentioned accumulate like financial debt — quietly, invisibly, until the interest payments become unmanageable. The monthly health check prevents communication debt by creating a regular, structured opportunity to name frustrations before they compound.
The End of the Partnership
When we exited Vulpine, the partnership ended professionally and personally intact. We split the proceeds according to our original agreement. We remain friends. We occasionally have coffee and talk about what we’re building next.
This outcome isn’t remarkable because it’s exceptional — it should be normal. But it isn’t, because most partnerships don’t invest in the foundation that makes a clean exit possible: aligned values, clear roles, structured communication, and the discipline to address problems before they become crises.
If you’re considering a co-founder: have the values interview first. Define the roles second. Build the communication structure third. Then — and only then — write the business plan.
The partnership is the infrastructure. The business is built on top of it. If the infrastructure is solid, the business can withstand anything. If it isn’t, the business is one stressful quarter away from a fight that nobody wins.
The Financial Agreement
Money destroys partnerships that survive everything else. Adam and I addressed the financial structure before we built anything.
Equal partnership. We structured the partnership so both of us had meaningful stake, meaningful risk, and meaningful voice. The specifics of the equity split matter less than the principle: both partners need to feel they have equal investment in the outcome.
Salary parity: We paid ourselves the same amount. When Vulpine couldn’t pay either of us, neither was paid. When it could pay one salary, we split it. When it could pay two, we were paid equally. Financial parity eliminated the most common source of partnership resentment: “I’m working harder and being paid less.”
Expense transparency: Every business expense over EUR 100 required both partners’ knowledge (not approval — knowledge). Under EUR 100, either partner could spend without discussion. This simple threshold prevented the micromanagement of small purchases while ensuring large expenses were jointly understood.
Exit provisions: We defined the exit terms before we needed them. What happens if one partner wants to leave? What happens if both want to sell? What happens if we disagree about selling? The terms were documented in our partnership agreement and never changed. When the exit actually happened, there was no negotiation between partners — the terms were already set.
The financial structure wasn’t exciting. It was boring, detailed, and comprehensive. It was also the reason that four years of building together ended with both partners financially satisfied and personally intact.
The Advice I Give Now
When founders at Startup Burgenland asked me about co-founders, I gave the same advice every time:
Don’t partner with your friend. Partner with someone whose skills complement yours and whose values align with yours. Friendship is a bonus, not a qualification. Some of the worst partnership failures I’ve witnessed were between close friends who assumed that friendship would carry them through business disagreements. It didn’t.
Test before committing. Before formalizing a partnership, do a project together. A small one. A weekend build. A one-month experiment. See how you handle disagreement. See how you handle stress. See how you handle the mundane, daily reality of working alongside someone for hours. The test reveals more in one month than conversation reveals in a year.
Write everything down. Roles. Equity. Salary. Decision authority. Exit provisions. Communication expectations. Every element of the partnership that matters should exist in a document, not in an understanding. Understandings shift. Documents don’t.
Schedule the difficult conversations. The monthly health check isn’t optional. The quarterly financial review isn’t optional. The annual “are we still aligned?” conversation isn’t optional. These conversations feel redundant when things are going well. They’re essential because they prevent things from going badly.
Adam and I built well together because we’d built the partnership first.
