Stop Asking Your Clients for Permission

There's a moment in almost every client relationship where you stop being the expert and start being an employee.

It doesn't happen all at once. It's one question. Then another. Then a habit. And by the time you notice it, the client is micromanaging you on decisions that should never have been theirs to make.

I had a guy on a recent Galadon Gold call - solid work, good campaigns, doing cold email setup for clients. He asked me something I don't get asked nearly enough: Am I seeking too much client permission? Is it too much to keep asking for approval when things aren't going the way I expected?

His specific situation: a beginner client, came through Facebook, wanted him to set up cold email infrastructure from scratch. The client wanted three email accounts running in Instantly, but only two are available on the free trial. To get three, he'd have to upgrade to the paid plan. So he went to ask the client for permission.

My first answer was: in this specific case, yes. You are spending her money. If there's a billing change, you tell her about it. That's just basic professional communication.

But then I told him the real thing.

Most of the time? Just do what you think is right. And when there is something to communicate - stop framing it as a question. Frame it as a recommendation. Because there's a version of that conversation that keeps you in the expert seat, and a version that kicks you out of it. And the difference is one sentence.

The Question vs. the Recommendation

Here's what a question sounds like:

"Should we upgrade to the paid plan to run three accounts?"

Here's what a recommendation sounds like:

"To run three accounts we need the paid plan. I recommend we start with two for now until we see the campaign working, then upgrade when we know what's converting. That way we're not spending more until we have data."

Same information. Completely different dynamic.

The question hands the decision to the client. The recommendation hands the decision to the expert - which is you.

She hired you because she doesn't know how many email accounts she needs. She doesn't know whether the paid plan is worth it at this stage. She doesn't know whether three inboxes outperforms two in a cold email campaign. That's the whole reason you're there. The second you ask her to decide, you've undermined the entire value proposition of the relationship.

I put it to him directly: who is she to tell you whether you need two emails or three emails? You're the one running the campaign. You should know which one is correct.

That landed. I could tell. Because it's not a harsh thing - it's just the truth about what the engagement is supposed to be.

How the Permission Trap Kills the Relationship

The permission-asking habit doesn't feel dangerous when it's happening. It feels polite. Professional, even. You've been trained - by corporate culture, by bad managers, by anxious first clients - to get sign-off before moving. CYA, check everything, don't make waves.

But here's what happens inside the client's head when you do this.

First question: they answer it, slightly surprised. Second question: they answer it again, slightly more aware. Third question: they start wondering why you don't just know. Fourth question: they start second-guessing the decisions you didn't ask about. And somewhere around the fifth or sixth time you've asked for permission on something that falls squarely within your domain of expertise, they've made a decision - consciously or not - that you're someone who needs to be managed.

Once that happens, you can't un-ring the bell. They start sending longer emails asking for updates. They ask to approve things before they go out. They start poking at your process. And three months later they cancel and tell you it "just wasn't the right fit." What happened is that you trained them to treat you like a junior employee, and eventually they found the relationship too high-maintenance.

The worst part is that most people think asking questions is a sign of respect for the client. It's not. It's a vote of no-confidence in yourself. Every permission-request is you saying, implicitly, I don't trust my own judgment enough to act on it. Clients hear that signal clearly, even when they can't articulate it.

What a Strong Recommendation Looks Like

The formula is straightforward: state what you're doing, state why, close it. Don't end with a question. If the client has a real objection, they'll raise it. But don't create a vacuum and ask them to fill it with a decision they're not qualified to make.

Compare these two versions of the same conversation:

Version A (question framing): "So I was thinking, we have the option of going to the paid plan which gives us three inboxes. What do you want to do?"

Version B (recommendation framing): "We're going to need the paid plan to run three inboxes. I recommend we go ahead - three accounts means more daily sending volume, faster data, and we're less exposed if one inbox hits a temporary deliverability issue. I'll set it up and send you a note when it's live."

Version B is a complete sentence of authority. You've told them what's happening, why it's the right call, and what they can expect next. There's no open-ended "what do you think?" at the end. The client's job is to flag if there's a real blocker - not to make the technical decision for you.

And here's the thing most people miss: clients prefer this. They don't want to become experts in cold email infrastructure. That's why they hired someone. When you show up with clear recommendations, you stop being a vendor they manage and start being an advisor they trust. That's the difference between a client who churns after 60 days and one who renews without you having to pitch them.

If you want a framework for how to structure these kinds of conversations from the first call, the Discovery Call Framework I put together covers how to set up authority positioning before the engagement even starts.

The One Exception: When You Do Need Permission

I want to be precise here, because there are cases where looping the client in isn't optional.

If you're spending their money - not platform subscription fees, but actual budget they've allocated - keep them informed. Not as a question, but as a heads-up: "We're allocating $X to this test, here's what we're expecting to learn."

If you're making a strategic pivot that changes the direction of the campaign in a fundamental way - switching target market, changing the core offer positioning, moving from cold email to LinkedIn outreach - give them context. That's not asking permission, it's managing a relationship professionally.

If you're doing anything that legally or contractually affects them - domain reputation, brand assets, data handling - loop them in.

Everything else? Make the call. That's what they hired you for.

The line is this: you don't ask clients their opinion on technical decisions inside your domain. You inform them of decisions that affect their business at a strategic level. The first is abdicating responsibility. The second is being a professional.

The Disguised Question (Worse Than Asking Directly)

