Adam Wilber lives in Florida. I live in Graz, Austria. We’re separated by an ocean, six time zones, different native languages, and fundamentally different working styles. He’s a high-energy creative who works in bursts of intense inspiration. I’m a systematic operator who works in steady, planned blocks. On paper, this partnership shouldn’t have worked.
It worked spectacularly. Over four years, we built Vulpine Creations into a twelve-product company with a 4.9-star rating, shipped to over fifty countries, and eventually exited by selling the product rights and inventory to respected magic companies. We never had a major disagreement. We never questioned the partnership. We never wished we’d gone solo.
When founders ask me about partnerships, they usually ask “how do you find the right partner?” That’s the wrong question. The right question is “how do you build the right partnership?” Because Adam and I didn’t find a perfect partnership. We built one, through specific practices and principles that any two people can implement.
The Foundation: Complementary Skills, Not Shared Skills
The most important structural element of our partnership was that our skills almost perfectly complemented each other with minimal overlap.
Adam brought: creative product design, magic performance expertise, visual aesthetics, the ability to see potential in ordinary objects, and deep credibility in the magic community through thirty-five-plus years of professional performing experience.
I brought: business operations, manufacturing management, logistics, marketing strategy, financial planning, and the systematic approach to execution that turns ideas into shipped products. I wrote about the early days of building Vulpine from a home office during lockdown — the partnership was tested by circumstances before it was tested by business challenges.
The overlap was thin: we both understood product quality, and we both cared deeply about customer experience. That shared value was the glue. Everything else was division of labor.
This complementarity eliminated most sources of partnership conflict. We never argued about how to do something because each function clearly belonged to one person. Adam never questioned my operational decisions. I never questioned his creative decisions. Respect for each other’s domain was built into the structure.
If you’re considering a partnership, map your skills against your potential partner’s. If you see significant overlap, proceed carefully — overlapping skills create territory disputes. If you see complementarity with a shared value system, that’s the foundation of a strong partnership.
The Operating Agreement: Clear Before It’s Needed
Before we shipped a single product, we established five operating principles. Not a formal legal agreement (though we had one of those too) — a behavioral agreement about how we’d work together.
Principle 1: Domain authority. In your domain, your decision is final. Adam has final say on product design, performance routines, and creative direction. I have final say on operations, pricing, and business strategy. This eliminated the committee-decision dynamic that slows most partnerships to a crawl.
Principle 2: One-sentence updates. Every weekday, we exchanged one-sentence updates via text: “Working on Product 8 prototype, testing materials.” “Shipped 40 units, set up new manufacturer call for Thursday.” These micro-updates maintained awareness without requiring meetings.
Principle 3: Weekly video call. One call per week, thirty minutes maximum. Agenda: what happened, what’s next, any decisions needed. No agenda, no call — we’d skip weeks where nothing required discussion. This prevented the meeting bloat that plagues most partnerships.
Principle 4: Disagreement protocol. When we disagreed (rare, but it happened), we had a rule: the person closer to the customer decides. If it’s a product design question, Adam decides because he’s closer to how magicians will use it. If it’s a pricing question, I decide because I’m closer to the purchasing data. This eliminated stalemates.
Principle 5: Either can call a Kill or Commit. Either of us could trigger a Kill or Commit review on any project or decision at any time, and the other would engage honestly without taking it personally. This kept zombie ideas from persisting.
These five principles were written on a shared document that we both referenced occasionally in the first year and barely needed afterward — because the principles had become habits.
The Time Zone Advantage
Six time zones of separation sounds like a problem. It was actually an advantage.
When I finished my workday in Graz, Adam’s day was just beginning in Florida. This created a natural handoff: I’d work on something during my day, send it to Adam at the end of mine, and he’d pick it up at the beginning of his. The result was a business that operated across fifteen to sixteen hours per day without either of us working more than eight.
Product photography would be done by Adam during his afternoon, sent to me overnight, and I’d have it uploaded and integrated into the sales page by the time he woke up. Manufacturing updates would come from European suppliers during my morning, and I’d have decisions ready for Adam to review when he started his day.
The time zone forced us into asynchronous communication, which turned out to be far more efficient than synchronous communication for a two-person operation. We made decisions via text messages, shared documents, and short voice memos. The thirty-minute weekly call was for alignment, not for operational work.
This experience convinced me that partnerships don’t require co-location or even time zone overlap. What they require is clear communication protocols, trust in each other’s domain authority, and enough shared context to make asynchronous decisions.
Trust as an Operating System
The deepest element of the partnership — harder to describe but impossible to overstate — was trust. Not blind trust. Earned trust, built incrementally through consistent behavior over years.
Trust manifested in specific ways:
- I trusted Adam to design products that met our quality standards without me reviewing every detail. He earned this by consistently delivering products that exceeded my expectations.
- Adam trusted me to manage finances honestly and strategically without him auditing every transaction. I earned this by providing transparent monthly financial reports and making conservative financial decisions.
- We trusted each other to represent the brand publicly. Neither of us needed the other’s approval before posting content, responding to customer inquiries, or making commitments on behalf of the company.
- We trusted each other’s judgment enough to accept decisions we disagreed with. When Adam wanted to pursue a product direction I was skeptical about, I supported it. When I wanted to price something higher than Adam was comfortable with, he supported it. In both cases, the domain authority principle and mutual trust made this possible.
Trust isn’t a feeling. It’s a track record. It’s built through hundreds of small moments where someone does what they said they’d do. Over four years and twelve products, Adam and I built a track record that made the partnership feel effortless — but it was effortful in the beginning. The trust was constructed, not given.
When to End a Good Partnership
Exiting Vulpine in 2024 ended a partnership that was still working well. We didn’t exit because the partnership was broken. We exited because the business had reached a stage where neither of us wanted what the next phase required.
Knowing when to end a partnership is as important as knowing how to build one. We had three options: scale up (bigger team, more products, more complexity), stay the same (maintain current size and output), or exit (sell and move on).
Scaling up would require skills and time commitments neither of us wanted to make. Staying the same felt like stagnation. Exiting preserved the brand, rewarded our work, and freed us for new things.
We discussed these options openly, without drama, using the same direct communication style that had served us throughout the partnership. The conversation took about two weeks. The decision was mutual. The execution was collaborative.
Not every good partnership needs to last forever. Some partnerships are designed for a specific mission, and when the mission is complete, ending the partnership isn’t failure — it’s completion.
What magic taught me about business includes this: performances end. The best ones end at the right moment — before the audience loses interest, before the energy fades, before the magic becomes routine. Vulpine’s partnership ended at the right moment.
Key takeaways:
- Partner with someone whose skills complement yours, not duplicate them — overlapping skills create territory disputes; complementary skills create capacity.
- Establish operating principles before shipping anything: domain authority, communication cadence, disagreement protocol — behavioral agreements matter more than legal ones.
- Use asynchronous communication as a feature, not a bug — time zone differences can actually increase a partnership’s daily operating capacity.
- Build trust through consistent behavior over hundreds of small moments — trust is a track record, not a feeling, and it’s constructed incrementally.
- Know when to end well — a partnership that was great for one phase of business isn’t obligated to continue into a phase that requires different things.
