Skip to content

GrowthLast updated 5 min readBy The PixelCrayons team

When an agency should turn a client down: the intake test we apply to our own enquiries

The short answer

An agency should decline work for fit, not for lack of people. We qualify every enquiry on five facts, record one of six outcomes, and give a reason with every no. Here is that test, the signals that should make an agency decline, and how to tell a fit problem from a capacity problem.

One enquiry splitting into two routes: a fit problem to decline or refer, and a capacity problem to staff

Most advice on turning clients down is about difficult personalities. The harder cases are polite clients with work you cannot do well, at a budget that cannot fund it, or at a time you cannot staff.

This post sets out the intake test we apply to our own enquiries, the six outcomes it can end in, and how an agency can use the same test to tell a fit problem from a capacity problem.

Fit or capacity: two different reasons to say no

An agency turns work away for one of two reasons, and they need opposite answers.

A fit problem means the work should not be done by you at all, so you decline or refer. A capacity problem means the work is right but the people are busy, so you find capacity. Treating one as the other is where agencies lose money.

Fit or capacity: telling the two apart
A polite client asks for work
  1. 1Is it work you deliver, inside your craft?
    NoA fit problem: refer it to a team that does it
  2. 2Can the budget fully fund at least one piece of work?
    NoNarrow it: fully fund one lever instead
  3. 3Can someone approve both the work and the spend?
    NoWork that waits weeks for sign-off misses its window
  4. 4Can both sides say how completion will be judged?
    NoWithout a finish line, it is judged on mood
  5. 5Are your people free to staff it?
    NoA capacity problem: a partner delivers it under your brand
Yes to allQualified: a proposal for monthly or fixed work
A no on fit means decline or refer; a no on capacity means find capacity.

Declining good work for lack of people hands the budget to a competitor. Accepting poor-fit work because the team happens to be free fills the calendar with a client who will not renew. The test below is designed to separate the two before anyone quotes.

The five facts we establish before saying yes

We do not qualify an enquiry on company size, a retainer or urgency. We qualify it on five facts, and we write down any that are still unknown rather than guessing. A suitable fixed project qualifies on its own; it does not need retainer potential.

  1. The problem and the deliverable. What must change, and how will both sides know it is done?
  2. Scope fit. Is this work we deliver, or does it belong to someone else? Custom software products, for example, belong to our sibling company, ValueCoders, and we say so on the first call.
  3. The decision process. Who approves the work, and who approves the spend? A first contact does not have to be the final approver, but the path has to exist.
  4. Budget, or a credible route to it. Can the budget fully fund at least one piece of work, rather than a fraction of several?
  5. Timing and dependencies. When must it start, and what has to be in place first: access, content, approvals, another supplier’s work?

For agency enquiries we add a sixth check before any outreach or proposal: whether the end client is already protected under another agency’s agreement with us. An uncertain overlap goes to the sales owner, and we do not proceed while it is unresolved.

Our protection runs through the work and for 12 months after the last assignment for that client ends, so an overlap can exist long after a project has closed. That is why the check comes before the proposal, not after it.

Six outcomes, and what each one means

Every enquiry ends in one of six recorded outcomes. Two of them say no, and both carry a written reason, so the decision can be reviewed later rather than remembered.

Outcome What it means What the client hears
Qualified: retainer Suitable recurring work that meets our recurring-fee criteria A proposal for monthly work
Qualified: package Suitable fixed work that meets our project criteria A fixed-scope proposal, no retainer attached
Needs qualification A credible need with one material fact still open The question we need answered, and who will chase it
Nurture Potential fit, but no buying step yet A follow-up they have agreed to
Refer The work belongs to another team Who should do it, with context passed on if they agree
Decline Unsuitable, cannot be delivered responsibly, or fails the commercial or relationship requirements A specific reason, not a vague “not a fit”

Signals that should make an agency say no

These are the signals we weigh most when deciding, and they matter more than a difficult first call. Any one of them is a reason to narrow the scope; two together are usually a reason to decline.

  • The budget spreads thin. A budget that buys a fraction of an audit, a fraction of content and a fraction of links moves nothing. We recommend fully funding one lever instead.
  • Nobody can approve. Work that waits weeks for sign-off misses its window, and the delay is blamed on the agency.
  • The deliverable has no finish line. If neither side can say how completion will be judged, the engagement will be judged on mood.
  • The date is set before the scope. A launch date fixed before anyone has sized the work turns every later discovery into a crisis.
  • It is outside your craft. Work you would be learning on the client’s budget belongs with someone who has done it.

Our reasoning on budget floors for search work is in why we turn down small SEO retainers.

Saying no without losing the client

A no to the scope does not have to be a no to the client. When we decline, we offer the next step that does fit, where one exists: a narrower scope the budget can fund, a free focused review with prioritised observations and no implementation, or a referral to a team that does the work.

For an agency, the capacity case has a different answer. If the only reason to decline is that your people are busy, the work can be delivered under your brand by a partner while you keep the client and the margin.

The capacity and delivery page sets out the routes, and white-label or referral covers when to hand a client on instead.

When this test is the wrong tool

The test is built for new work. It fits less well in three situations, and we treat each as an exception with a recorded reason and an accountable approver rather than a quiet override.

  • A long-standing client asks for something small. Serving a client of several years can be right even when the job alone would not qualify.
  • A young agency needs cash flow. Taking a marginal project to cover payroll is a business decision, not a failure of the test. Write down why, and when you will stop.
  • The facts will only appear in delivery. When the scope is genuinely uncertain, a paid discovery stage answers the five facts before a full commitment.
Parvessh Agarwal

Written by

Parvessh Agarwal

Founder and Chief Executive, Vinove

Parvessh founded Vinove in 2004 with one idea: build focused technology companies that earn their place in real markets. His focus is on the long game, on companies that survive and serve real customers long after launch.

LinkedIn →
Keep reading

Related
reading.

Rankings on this topic

Scored on public evidence by the PixelCrayons Index. PixelCrayons is scored like every firm: ranked where it has a case study, listed where it has not.

Ways to work with us

A named senior team at one monthly rate, direct or behind your agency's brand.

Questions

Frequently
asked.

Not when the reason is fit. Declining work you cannot deliver well protects your results and your reputation. Declining good work only because the team is busy is different: that is a capacity problem, and it usually has a better answer than saying no.

Give a specific reason and a next step. Name what the budget or scope can fund, offer a smaller piece of work, or introduce someone better suited. A clear reason is easier to accept than a vague “not a fit”, and it leaves the door open.

Rarely for size: a small team alone does not make a poor fit. We decline or pause when the work is outside our scope or a protected-client overlap is unresolved, and record the reason. Joining our partner bench needs no project at all.

Need people,
not a project?

Named specialists at one monthly rate. You interview every person before signing.

Reply within four business hours (typical) · Free · No retainer required