There's a version of this habit that's worse than straightforward permission-asking. I see it constantly. It's the question you ask when you've already made the decision.

"What do you think about upgrading the plan?"

You already know the answer. You've already decided what should happen. But instead of just saying it, you dress it up as a question and hope they tell you to do what you were going to do anyway.

This is worse than asking for permission outright. Because now you're wasting their time and handing them the decision. And if they say the wrong thing - "let's wait on the upgrade" - you're stuck. You either push back (awkward, undermines the question you just asked) or you go along with the worse option (bad for results).

Just say what you're going to do. Let them react. The conversation is cleaner, the relationship is cleaner, and you don't put yourself in a position of waiting for the client to give you permission to do your own job.

How This Pattern Shows Up Across the Whole Relationship

I see this play out across every type of agency and consulting engagement, not just cold email setup.

There are consultants who run every email through client approval before it goes out. They frame it as being collaborative. What they're doing is transferring responsibility for results. If the campaign tanks, they can say "you approved it." If it works, the client gets the credit. It's a lose-lose setup disguised as communication hygiene.

There are cold email agencies that check in with clients on subject line variations, follow-up timing, inbox rotation schedules. Then they wonder why the client is treating them like an employee. They trained them to. They handed over the wheel, the client grabbed it, and now they can't get it back.

I've been on the other side of this too - as a client, as an investor, as someone who's written checks for services. When a vendor shows up asking me to make technical decisions I hired them specifically to handle, I lose confidence fast. Not because they asked, but because the ask signals that they don't know what they're doing. Or worse, that they're trying to shift accountability.

The best engagements I've had - on both sides - look the same way. The expert comes in, assesses the situation, tells you what's going to happen and why, executes, and reports back on what they found. The client's job is to give context, set objectives, and raise flags on things the expert can't see. Not to approve every micro-decision inside the expert's own domain.

If you're trying to build an agency that grows beyond just yourself, getting this dynamic right is foundational. The 7-Figure Agency Blueprint gets into the structural side of building a client operation that scales - but it starts with this kind of positioning work.

It Starts Before the Engagement

There's a sales dimension here I want to flag, because the permission-asking habit doesn't start after you sign the contract. It starts in the sales conversation.

When a prospect says "you're taking all the risk here, not me" - that's a test. They're watching to see how you respond. If you agree, or if you hedge, you've told them that your confidence in what you do is conditional. If you reframe it calmly - "we both take risk here, I'm putting my time and reputation on the line too, and I don't take on clients I don't think I can deliver for" - you've positioned yourself as a peer, not a vendor.

But the easiest way to avoid that test entirely is to never create the conditions for it. When you show up with clear recommendations, structured decisions, and no hedging on things inside your domain - the prospect reads confidence before they've even signed anything. They don't start poking at risk allocation because you've already telegraphed that you know exactly what you're doing.

The agencies that struggle most with client confidence are almost always the ones that showed up vague in the first conversation. They said "whatever you prefer" on decisions they should have owned. They asked what the client wanted to test instead of presenting a testing plan. They said "we can try a few different approaches and see what works" instead of "here's the approach and here's why it works."

Vagueness reads as uncertainty. Uncertainty reads as risk. And then you're in a conversation about why you deserve the contract instead of a conversation about what you're going to build together.

What This Changes

When I told the guy I was coaching to shift from questions to recommendations, he pushed back a little - not on the advice, but on what it meant about his positioning. If I just tell her what to do, doesn't that feel pushy?

No. It feels like expertise. There's a difference between being pushy and being clear.

Pushy is insisting on something in the face of a client's real objection. Clear is stating what you believe is right and why, and then giving the client room to respond. Recommendations are not ultimatums. They're professional direction. They say: I've thought about this, here's where I've landed, here's the reasoning, here's what we're going to do - tell me if there's something I'm missing.

That's it. That's the whole thing.

His specific recommendation to the client on the Instantly plan could have sounded like: "We need three inboxes to do this right. That means moving off the trial to the paid plan. I recommend we either upgrade now, or we start with two inboxes and add the third once we see early data. I'd go with Option A, but tell me if the timing on billing is an issue."

Notice the structure: here's what needs to happen, here's the choice between two good options, here's my recommendation, here's the opening for a real objection. The client isn't being asked to decide whether three inboxes is better than two - they're being asked whether now or later works better for the billing. That's a question they can answer. You've pre-qualified both options. You've done the thinking. You're just letting them weigh in on the one variable where their input is relevant.

That's how you give clients control without surrendering authority.

The Bottom Line

Clients hire you because you know more than they do. The moment you ask for permission on a decision inside your domain, you've told them they were wrong to believe that.

The fix isn't complicated. Audit the last five client communications you sent. Count how many times you ended with a question that you already knew the answer to. For each one, rewrite it as a recommendation. See how it reads. See how it feels.

It'll feel weird at first, like you're being presumptuous. That discomfort is exactly the feeling of expertise asserting itself. It's supposed to feel that way. You're not being rude - you're being the expert they paid for.

Stop asking for permission. Start giving recommendations. The client relationship you want is on the other side of that habit.

If you're building out cold email campaigns and want to get the lead sourcing and infrastructure right from the start, ScraperCity handles the B2B lead database side, and Instantly is what most of the people I coach are using for sending infrastructure. Get the foundation solid, then focus on the stuff that matters - positioning, offer, and not asking your client whether to push send.