Before the Kickoff Call: Fifteen Client Signals That Merit a Pause

Design engagements rarely fail at the kickoff call; they often reveal themselves there. The Client Red Flag Index is a field tool for FNAD members who need to evaluate an opportunity before calendar invitations, file transfers, and deposit invoices create momentum that is difficult to reverse. The index is not a personality test for clients. It is a structured way to notice patterns that predict scope drift, payment delay, and decision paralysis.

How to Use the Index

Read each signal as a prompt for clarification, not as an automatic rejection. A single item may reflect an inexperienced buyer or a rushed internal process. Several items together suggest that the engagement lacks the conditions a designer needs to do professional work. For each signal, the recommended move is a short conversation or written condition that protects the project before it begins.

The Fifteen Signals

1. The scope is a feeling, not a document. The client describes the work in broad aspirations but cannot name deliverables, audiences, or approval criteria.
Move: Send a one-page scope summary before the kickoff. Script: 'Before we schedule the kickoff, I will send a one-page scope so we can confirm what is included, what is excluded, and who approves each stage.'

2. The timeline is already late. The project is urgent because of an internal delay the client has not resolved.
Move: Separate the client's urgency from your capacity. Script: 'I can hold the start date only after the brief and deposit are in place. If those are not ready, the schedule will move by the same number of business days.'

3. Payment terms are treated as a test of trust. The client hesitates on a deposit or asks to defer paperwork until after the first meeting.
Move: Make the commercial terms part of intake, not a later negotiation. Script: 'Our standard terms are a deposit and a signed agreement before work begins. That protects both sides and keeps the project schedule realistic.'

4. The decision-maker is everywhere and nowhere. Several people speak, but no one accepts responsibility for final approval.
Move: Ask for a named approver. Script: 'Please identify one person who has final sign-off. I will route review questions through that person so feedback does not conflict.'

5. 'We will know it when we see it.' The client cannot define success but expects the designer to recognize it intuitively.
Move: Convert taste into criteria. Script: 'Let us agree on three measures of success and two examples of work you do not want. That will help us evaluate directions without relying on instinct alone.'

6. The budget is a secret. The client wants a proposal without sharing a range, constraints, or procurement limits.
Move: Offer tiered options rather than a single guess. Script: 'I can provide three levels of scope with different budgets. That will let you choose a fit without asking either of us to invent a number.'

7. Procurement is described as a formality. The client implies that contracts, insurance certificates, or vendor onboarding can wait.
Move: Treat procurement as part of the critical path. Script: 'I will not begin discovery until vendor onboarding is complete. That avoids rework if the paperwork requires changes to the agreement.'

8. Past vendors are described only as villains. The client explains every previous disappointment as a failure of character rather than a mismatch of process.
Move: Ask what worked, not only what failed. Script: 'What did the last engagement do well that you want repeated? That will help me understand the working style you expect.'

9. The brief arrives as a screenshot of a competitor. The client wants a result without describing the problem it should solve.
Move: Return to the underlying business question. Script: 'I can use that reference as a visual input, but I need to understand the audience and decision it supports before I recommend a direction.'

10. Meetings are scheduled without an agenda or an owner. Recurring calls appear before anyone has defined their purpose.
Move: Require a short agenda and a decision owner for each meeting. Script: 'I will attend recurring reviews if we set an agenda and identify the decision needed. Otherwise, I will send a written update.'

11. Feedback is plural but unattributed. Comments arrive as 'the team thinks' or 'leadership feels' without a source.
Move: Ask for consolidated, attributed feedback. Script: 'Please consolidate comments through the approver and note who raised each point. That will help me respond to the actual decision-makers.'

12. The client wants to own files before signing. Source files, working documents, or final assets are requested during the proposal stage.
Move: Clarify ownership and transfer timing in the agreement. Script: 'Ownership and file transfer are defined in the agreement. I can explain the terms before signature so there are no surprises later.'

13. Rush fees are expected as standard. The client treats accelerated delivery as a normal courtesy rather than a tradeoff.
Move: Price the acceleration explicitly. Script: 'The requested timeline requires additional capacity. I can meet it with a rush fee or adjust the schedule to the standard pace.'

14. Communication moves to private channels before agreement. The client wants to continue by text or personal email while leaving the formal record incomplete.
Move: Keep project decisions in a shared written record. Script: 'I will use email for project decisions so both teams have a clear record. We can use messaging for scheduling only.'

15. The project is framed as a favor. The client implies that exposure, goodwill, or future work should substitute for part of the fee.
Move: Separate relationship-building from commercial work. Script: 'I value the relationship, and the project still needs a fee that covers the scope. I can adjust the scope if the budget is fixed.'

A Simple Go/No-Go Scorecard

Use the index during intake, not after the proposal is sent. Score each of the fifteen signals as follows: 0 for absent, 1 for unclear or unaddressed, and 2 for clearly present. The maximum total is 30.

• 0–8: Proceed with standard terms and a written scope.
• 9–16: Proceed only after clarifying the highest-scoring items and confirming them in writing.
• 17–30: Decline, pause, or require a revised engagement structure before investing further time.

The scorecard is not a substitute for professional judgment. It is a record of what was known before the work began. For FNAD members, that record is also a useful advocacy tool: it shows that responsible client selection is part of professional practice, not an obstacle to business development.