---
title: "How to spot problematic clients before you write a proposal"
description: "Spot problematic clients before you write a proposal: run a short intake, score the red flags, and decide to decline, reprice, restructure or proceed."
canonical: "https://pr-102.preview.formlio.com/blog/spot-problematic-clients-before-proposal"
locale: "en"
type: "post"
date: "2025-09-22"
category: "How-To-Guides"
alternates:
  fr: "https://pr-102.preview.formlio.com/fr/blog/reperer-clients-problematiques-avant-proposition-commerciale.md"
---

# How to spot problematic clients before you write a proposal

![](https://cdn.formlio.com/content/614d00d06b0b1a354664a8523dbef4d4229fdca6-6144x3456.jpg)

Gut feel is a poor filter when the pipeline is thin and every brief looks like rent. A short intake, a simple score and a planned response catch the costly clients before you spend a weekend on their proposal.

THE SHORT ANSWER

## Screen every brief with a short scored intake before you quote

Vet the client before you write a word of the proposal. Run a short intake call, score what you hear across budget, decision makers, goals, respect for your process and payment terms, then pick a response: decline, reprice, restructure or proceed. A score keeps you honest when you badly want the work.

Many studios vet clients after the fact. The project slips, the feedback turns into a committee, the final invoice sits unpaid, and only then does someone say the signs were there from the first call. They usually were. The problem is that nobody wrote them down, and nobody decided in advance what they would do about them.

A proposal is expensive to write well. It takes research, a scope, a timeline, pricing and often a few hours of design. Spending that effort on a client who was never going to sign, or who will cost you more than they pay, is the most avoidable loss in a creative business. Vetting belongs before the proposal, because that is the last moment when walking away costs you nothing.

The method here has three steps. Start by running a short intake conversation built to surface specific signals. Then score what you heard against a simple rubric instead of trusting your mood that day. Finally, choose a response that matches the score. A middling score is rarely a reason to say no; it is usually a reason to write a different proposal.

[Forrester's State of Business Buying research](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024) found that 86% of B2B purchases stall during the buying process.

Even good clients are slow to buy, so a stall on its own is normal. A stall with no budget, no named approver and no clear goal is a pattern worth scoring.

**The signal areas to check on every intake**

- **Budget**: Is there a real range, and does the way they talk about money hold together from the start of the call to the end?
- **Decision makers**: Do you know who approves the work, who influences it, and whether you will ever speak to the person who signs?
- **Goals**: Can the client say what success looks like in their own words, beyond wanting something that looks better?
- **Respect for your process**: Do they accept your intake, your discovery step and your way of presenting work, or push to skip straight to a price and a mock-up?
- **Payment terms**: Are they comfortable with a deposit and staged payments, or do they resist paying anything before they see finished work?

**Why the approver question matters**

- **13** people are involved in the average B2B buying decision — Your contact is rarely the only person who decides. ([Forrester: The State Of Business Buying, 2024 (2024)](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024))
- **93%** of B2B buyers took part in a buying group rather than deciding alone — Forrester Buyers' Journey Survey. ([Forrester: What's the big deal about getting rid of MQLs? (2023)](https://www.forrester.com/blogs/saying-goodbye-to-mqls-whats-the-big-deal-about-getting-rid-of-mqls))

SPOT THE SIGNALS

## Ask these questions in the first conversation

The questions to ask a potential client before sending a proposal make each signal visible: what budget range they have set aside, who signs off and who else will review, what a good result looks like, why the deadline is fixed, and whether they have worked with a designer on this before. Score each answer as you go.

A red flag only helps if you can ask for it. Bad clients rarely announce themselves; they answer ordinary questions in revealing ways. The trick is to ask questions that leave room for the revealing answer, then write it down before you have time to talk yourself out of it.

The table below pairs each signal with the question that surfaces it and a weight. Weight matters because signals are not equal. A request for free spec work tells you far more about the relationship ahead than a tight deadline does. Score each signal from nothing (no concern) up to a heavy weight (a clear problem), and add the totals at the end of the call.

**The intake rubric: signal, question, weight**

| Signal | Question that surfaces it | Weight |
| --- | --- | --- |
| No budget | What range have you set aside for this, even roughly? | Heavy |
| Unnamed decision maker | Who signs off on the final design, and who else will review it? | Heavy |
| Spec or free-work request | How do you usually choose between studios? | Heavy |
| Unclear goals | After launch, what tells you this worked? | Medium |
| Past designers burned | Have you worked with anyone on this before? What happened? | Medium |
| Resistance to process | Here is how we run projects. Does that work on your side? | Medium |
| Rush with no reason | What is driving the date? | Light |

[Forrester's State of Business Buying research](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024) reports that, on average, 13 people within an organization are involved in the buying decision, with 89% of purchases involving more than a single department.

That is why the decision maker question deserves the extra weight. If your contact cannot name who signs, you are writing for an audience you have not met.

### Signals that look bad but are not

Some items on popular red-flag lists are noise. An NDA before the first call can simply mean the client needs to show you confidential files. A formal RFP often comes from a well-run organisation with a procurement rule, not from a bad client, even if it means more paperwork for you. A first-time buyer of design needs more guidance, which is a pricing question rather than a warning. An urgent deadline tied to a real launch or event is a constraint, not disrespect.

Score these at zero unless they come with something else: an NDA plus a refusal to share a budget, or an RFP with a scoring sheet that only weighs price. On their own, they describe the client's situation. The heavy signals describe how the client will treat you.

WORKED EXAMPLE

## Score a pair of briefs side by side to see the method in action

Take a pair of fictional brand identity briefs and run them through the same rubric. The intake notes look similar at first glance, yet the scores split clearly, and each score points to a different proposal: a standard proposal for the low scorer, and a restructured, protected proposal or a polite decline for the high scorer.

Illustrative example with fictional clients: both briefs ask for a brand identity for a small consumer brand. Each signal scores 0 (no concern) to 3 (clear problem). Heavy signals carry extra weight and can add up to 6 points each.

**Brief A, a coffee roaster.** On a 15-minute call, the founder gives a budget range, says she and her co-founder sign off together, and describes success as getting stocked by independent grocers. The launch date is tied to a trade fair. She worked with a freelancer before, who moved abroad. She accepts the deposit and the discovery step without fuss.

**Brief B, a skincare start-up.** The marketing manager will not share a budget ("just tell us what it costs"), says the board will review "at some point", and asks for initial concepts before signing anything so they can compare studios. Success is described as "something high-end". The previous agency "didn't get it". The deadline is in three weeks, with no reason given.

**Illustrative example: the briefs scored**

| Signal | Brief A score | Brief B score | Note on Brief B |
| --- | --- | --- | --- |
| No budget (heavy) | 0 | 6 | Refused any range |
| Unnamed decision maker (heavy) | 0 | 4 | Board reviews, timing unknown |
| Spec or free work (heavy) | 0 | 6 | Wants concepts before signing |
| Unclear goals | 0 | 2 | Goal is a feeling, not an outcome |
| Past designers burned | 0 | 2 | Blames the last agency |
| Resistance to process | 0 | 2 | Wants to skip discovery |
| Rush with no reason | 0 | 2 | Tight date, no driver |
| Total | 0 | 24 | Decline or restructure |

Illustrative score bands for this example: 0 to 5 means proceed with your standard proposal. 6 to 11 means proceed with protections. 12 to 17 means reprice or restructure, for example by selling a paid discovery phase first. 18 and above means decline politely.

Brief A gets a normal proposal. Brief B scores well into the decline band. If the studio wants to keep the door open, the honest offer is a paid discovery phase with a named approver from the board, no free concepts, and a full deposit before any work starts. If the client refuses that, the score was right.

For Brief B, the vague approval chain should worry you more than the budget. A client who cannot say who decides is a client who may never decide.

April Dunford makes the point in [her guide to building a sales pitch](https://www.lennysnewsletter.com/p/how-to-build-a-killer-sales-pitch): companies that stuck with the status quo usually did not decide it was better than the other options.

RESPOND

## Match your response to the score instead of just saying yes or no

When vetting says proceed with caution, a proposal can prevent scope creep and other risks by turning each into a written protection: a named approver for an unclear decision chain, a revision cap for vague goals, a deposit for payment worries, and a change-order rate for scope that keeps growing. Decline only when the protections themselves would be refused.

A score is only useful if it changes what you send. The response options are simple, and you should decide which applies before you open your proposal template.

**Decline** when the heavy signals stack up and the client has already pushed back on a paid first step. Keep it short and kind. Thank them, say the project is not the right fit for how you work, and if you can, suggest another studio or freelancer who might suit them. Turning work down well protects your reputation; clients talk.

**Reprice** when the brief is fine but the budget is not. Offer tiered scope: a core option that fits the money they have, a recommended option, and a fuller option. That turns a budget fight into a choice the client controls.

**Restructure** when the goals are unclear. Sell a paid discovery phase first, with its own short proposal, and quote the main project when you both know what it is.

**Proceed with protections** when the client is good but a few signals worry you. The list below maps each worry to a line in the proposal.

**Turn each risk signal into a proposal protection**

- **Unclear decision maker: name the approver**: Write the approver's name and role into the proposal, and state that feedback reaches you through them. It stops surprise opinions from people you never met.
- **Vague goals: cap the revisions**: State how many rounds of revisions each phase includes and what counts as a new round. Vague goals produce endless rounds unless the cap is on the page.
- **Payment worries: take a deposit**: Ask for a deposit before work starts and tie later payments to milestones. A client who will not pay a deposit is telling you how the final invoice will go.
- **Growing scope: set a change-order rate**: List what is out of scope and the rate for extra work, so a new request becomes a quote rather than a favour.
- **Shaky relationship: add a termination clause**: Let either side end the project with reasonable notice, with payment due for work completed. It gives you a clean exit if the warning signs prove right.

Data from [IPSE's Freelancer Confidence Index survey](https://www.ipse.co.uk/articles/heres-how-clients-get-away-with-paying-freelancers-later), covering Q1 2024, found that 32% of freelancers had experienced a delay in payment from a client in the preceding 12 months.

Put these protections where the client will actually read them: next to the scope and the price, not buried in terms at the end. A deposit and milestone payments are far easier to agree before work starts than to chase once an invoice is late.

[McKinsey's research on how business customers buy](https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/do-you-really-understand-how-your-business-customers-buy) shows that, throughout the decision journey, almost 65 percent of B2B customers will come away from it frustrated by inconsistent experiences.

Vetting also continues after you send. A proposal that lives as a link rather than an attachment can tell you who opened it, whether it was forwarded, and where the reader spent time. Treat that behaviour as late intake data. A proposal that is never opened after a warm call says the urgency was not real. A forward to people you have never heard of says the approval chain is bigger than the client admitted. Long, repeated reads of the pricing section followed by silence usually mean a budget conversation is coming, and you can open it first.

![Open notebook with handwritten intake notes beside a laptop on a wooden desk](https://cdn.formlio.com/content/pexels-39219777)
*Score the intake notes before you open the proposal template.*

*Photo: Vitaly Gariev*

ALREADY IN TROUBLE

## Handle a problem client you have already accepted

To deal with problematic clients you have already accepted, name the exact problem first: scope creep, indecision, poor communication or crossed boundaries. Then fix it in writing, with a change order for new scope or a reset of the approval process. If nothing improves, exit professionally with notice, a handover and a refund of unearned fees.

Sometimes the warning signs slip through, or a good client changes after the work starts. You are not alone in a relationship that soured.

[Forrester's State of Business Buying research](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024) found that 81% of buyers express dissatisfaction with their chosen providers.

Unhappiness on the client side is common, which is why it pays to name the problem precisely rather than tolerate it.

**Reset or exit a difficult project**

1. **Name the specific problem**: Write down whether it is scope creep, indecision, slow communication or boundary issues. A named problem has a fix; a general bad feeling does not.
2. **Meet and reset in writing**: Talk it through on a call or in person, then confirm the agreed fix by email: who approves, how feedback arrives and how fast you each reply.
3. **Price new scope with a change order**: Any request outside the original scope gets a short written change order with its cost and timing, approved before you start the extra work.
4. **Exit if nothing improves**: Give notice under your termination clause, hand over files and documentation for the work paid so far, and refund any fees you have not yet earned.
5. **Update your rubric**: Look back at the intake notes. If a signal was there and you scored it low, raise its weight so the next brief like this gets caught.

The cleanest reset starts with a document the client can read and approve. If you send proposals as Formlio documents, a change order can be its own short Formlio proposal with the new scope, the price in an interactive quote and an agreement block, so the client approves with Slide-to-Approve or signs with an e-signature before work restarts. You get a notification when it is opened and when it is approved, and version history keeps a record of what changed and when. The same applies at the start: the scope, the named approver, the deposit and the revision cap sit in blocks the client reads, not in an attachment they skim.

## FAQ

### How do you deal with problematic clients?

Name the specific problem, fix it in writing with a reset of approvals or a change order, and exit professionally under your termination clause if nothing improves. Better still, score clients at intake so fewer problems get through.

### What questions should I ask a potential client before sending a proposal?

Ask what budget range they have set aside, who signs off and who else reviews, what success looks like after launch, what is driving the deadline, and whether they have worked with a designer on this before.

### Is a client who asks for an NDA or sends an RFP always a red flag?

No. NDAs often protect confidential files, and RFPs often come from organisations with procurement rules. Treat them as neutral unless they come with heavier signals, such as no budget or a request for free concepts.

### How do I politely turn down a client who is a bad fit?

Reply promptly, thank them for the conversation, say the project is not the right fit for how you work, and suggest another studio if you can. Keep it short and avoid listing their faults.

### How do I qualify a lead when I don't know their budget?

Offer ranges and watch the reaction, or propose a paid discovery phase that defines scope before the main quote. A client who refuses both a range and a paid first step is unlikely to accept your final price.

### What should a proposal include to prevent scope creep?

A clear deliverables list, explicit exclusions, a revision cap per phase, a change-order rate for extra work and a named approver. With Formlio, these sit in blocks next to an interactive quote the client approves inside the document.

### How do you prepare a proposal for a client?

Vet the client first, then write the proposal around their goals: the problem in their words, your approach, scope and exclusions, timeline, pricing options and terms, ending with a clear way to approve.

## Put scope, approvals and terms on the page

Build proposals with blocks for scope, pricing and approval, then see who opens and forwards them before you follow up.

[Start free](https://pr-102.preview.formlio.com/templates)

## Sources

1. [Forrester's State of Business Buying research](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024)
2. [Forrester: What's the big deal about getting rid of MQLs?](https://www.forrester.com/blogs/saying-goodbye-to-mqls-whats-the-big-deal-about-getting-rid-of-mqls)
3. [her guide to building a sales pitch](https://www.lennysnewsletter.com/p/how-to-build-a-killer-sales-pitch)
4. [IPSE's Freelancer Confidence Index survey](https://www.ipse.co.uk/articles/heres-how-clients-get-away-with-paying-freelancers-later)
5. [McKinsey's research on how business customers buy](https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/do-you-really-understand-how-your-business-customers-buy)

## Related

- [How to write an engaging proposal that builds client trust](https://pr-102.preview.formlio.com/blog/how-to-write-proposal-guide)
- [Four actionable strategies for proposals that win clients](https://pr-102.preview.formlio.com/blog/actionable-proposal-strategies-win-clients)
- [Why sales proposals fail and what top closers do differently](https://pr-102.preview.formlio.com/blog/why-sales-proposals-fail)
- [Managing client relationships in creative projects, from proposal to close](https://pr-102.preview.formlio.com/blog/manage-difficult-clients-creative-industry)
- [5 ways to present a proposal that builds client confidence](https://pr-102.preview.formlio.com/blog/present-proposal-client-confidence)
- [Your proposal is being ignored. Here's how to fix that](https://pr-102.preview.formlio.com/blog/how-to-fix-ignored-proposal)