title: "The Partnership Question: How Marijan and I Navigate Disagreement" date: 2025-11-27 author: David Sanker
There's a particular kind of silence that falls between two people who disagree about something important. Not hostile silence — the other kind. The kind where both of you are still thinking, still respecting each other enough not to fill the air with noise.
Marijan and I have sat in that silence more than once.
I've spent a good portion of my life at intersections — law and code, structure and creativity, the certain and the possible. So when I started building AI systems for law firms, it felt less like a career pivot and more like two rivers finally joining. But rivers don't always flow smoothly together. Sometimes they push against each other before finding a shared current.
That's the honest story of our partnership.
How We Found Each Other
We met at a tech conference — the kind where everyone's simultaneously exhausted and overstimulated. Marijan was presenting on machine learning applications. I was in the audience with a legal pad and too much coffee, scribbling notes in the margins.
The conversation that started over bad conference coffee kept going. We had the same itch: legal practice was drowning in paperwork that machines could handle, if only someone bothered to build the right tools. He brought deep expertise in algorithmic systems. I brought years of reading contracts until my eyes blurred and the particular frustration of knowing exactly what needed to change.
What I didn't fully appreciate at the time was that our different starting points — his engineering mind, my legal one — would be both our greatest asset and the source of nearly every disagreement we'd have.
The First Real Test
We were building a contract automation tool for small law practices. The kind of firms that can't afford enterprise software but are spending hours on work that should take minutes.
The disagreement that crystallized everything for us was about the user interface.
I wanted simplicity. Clean, clear, accessible to a solo practitioner who didn't go to law school to become a software user. Marijan wanted something more sophisticated — real-time analytics, dynamic data visualization, the kind of interface that would make a data scientist feel at home.
Neither of us was wrong. That was the problem.
I remember the specific evening we reached the impasse. We'd been at it for a while, and the conversation had that slightly frayed quality where you're no longer really listening, just waiting for your turn to make the same point again. I caught myself doing it. I stopped.
What I said instead was something like: "Tell me why this matters to you."
Not a negotiating tactic. Genuine curiosity. Because somewhere in the middle of defending my position, I'd stopped being curious about his.
What came out of that conversation wasn't a compromise — compromise usually means both people getting less than they wanted. What came out was a third option neither of us had considered: a toggle feature. Basic mode and advanced mode, letting the user decide. The solo practitioner could stay in clean, simple view. The tech-forward firm could dig into the analytics.
It was better than either of our original ideas. That's the part that still stays with me.
The Investor Decision
That UI disagreement was a warm-up, as it turned out.
A few months later, a potential investor showed serious interest — the kind of interest that changes the shape of a conversation. The condition attached to that interest was a pivot in our business model. Not a small adjustment. A meaningful departure from what we'd set out to build.
Marijan and I sat with it differently. He was drawn to the financial stability, the runway it would provide. I kept circling back to what we'd originally promised ourselves and, implicitly, the users we'd designed this for. I wasn't immune to the appeal of the investment — I have a family, and I understand what security means. But something felt off about the trade.
We reached a genuine impasse. The kind where pushing harder would have done damage.
So we did something counterintuitive: we stopped talking about it for a few days. Not avoiding it — deliberately stepping back. We each spent time separately imagining the two futures. What did the business look like in five years if we took the money? What did it look like if we didn't?
When we came back together, we'd arrived at the same place independently. Our original mission wasn't negotiable. The investor wasn't the right fit.
That shared conclusion — reached separately, confirmed together — did something for our partnership that no amount of smooth agreement could have. It showed us we were actually aligned on what mattered, not just on the surface, but underneath.
What I've Learned About Disagreement
I work with people now who are navigating their own partnerships — business, creative, sometimes personal. And I see the same pattern repeat: disagreement gets treated as a warning sign, evidence that the partnership is fragile or fundamentally misaligned.
My experience is almost the opposite.
You don't learn what someone is made of when you agree. You learn it when you disagree and they stay in the room. When they're still curious about your perspective even while holding their own. When they can say "tell me more" instead of "yes, but."
A few things that have actually worked for us:
- Name the disagreement early. Don't let it calcify into a position. The longer you wait, the more identity gets wrapped up in being right.
- Separate the person from the idea. Marijan's interface idea wasn't Marijan. I could push back on it without pushing back on him.
- Give each other space to think. The investor decision taught us that sometimes the most productive thing is to stop talking and go think separately.
- Revisit your shared values when you're stuck. Not as a rhetorical move, but genuinely. What did we build this for? Who are we building it for?
- Welcome a third voice occasionally. An outside perspective — a mentor, an advisor — can reframe a stalemate that's gone circular.
Trust isn't something you establish once. It's something you keep demonstrating, especially under pressure.
An Invitation
I think about the partnerships in my own life — not just with Marijan, but with the mentors who shaped how I think, the clients who trusted me with decisions that mattered, my family watching me navigate all of this — and what strikes me is how little of the meaningful stuff happened in easy agreement.
The growth lived in the friction. Handled with enough care, friction is just unpolished collaboration.
So I'll leave you with this: think about a partnership in your own life — business, creative, personal — where disagreement has been sitting between you. Is it possible that the silence isn't a sign of damage, but an invitation to go a layer deeper?
What might you find there if you stayed curious instead of defensive?
FAQ
Q: How can disagreements in business partnerships lead to innovation? A: Disagreements force you to examine your assumptions. When Marijan and I couldn't agree on the interface direction, neither of us was simply right — and that tension pushed us toward a toggle feature that served users better than either original idea would have. Synthesis, when you're genuinely open to it, tends to outperform consensus.
Q: What role does trust play in a business partnership? A: Trust is the thing that makes disagreement survivable. It doesn't arrive all at once — it builds through small moments of honesty and larger tests of integrity. The investor decision was one of those larger tests for us. When Marijan and I independently reached the same conclusion about protecting our original vision, that reinforced something between us that smoothly agreeable moments couldn't have.
Q: How can partners manage disagreements about business direction? A: Give yourselves permission to pause. When we were stuck on the investor question, stepping back to think separately — then reconvening — let us arrive at a decision that felt earned rather than forced. It also helps to distinguish between disagreements about tactics, which are usually negotiable, and disagreements about core values, which usually aren't.
AI Summary
Key facts: - Marijan and the author met at a tech conference and developed a shared vision for AI tools in legal practice - Their disagreement over a contract automation tool's interface led to a toggle feature combining simple and advanced modes - A potential investor's demand for a business model pivot was ultimately declined after both partners independently concluded it conflicted with their original mission
Related topics: business partnership, conflict resolution, AI in law, innovation through disagreement, communication in partnerships, trust building, decision making, product development strategy