Client Red Flags Before Project Start¶
Use this page when you can already see warning signals before the project starts.
This page focuses on early risk indicators that often look manageable in isolation but become expensive once they stack together.
What This Risk Usually Looks Like¶
Contradictory answers¶
The client changes the description of the problem, success criteria, or timeline from one conversation to the next.
Pressure to commit before clarity¶
You are being asked to quote, schedule, or start before the brief is stable.
Vague approval path¶
Feedback can come from multiple directions, but no final decision-maker is clearly visible.
Weak payment signal¶
The client wants commitment first and structure later.
Why This Becomes Dangerous Before Commitment¶
Red flags rarely stay isolated¶
One signal often predicts another: vague scope can travel with deposit resistance, stakeholder sprawl, and revision drift.
Early ambiguity usually expands after kickoff¶
If expectations are unstable now, they usually do not become cleaner once the work has started.
What Not to Do Next¶
- do not normalize instability because the project looks attractive
- do not assume a signed agreement will fix unclear expectations by itself
- do not ignore several smaller warning signs because none of them looks fatal alone