# Your growth problem is probably an ownership problem *Why the friction throttling growth usually lives between your teams, not inside any one of them.* **TLDR:** If you've watched a growth motion stall even though every team touching it is doing good work, and you couldn't figure out where the leak actually is, this article has the answer. You'll learn why the friction usually lives in the seam between two teams rather than inside either one, how we traced our referral pipeline's leak to an ownership gap between marketing and partnerships, and how to find and close the same blind spot in your own business. **Authors:** [Vadim Zolotokrylin](/people/vadim-zolotokrylin) --- We had a growth motion that should have worked. Referral partners, the people who sit close to founders and can introduce us, are the highest-converting way we reach the founders we build with. We knew that. We had the partners, the tooling, and the intent. It still leaked. Introductions stalled, follow-ups went cold, and no dashboard told us why. The leak was not inside any one team. It was in the space between two of them. ## The lever is rarely where you point the flashlight There is a pattern we keep seeing, in our own operation and in the founders we work with. The friction holding growth back is rarely inside the function you are staring at. It sits in the seam between two functions, where the work is real but ownership is not. When a number is not moving, the instinct is to look harder at the team closest to it. Sales is not closing, so you inspect sales. Referrals are not landing, so you inspect the partnerships effort. But when a motion crosses two teams, the problem is usually not inside either one. It is in the handoff nobody owns. ## Our blind spot was between marketing and partnerships Here is where ours lived. Marketing ran cold outbound: the sequences, the LinkedIn tooling, the lead scoring. Partnerships owned the relationships: the trust, the conversations, the deals. Both teams were good at their half. The referral partner motion belonged to neither. Sourcing a partner looked like outbound, so it drifted toward marketing. Working the relationship looked like partnerships, so it drifted there. Each team assumed the other had the parts it was not doing. The candidate who replied to a campaign, the introduction that needed a sender the recipient would recognize, the partner who went quiet after month one: all of them fell into the gap. We had even written the definition of an ideal referral partner in two places, once in each team's docs, each version subtly different. Two sources of truth is another way of saying none. ## The fix was ownership, not a tactic We did not fix this with a better sequence or a new template. We moved ownership. Partnerships now owns the referral motion end to end: who counts as a partner, how we find them, how we work them, and what a result means. Marketing runs cold outbound as one channel that feeds it, using the same tooling it already runs for founders. Then we made the motion legible: one funnel with named stages and a clear gate between each, so anyone, including an AI agent, can see where a partner is and what has to be true to move them forward. One definition of a partner, in one place, that every other document points to. Same offer. Same partners. A pipeline that finally moves, because one team owns the whole of it instead of two teams owning halves. This is the same lesson we learned about [introductions over cold outreach](/insights/referrals-close-cold-outreach-doesnt): the leverage was never in the tactic. It was in getting the structure right. ## How to find your own seam You can look for this in your own business. The blind spots have symptoms: 1. Work that every team touches and no team owns: onboarding, handoffs, "the website," the referral motion. 1. A metric two teams both influence and neither is accountable for. 1. A definition that lives in more than one place, worded differently in each. 1. Handoffs that go cold, where each side assumes the other picked it up. When you find one, resist the urge to add a process or a meeting on top. Assign the whole motion to one owner, make the other side a clearly scoped input, and write the shared definition down once, where everyone can point to it. The reason this is hard to see from the inside is that everyone is doing their job. No one is failing. The failure is structural, and structure is exactly what no single person is watching while they execute. That is why the lever hides in the seam, and why moving it works.