Client Red Flags That Kill Agency Margins (And Look Innocent at First)
The clients who destroy your margins don't start out difficult. They start out enthusiastic. Here's what to watch for in the first 30 days before the pattern sets in.
01. How Margin-Killing Clients Are Different From Difficult Clients
Difficult clients are easy to identify. They're demanding, impatient, rude, or unreasonable in ways that are immediately obvious. Margin-killing clients are harder to spot because they're often genuinely nice people who pay on time and express appreciation for your work. The difference isn't in how they treat you. It's in the specific patterns that consume hours without generating revenue. A client who is brusque but has clear briefs, approves quickly, and never expands scope is a more profitable client than a warm, enthusiastic client whose approvals take three rounds and whose definition of scope is always slightly larger than last month's. This is about patterns of working that systematically erode margin. Recognising them in the first 30 days gives you the chance to address them before they set expectations for the entire engagement.
"Margin-killing clients don't start out difficult. They start out enthusiastic. The difference isn't in how they treat you — it's in the specific patterns that consume hours without generating revenue."
02. Red Flag 1: The 'Quick Question' Pattern
The quick question isn't quick. It's a request for strategic input, creative direction, or detailed analysis framed as an afterthought that shouldn't require much time. 'Quick question — what do you think about our positioning for the enterprise segment?' is not a quick question. It's a consulting deliverable wearing casual clothes. In the first month of a client relationship, two or three quick questions feel like relationship-building. By month three, they've established a pattern where the client expects access to your team's thinking at any time, for any topic, without it counting against anything in the scope. What to watch for: messages that begin with 'quick question,' 'just wanted to ask,' or 'this might be silly but' followed by something that requires meaningful thought. Track the time you spend responding. If it's more than 30 minutes per week, you have an account where ad-hoc advisory work is being absorbed without billing. How to respond: address the first quick question directly, but note it: 'Happy to dig into this. If strategic questions like this become a regular part of our work, we should probably include a monthly strategy session in the scope so you get proper attention on them rather than ad hoc answers.'
03. Red Flag 2: Approval by Committee With No Named Decision-Maker
The approval chain red flag reveals itself in the first review cycle. You submit work. It comes back with feedback from three different people whose comments contradict each other. You're asked to accommodate all three perspectives. The revision isn't about improving the work — it's about navigating internal client politics that you're now managing for free. This pattern is particularly expensive because it multiplies revision rounds. Each round of contradictory feedback requires another round of work. A project estimated at two revision rounds becomes six. What to watch for: who sends the kickoff brief? If it's a team rather than a named individual, ask immediately: 'Who is the primary decision-maker we should address feedback to?' How to respond: 'We work best with a single point of contact who consolidates feedback before sending it to us. This keeps revision rounds clean and makes sure the direction is aligned before we go into production. Can we agree on who that person is?'
04. Red Flag 3: The Scope Expander Who Frames Everything as Included
The scope expander's tell is a specific linguistic pattern: 'As part of this project, could you also...' or 'I assumed that would be covered under...' or 'That seems like a natural extension of what we're already doing.' Each of these phrases is trying to add scope without acknowledging that scope is being added. The scope expander isn't necessarily acting in bad faith — many genuinely believe the additions are reasonable extensions of the original agreement. The problem is that a series of reasonable extensions can double the scope of a project without the client perceiving any escalation. What to watch for: any request in the first month that references work not specifically described in the proposal or brief. The trigger isn't the size of the request — it's the framing. How to respond: 'That's not in the current scope, but we can handle it a few ways. We can add it as a small change order, we can swap it for something else in the current scope, or we can schedule it for phase two. Which works best?' This response makes the scope issue explicit without accusation.
05. Red Flag 4: The Moving Brief
The moving brief is a scope problem that starts upstream. The client submits a brief. Your team starts work. The client revises the brief — not because the work triggered new thinking (which is normal), but because the original brief wasn't properly considered. The first brief was provisional, and your work against it was wasted. Clients who submit moving briefs often do it repeatedly throughout an engagement. The cost lands on your team in the form of work that gets discarded. What to watch for: a brief that arrives without clear answers to: who is the target audience, what is the specific objective, and how will success be measured. Incomplete answers predict brief revision. How to respond: before starting any significant work, require a brief sign-off: 'Before we go into production, I want to make sure we're aligned on the brief. Can you confirm the target audience is X, the objective is Y, and success looks like Z?' Getting this confirmation in writing creates a reference point when the brief starts moving.
06. Red Flag 5: Communication That Requires Immediate Response
The communication urgency pattern is a boundary issue that compounds over time. If a client sends messages at 7pm and expects morning responses by 8am, they've established an implicit expectation of near-constant availability. Meeting this expectation once creates the precedent. The cost isn't just the time spent on out-of-hours messages. It's the context-switching cost for the team members who feel they need to check messages during non-work hours. What to watch for: messages sent outside business hours in the first two weeks. Not because you need to respond to them urgently — but because the timing signals the client's expectations. How to respond: establish response time expectations early, explicitly, and in writing: 'Our team responds to messages within 24 hours on business days. For urgent items, [name] is the point of contact.' Setting this in the onboarding document, before it's tested, is much easier than correcting the expectation after it's established.
07. Red Flag 6: The Comparison Threat
'Our previous agency did this for half the price' or 'I've seen other agencies include this without charging extra' are margin pressure tactics that usually appear when you first try to scope a change order or decline an out-of-scope request. They're designed to make you feel that your price is the problem rather than the scope. The comparison threat is worth noting not because you should immediately capitulate — you shouldn't — but because it signals a client who manages the relationship through price pressure rather than collaborative problem-solving. That pattern doesn't improve over time. How to respond: 'I understand you've seen different pricing structures. We can adjust scope to reach a price that works for both of us — what would you remove from the deliverable list to reduce the investment?' This re-frames the conversation from price to value, and puts the scope decision back with the client.
08. Red Flag 7: The Free Round
The free round is a specific revision tactic: the client expresses dissatisfaction with the direction of a deliverable and asks for a complete restart. Not an iteration on the existing work — a fresh start in a different direction. Then frames this as a revision round rather than new work. A restart is not a revision. A revision improves and refines an existing direction. A restart discards it and begins again. The labour cost is equivalent to producing the original deliverable a second time. Treating it as a revision round means you've effectively done the work twice for the price of once. What to watch for: feedback that says 'we'd like to go in a different direction' rather than 'here are the specific changes we need.' Direction change = potential restart = should not consume a revision round.
09. What To Do When You See These Patterns
The instinct when you see a red flag pattern in the first month is to wait and see if it develops. This instinct is wrong. Patterns that establish themselves in month one become expectations in month two and entitlements in month three. The window to address them without conflict is exactly when you first notice them. The conversation doesn't need to be confrontational. In most cases, the most effective approach is a simple, neutral acknowledgment: 'I want to make sure we're set up to work well together long-term. I noticed [specific pattern]. Let's agree on [specific expectation] so we're both clear going forward.' Most clients respond to this well because it's framed as a setup conversation, not a complaint.
10. When the Pattern Is Already Established
If you're reading this and recognising patterns in an existing client relationship rather than a new one, the path forward is harder but not impossible. The key is to re-frame the conversation as a 'working together' discussion rather than a 'you've been doing something wrong' accusation. 'As we head into month X, I want to make sure we're set up for a sustainable engagement. I've noticed that [specific pattern] has been adding scope beyond what we've allocated. Going forward, I'd like to [specific change]. Does that work for you?' This approach acknowledges the history without assigning blame and proposes a clear change going forward. Clients who respond poorly to this conversation are telling you something important about whether the relationship is worth continuing.
Track which clients are actually profitable.
Know the effective hourly rate by client before the pattern sets in.
