You took the call. They seemed nice. The project sounded straightforward — rebrand, new site, maybe some SEO. You sent the proposal the same evening because you didn't want to lose the momentum.

Three weeks in, you're rewriting the scope for the fourth time. They've added their business partner to the thread who has "a completely different vision." You're eating hours you can't bill. And you're thinking: I knew something was off on that first call.

You did know. You just didn't have a system for acting on it.

The most expensive mistake isn't a bad project — it's a bad client

Most agency content focuses on what happens after you sign a client. The onboarding flow, the kickoff, the handoff. But the highest-leverage filter in your entire business sits upstream of all that: the discovery call.

A tight onboarding process can't save you from a client who was never going to be a good fit. It just makes the failure more organized.

The problem is that bad-fit clients don't show up wearing a sign. They show up enthusiastic. They compliment your portfolio. They say things like "we just need someone to take this off our plate." And because most freelancers and small agencies are optimizing for revenue, they hear what they want to hear.

What you need is a short list of concrete behavioral signals — things people do on a discovery call that predict pain downstream. Not vibes. Patterns.

Here are the five I've learned to watch for.

1. They can't tell you who makes the final decision

You ask: "Who's going to be reviewing and approving deliverables on your side?"

And you get some version of: "Well, I'll be the main point of contact, but my partner will want to weigh in, and our operations person has opinions too."

That's not a team. That's an approval swamp. Every deliverable will get pulled in three directions. Revisions will contradict each other. And you'll be the one triangulating between people who haven't aligned internally.

What to listen for: Hesitation when you ask who signs off. Multiple names without a clear hierarchy. "We'll figure that out once we get started."

If they can't tell you the decision-maker on a 30-minute call, they won't have one during the project either.

2. They've already burned through another provider

"We worked with someone before but it didn't go well" — fine. That happens. But press on it. Ask what specifically went wrong.

If every answer is about the other provider and none of it is reflective — "they didn't communicate," "they missed deadlines," "they just didn't get it" — you're hearing someone who externalizes every problem. You're about to become the next provider who "just didn't get it."

What to listen for: Zero ownership in how the last engagement failed. Vague grievances. The phrase "we've been burned before" used to justify unusual demands (upfront spec documents, daily check-ins, milestone payments held until they're "satisfied").

Good clients who've had bad experiences say: "Here's what went wrong, and here's what we're doing differently this time." Bad-fit clients just want you to promise it'll be different.

3. They negotiate the process before they understand it

You start explaining how you work — your phases, your timeline, your communication cadence — and before you're two sentences in, they're pushing back. "Can we skip the strategy phase?" "We don't really need a kickoff." "Can you just start on the design this week?"

This isn't someone who's efficient. This is someone who doesn't value the structure that protects both of you. And the moment something goes sideways, they'll blame the process they asked you to skip.

What to listen for: Requests to compress or skip early phases. Impatience with anything that isn't "the deliverable." Treating your process like overhead instead of infrastructure.

Clients who skip the process always end up needing it the most.

4. The scope is a moving target inside a single conversation

Watch what happens when you try to pin down what they actually need. You start the call talking about a website redesign. Ten minutes in, they mention an email funnel. By minute twenty, there's a mobile app on the table and "maybe some brand guidelines."

This isn't ambition. This is someone who hasn't done the internal work to know what they want. And they're going to use your engagement to figure it out — on your dime, on your timeline.

What to listen for: Scope that expands or shifts within the call itself. New deliverables introduced casually mid-sentence. "While we're at it" energy. A lack of prioritization when you ask what matters most.

If the project can't hold its shape for 30 minutes on a call, it won't hold its shape for 30 days in production.

5. They push for a price before there's a defined problem

"Just give me a ballpark" is the most dangerous sentence in freelancing.

When someone wants a number before they've answered your scoping questions, they're telling you that cost is their primary filter — not fit, not quality, not outcome. You're being evaluated as a line item, not a partner.

What to listen for: Price questions in the first five minutes. "What would something like this typically cost?" before they've explained what "this" is. Reluctance to go through your intake or scoping process because they "just want to know if it's in budget."

You can absolutely be transparent about pricing ranges. But if the entire energy of the call is oriented around cost before scope, you're going to be negotiating margin for the life of the project.

The framework

I run every discovery call through a quick mental scan before I send a proposal. Here's the version I've turned into a checklist:

┌─────────────────────────────────────────────────────┐
│         DISCOVERY CALL RED FLAG SCAN                │
│                                                     │
│  □ Decision-maker clarity                           │
│    Can they name ONE person who approves work?      │
│                                                     │
│  □ Past-provider accountability                     │
│    Do they own any part of previous failures?       │
│                                                     │
│  □ Process respect                                  │
│    Did they accept your workflow without resisting?  │
│                                                     │
│  □ Scope stability                                  │
│    Did the project definition hold for the call?    │
│                                                     │
│  □ Value-before-price orientation                   │
│    Did they explore scope before asking cost?       │
│                                                     │
│  ─────────────────────────────────────────────────  │
│  SCORING: 0-1 flags = green light                   │
│           2-3 flags = proceed with guardrails       │
│           4-5 flags = walk away or restructure      │
└─────────────────────────────────────────────────────┘

Two flags doesn't mean you decline. It means you add structure: tighter scope documentation, a paid discovery phase, milestone-gated payments, or a shorter initial engagement. Three or more, and you're taking on a project that will cost more in energy and rework than it pays in revenue.

The uncomfortable math

Turning down a bad-fit client feels expensive. It's not. A single misaligned engagement at a small agency doesn't just burn the hours on that project — it bleeds into everything else. Your other clients get slower responses. Your team gets demoralized. You stop doing business development because you're firefighting.

The discovery call is your cheapest filter. Use it like one.

I put together a printable version of the red flag scan plus a full discovery call question bank — the actual questions I use to surface these signals in real conversations. You can grab it free here: agencyonboardingos.com/checklist