Early in business you take almost every client. You need the revenue and you tell yourself you can make it work. Years later you develop instincts that protect both sides. Here are the warning signs I now recognise early.
Early in business, you take almost every client who calls.
You have to. The overheads are real, the pipeline is uncertain, and every new engagement represents income and — you tell yourself — an opportunity to prove your value. You find reasons to overlook the things that make you uneasy in the sales conversation. You decide you can work around them.
I spent several years doing exactly this. And I learned, through enough uncomfortable experience, that the instincts I was suppressing in those sales conversations were almost always right.
The clients I should have walked away from early were the ones who eventually caused the most friction, the most unpaid work, the most staff stress, and in some cases the most reputational risk. The revenue they brought in rarely justified what came with it.
These days I have different conversations with prospective clients. And I have a set of signals that I pay attention to very carefully — not because I am looking for reasons to say no, but because I have learned that a good client relationship requires the right fit on both sides. When it is not there from the start, no amount of goodwill can manufacture it later.
Here is what I watch for now.
”We Just Need Basic IT Support — Nothing Complicated”
This one sounds reasonable. Most businesses are not running complex enterprise infrastructure. Most requests are, in fact, not particularly complicated.
The problem is not the statement itself. The problem is what it often signals underneath: an expectation that IT support is a commodity, that one provider is interchangeable with another, and that the relationship is transactional rather than advisory.
Clients who approach IT this way tend to evaluate everything on price. They do not understand — or do not want to understand — the value of proactive work, security posture, strategic planning, or relationship continuity. They will always have a cheaper quote in their inbox. Every conversation about investment eventually becomes a negotiation about cost reduction.
More importantly, there is no such thing as “basic IT support” for a business that is actually running on technology. Every business has complexity. The ones who believe they do not are often the ones who have not yet experienced what happens when something goes wrong in an environment that has been managed to the minimum.
When a prospective client tells me they just need basic support, I do not automatically decline. I explore what they mean by it. But if the conversation reveals that they have genuinely no interest in security, no appetite for strategic input, and a view that the role of an IT provider is to fix things when they break — I am honest about the fact that we are probably not the right fit.
They Have Had Three IT Providers in Two Years
This one is worth understanding carefully, because there are legitimate reasons to change IT providers — a genuinely poor service experience, a change in business size or complexity that the provider could not accommodate, a specific incident that revealed a capability gap.
But three providers in two years is a pattern, not a series of bad luck. And the pattern almost always reveals something about the client rather than the providers.
What I have found, in every case I can recall where this has come up, is one of the following: the client has unrealistic expectations about response times and availability, the client has disputed invoices and been difficult about payment, or the client has an internal person who undermines the IT provider’s relationship with the rest of the business.
I now ask directly: why did you leave each of them? What I am listening for is whether the client can articulate a clear, specific, reasonable reason for each departure — or whether the pattern involves escalating frustration, conflict over cost, and a sense that the provider was never quite good enough.
If the latter, the problem almost certainly travels with the client. We would be provider number four.
They Want to Negotiate the Contract Before They Have Even Seen It
There is a difference between a client who reviews a contract carefully and asks reasonable questions about specific terms, and a client who enters the conversation wanting to negotiate before they know what they are negotiating.
The second type is signalling something important: they are not primarily trying to understand what they are buying. They are trying to establish that they have leverage. The opening position is not “help me understand this” but “I want a better deal.”
Clients who begin the relationship this way rarely improve. The negotiation does not end at the contract — it continues into the engagement. Invoices get scrutinised for reasons to reduce them. Scope discussions become adversarial. Every out-of-scope request becomes a dispute about what was implied.
I am happy to discuss our pricing, explain how we structure engagements, and work with businesses that have genuine budget constraints. What I now decline to do is enter a relationship that begins with the assumption that our proposed terms are a starting point for a downward negotiation.
Their Internal IT Person Is in the Room and Has Said Nothing
This is a specific scenario, but I have seen it enough times to trust it.
A business brings us in for a conversation. There is an internal IT coordinator or a staff member who handles day-to-day technology issues. That person sits in the meeting but contributes nothing — no questions, no context, no engagement. They are present but not participating.
What this usually means is that the internal person feels threatened by the conversation. They are worried about their role. And rather than engaging with the possibility that a managed IT provider could support and extend what they do, they have decided — consciously or not — to obstruct it.
The obstruction is rarely overt. It tends to be passive: slow responses to requests for access credentials, delays in sharing documentation, a quiet stream of negative commentary to the decision-maker after meetings. The engagement technically starts but practically never gets traction.
I have learned to address this directly in the room. I talk explicitly about how we work alongside internal IT people, what that collaboration looks like, and what each side is responsible for. If the person in the room does not engage when I do that — if the wall stays up — I take it seriously as a signal about how the engagement will go.
They Tell Me My Predecessor Left a “Complete Mess”
I have taken on environments in genuinely poor condition. Servers running unsupported software, no documentation, security policies that had never been reviewed. That work is real and we do it.
But there is a difference between a client who acknowledges a poorly managed environment and is genuinely committed to fixing it, and a client who uses “complete mess” as an explanation for why no provider before us has ever been able to deliver what they needed.
The second type is often describing a situation where the “mess” is partly of their own making — they did not allow proactive work, they did not fund the remediation, they approved workarounds instead of proper fixes. They are now looking for a new provider who will either clean up for free or inherit the mess without being allowed to properly address it.
I ask a specific question in these conversations: if we identify things that need to be fixed, and we give you a clear recommendation with a cost and a timeframe, what happens? If the answer is evasive — if it involves vague references to budget constraints and questions about whether it is strictly necessary — I have my answer about why the previous environment was in poor condition.
They Have Been “Meaning to Do Something About Cybersecurity”
Every IT provider in Australia has heard this sentence. Businesses know they should have better security. They are aware, at some level, of the risk. They have been intending to address it.
Except they have not. And the conversation is usually happening because something has either almost gone wrong or they need to tick a box for an insurance application or a client contract requirement.
I take this seriously as a signal because it tells me how decisions will be made in the engagement. Security work requires approval, funding, and sometimes disruption to existing workflows. If the history is that security was always the thing they were going to get to eventually, the same inertia will apply to the security work I recommend.
The clients who treat security recommendations as urgent and act on them promptly are the ones whose environments I can actually protect. The clients who treat every security recommendation as a negotiation about cost and timing are the ones who will eventually have an incident — and who may, if they are not careful, point at us as the party responsible for not having prevented it.
I do not decline these clients. But I document the recommendations I make and the responses I receive, and I am explicit about what the risk looks like if they choose not to act.
What This Is Really About
None of these signals are about avoiding difficult work or demanding perfect clients.
They are about fit. The clients we work with best are the ones who understand that IT is a business-critical function, who engage genuinely with the strategic conversation, who act on recommendations, and who treat the relationship as a partnership rather than a vendor transaction.
Those clients get the best outcomes from us. We invest more in their environments, we are more proactive, and we are genuinely motivated to help them grow. The relationship produces something more than what either party could generate alone.
The clients who do not fit that model — who want the minimum for the lowest price, who have a history of difficult provider relationships, who resist the strategic conversation — tend to have poor technology outcomes regardless of who their provider is. The common thread is not the provider.
I am not the right IT partner for every business. Knowing that, and being willing to say so, is something I had to learn. I am glad I did.
