The relationship-intelligence category has a credibility problem, and the category knows it.

We hear the same conversation in every Boomerang sales cycle. The CRO loves the idea. The CFO is in. Then the email gets forwarded to a board member or a senior advisor, and the response comes back:

"I'm not letting your sales team inside my network."

The objection is correct. It is the right objection. The reason it gets raised is that the first generation of relationship-intelligence tools earned it. The model was: install a Chrome extension, vacuum every contact and every relationship, score it, and serve it to anyone with a seat. The connectors at the other end of those relationships were never asked. They didn't know they were being mapped. They certainly didn't approve specific intro requests one at a time.

That model is incompatible with the people who actually have the relationships you need. Senior operators, board members, advisors, and high-trust customers have spent decades building those networks. They will not let a random AE inside them. They are right not to.

The next generation of this category has to be built on a different foundation. We're calling that foundation the Relationship Data Bill of Rights. Six principles, listed in order of importance. None of them are negotiable. We hold ourselves to them at Boomerang and we think the rest of the industry should too.

The six principles

1. The connector owns the data, not the company

The contacts in your CEO's LinkedIn graph belong to your CEO. The contacts in your board member's email belong to your board member. The relationships your customer champions have at peer companies belong to those customers.

A relationship tool's job is to make the connector's relationships more useful to the connector, with consent, on the connector's terms. Not to harvest them for the company's database.

Practically this means: if a connector leaves, their relationship data leaves with them. If a connector revokes permission, their data is purged. The default state is "the connector owns this." The exception state is "the connector explicitly opted in to share specific data for specific purposes."

This is a significantly weaker position than what most current tools take. We think it is the right one.

2. Connectors stay anonymous to reps unless they opt in

Your AE should not be able to scroll through your board member's LinkedIn graph. Your BDR should not be able to see that your CTO went to Stanford with the CISO at the target account.

The right design surfaces that a path exists and the strength of the path, without exposing the connector's identity. Something like:

"A board member has a 91/100 strength path to the CFO at Airbus."

The rep can request the intro. The connector then decides, on a per-ask basis, whether to reveal themselves and approve the introduction. The rep never sees the connector's underlying network unless the connector chooses to surface it.

This single design choice removes 80% of the legitimate objection from senior connectors. They are not exposed by being in the system. They are exposed only when they choose to be, on a specific ask.

3. Every ask is opt-in, every time

There is no such thing as a standing permission to be tapped for warm intros.

Some tools try to get around the consent problem by collecting blanket consent at signup: "I agree my contacts may be used for introductions." This is consent theater. It is not what the connector actually wants, and it falls apart the first time something goes wrong.

The right pattern is per-ask consent. Every single intro request is a fresh decision by the connector to approve or decline. Standing rules (deal size, cadence cap, channel) can pre-filter what reaches the connector, but the final approval is always the connector's, always per ask.

This is more friction for the company using the tool. It is the only sustainable model.

4. Connectors set the rules. The system enforces them.

A board member should be able to write down, in plain English:

"Only show me $500K+ in-flight deals. Email only. Maximum two asks per quarter. Exception: when the CEO is asking, anything goes."

A customer champion should be able to write down:

"Only after a positive QBR. Slack me, not email. Maximum three asks per quarter. Never ask me about competitors."

A platform that lets connectors author these rules and then enforces them invisibly (so the rep never sees a request that violates them) treats connectors as the senior adults they are. A platform that doesn't is asking the rep to remember dozens of unwritten preferences, which means the preferences will be violated, which means connectors will quietly disengage.

5. The connector hears back when something happens

If a connector makes an intro and never hears whether it produced a meeting, pipeline, or revenue, you have wasted their relationship capital twice. Once when they made the intro. Once when they didn't get closure.

The system has an obligation to close the loop, every time, with every connector. Not a quarterly digest. A specific, contextual message:

"Your intro to David Chen at Airbus turned into a meeting on Wednesday, a $750K opportunity, and last week, a signed contract. Thank you."

This is not a nice-to-have. It is what makes the next ask possible. The connectors who feel respected become more, not less, generous over time. The connectors who feel used become unavailable.

6. The data is portable and the connector can leave with it

If a senior advisor decides to leave your platform, they should be able to take their relationship graph with them. If a board member's company changes vendors, the board member's data should not be held hostage.

This is the standard the rest of SaaS has converged on (CSV exports, API access, GDPR-era data portability rights). The relationship-intelligence category has lagged because the data is the lock-in. We think that's the wrong trade. A platform that depends on locking in data is a platform that has stopped trying to earn the next month of usage.

Why this matters now

Three forces are about to make the relationship-data status quo untenable.

First, the population of "asked" people is getting more sophisticated. Senior operators, board members, and seasoned advisors have all seen the worst version of relationship tools. They know what bad looks like. They are now actively asking their portfolio companies what consent model their relationship tool uses. The companies that can answer the question well will keep the connectors. The ones that can't are losing them quietly.

Second, AI agents make this worse before it gets better. When the actor on the other end of a relationship ask is an AI agent rather than a human rep, every existing trust assumption gets re-examined. Connectors who tolerated being mapped by a friendly AE will not tolerate being mapped by an algorithm operating at agent scale. The category will either professionalize its data practices in the next 18 months or it will get regulated into doing so.

Third, the legal layer is moving. GDPR was the first wave. CCPA was the second. The CCPA-style state laws now in force across most of the US are increasingly being read to cover inferred relationship data, not just self-volunteered contact data. Tools that harvested relationship graphs in the 2018-2022 era are quietly removing functionality. Tools that didn't will have to.

This is the moment to set the standard, not the moment to wait for it to be set for you.

What buyers should ask before signing a relationship-intelligence contract

Five questions. Ask all five before signing. The vendor's answers will tell you everything.

1. Where does the relationship data come from, exactly? If "from public sources" is the only answer, that is incomplete. The interesting data (response cadence, deal context, relationship strength) is not public. Where is it coming from, with whose consent?
2. What does a connector see and control? Specifically, can a board member or advisor log in, see what is being inferred about their network, set their preferences, and revoke consent on a per-ask basis?
3. Are connectors anonymous to reps by default? If reps can browse the senior connector graph without opt-in, that is the wrong design.
4. What happens to a connector's data when they leave? If the answer is "it stays in the company's database forever," that is the wrong design.
5. What is the closure-loop mechanism? If the connector never hears back about what their intros produced, the program will degrade over 12 months whether the data quality is good or bad.

If a vendor can answer all five cleanly, they have built the right thing. If they hedge on any of them, they have built the 2018 version.

What this looks like at Boomerang

We hold ourselves to all six. Specifically:

• Super Connectors are anonymous to reps by default. Reps see "a board member has a path to this CFO," never the name, until the connector approves.
• Every ask is opt-in per ask. We do not collect blanket consent.
• Connectors set preferences (minimum deal size, channel, cadence, exceptions) and Rudy, our agent, enforces them. A rep cannot bypass them.
• Closure messages go out automatically every time an intro becomes a meeting, pipeline, or revenue.
• Connectors can leave with their data.

We think this should be the floor, not the ceiling. We expect the rest of the category to converge here in the next two years. We'd rather start the conversation now than have the regulators or the press start it for us.

If you are evaluating a relationship-intelligence vendor and theirs doesn't pass the five questions above, we are happy to compare notes. Either you'll pick us, or you'll pick a competitor, but either way you'll have asked the right questions, and the category gets better.

Curious how Boomerang's consent model works in practice? Read the manifesto or book a demo and we'll walk through it live.