So the Client's Cousin 'Does AV': How to Protect Your Project Without Burning the Relationship

You've been through the discovery call, scoped the project, written the proposal, and gotten the signed contract. Then, somewhere around week two, a new name shows up in the email thread. The client's brother-in-law. A friend who "set up the system at their lake house." A nephew who "works in IT." And suddenly you're fielding questions about why you didn't spec a different brand, whether the cable runs really need to be that long, and whether the whole thing could just be done with a few smart plugs and a YouTube tutorial.

This is one of the most common — and most frustrating — dynamics in client-facing AV work. And how you handle it will say a lot about whether you get referrals from this client or a headache that follows you for months.

Why This Keeps Happening

Before you get defensive, it helps to understand what's actually going on. Clients bring in their tech-adjacent friends and family for a few reasons, and almost none of them are malicious.

First, AV work is expensive and often feels abstract to people who aren't in the industry. When someone they trust says "I know a little about this stuff," it feels like a safety net. Second, they may not fully understand the difference between consumer tech and professional AV — and honestly, why would they? The marketing language overlaps constantly. And third, they want to feel like an informed buyer, not just someone signing checks.

Understanding this doesn't mean you have to accept interference in your scope of work. But it does mean you'll handle it better if you lead with empathy rather than irritation.

Set the Stage Early — Before There's a Problem

The most effective way to handle the cousin situation is to make the project structure clear before anyone shows up in the thread uninvited. Your contract and your kickoff conversation should both establish, plainly, how decisions get made and who the point of contact is.

This doesn't need to be confrontational. Something like: "Throughout the project, I'll be coordinating directly with you as the decision-maker. If you want to loop in anyone else for input, just give me a heads up so we can manage the conversation in a way that keeps things on schedule."

That language does a few things. It names you as the professional in charge of the process. It leaves room for the client to involve others if they want to. And it frames any outside involvement as something that needs to be coordinated — not something that just happens to you.

When the Interference Has Already Started: Scripts That Actually Work

Let's say you're already in it. The cousin has opinions, the client is forwarding emails, and you're getting questions you didn't agree to answer. Here's how to redirect without going sideways.

When someone challenges your spec: Avoid getting into a technical debate in an email chain. Instead, try: "That's a fair question — happy to walk through the reasoning. I'd suggest we set up a quick call so I can explain the tradeoffs in context rather than back-and-forth over email. [Client name], does that work for you?"

This moves the conversation to a format you control, keeps the client in the center of it, and signals that you're not dismissing the question — you're just managing it professionally.

When someone recommends a different product or approach: "I've looked at that option. The reason I went a different direction is [specific reason tied to the client's stated goals]. If you'd like, I can put together a quick comparison so [client name] can see both approaches side by side."

This works because it's confident without being dismissive, and it keeps the client — not the cousin — as the decision-maker.

When someone tries to change the scope mid-project: "I want to make sure we get this right. Any changes to what we agreed on in the contract will affect the timeline and budget, so let me put together a change order so we're all clear on what that looks like before we move forward."

Change order language is your best friend here. It makes the cost of scope creep visible without making it personal.

The Boundaries Conversation: When You Have to Be Direct

Sometimes the diplomatic approach isn't enough, and you need to have a clearer conversation with your actual client — not the cousin. This is a conversation you have privately, and it sounds something like this:

"I want to make sure this project goes smoothly for you, and I've noticed we're getting a lot of input from different directions. I'm totally fine with you involving people you trust — but for the project to stay on track, I need one person on your side making the final calls. Can we agree that's you?"

Most clients, when it's put this way, will get it. They hired you. They want results. They don't want the project to become a committee.

Protecting Your Standards Without Being Condescending

Here's the balance you're walking: you need to protect your professional standards and your scope of work, but you can't make the client feel stupid for trusting someone they care about. The moment you come across as dismissive of the cousin's input, you risk the client getting defensive — and now you've got two people working against you instead of one.

Keep your language outcome-focused. You're not arguing about who knows more about AV. You're talking about what will and won't work in this specific install, for this specific client, in this specific room. That's your domain, and framing it that way keeps the conversation professional rather than personal.

The Longer Game

Handle this well, and you actually come out ahead. Clients who watch you navigate a difficult dynamic calmly and professionally — without throwing anyone under the bus — tend to trust you more, not less. They've seen how you handle pressure. They know you're not just in it for easy jobs.

And if the cousin ever actually does have a useful insight? Acknowledge it. Give credit where it's due. Nothing builds goodwill faster than a professional who's confident enough to say "that's actually a good point." You're not competing with the cousin. You're doing the job.