One Battle After Another: Why Great Projects Start with Saying No

The Project That Should Never Have Started

Alex opened by grounding the talk in a specific, real failure rather than theory. He described a project that looked ideal on paper: a large, recognisable brand, a substantial budget, and a global rollout scope. Internally, this was the kind of project teams celebrate. It was positioned as "the one."

But from the very first call, something did not feel right. Three warning signs appeared immediately: there was no identifiable decision maker, the timeline had already been fixed before the agency was involved, and the client revealed that multiple agencies had attempted the project before and all had failed.

The internal response was to override the doubt. The agency concluded it could succeed where others had not. It could not.

What followed was, in Alex's own description, "one battle after another." The difficulty was not rooted in technical complexity. The setup itself was broken from the start. The project produced endless scope debates, persistent alignment failures, constant delays, and a stream of escalations. Alex used this story as the lens through which the entire session was framed: the lesson was not about delivery, it was about selection.

What Makes a Client Good or Bad

Alex was explicit that budget and brand name are not indicators of client quality. The markers of a good client are behavioural and structural.

A good client demonstrates:

• Clarity about what they want and why
• Clear internal ownership and a designated decision maker
• Willingness to be challenged and to challenge

the agency in return

• An understanding of the complexity involved
• Commitment to a shared understanding of what success looks like A bad client exhibits the opposite:
• No clear ownership internally
• A price-driven orientation from the outset
• Constant change requests and shifting requirements
• Internal misalignment, with different stakeholders pulling in different directions The most important observation Alex made here was that bad clients do not break projects in isolation. They break teams. The human cost to staff who are trapped in chaotic, directionless engagements is where the real damage is done.

The Five Red Flags

Alex identified five specific signals that, when present, should trigger serious reconsideration of whether to proceed.

Red Flag 1: No Decision Maker When a client says something like "we need to align internally first," this sounds harmless.

Alex was clear that it is not. The absence of a reachable, empowered decision maker means the project will be governed by politics, approvals will take longer than expected, real progress will stall, and accountability will be diffuse. The phrase itself should function as a stop sign.

Red Flag 2: Discovery Resistance If a prospect pushes back on a discovery phase and asks for a quick estimate based on incomplete requirements, they are signalling that they do not intend to invest in understanding their own problem. Alex's view is direct: if they will not invest in understanding, they will not invest in success. The discovery phase costs money and time, and clients who treat it as optional are demonstrating a fundamental attitude toward the project that will not change once work begins.

Red Flag 3: Price-First Conversations When pricing is the dominant topic in early conversations, it will remain the dominant topic throughout the engagement. "Can you make it cheaper?" as an opening move is a predictor, not an anomaly. Alex stated plainly: if price is the main topic at the beginning, it will be the only topic later.

Red Flag 4: Blaming Previous Agencies When a prospect has worked with multiple agencies and all of them have failed, Alex acknowledged this is theoretically possible. But he urged caution about accepting the explanation uncritically. If everybody before you was a problem, there is a real chance you will be the next one.

Red Flag 5: The Smell Test The hardest signal to name but the one Alex said should be taken most seriously is the intuitive feeling that something is off. This is the case where you cannot articulate a specific objection, but something in the dynamic feels wrong. Alex's consistent pattern, before he learned to act on it, was to justify that feeling away with other arguments, reminding himself of the budget size or the brand name or the growth opportunity. His instruction to the audience: if you feel it early, trust it.

Why Agencies Keep Saying Yes Anyway

Alex was candid about the forces that override good judgment. He listed them without defensive framing: Revenue pressure: The pipeline needs filling, and this deal is available now.

The big logo: A recognisable brand name on the website or in a pitch deck is genuinely valuable for future sales.

Networking and referral value: Some clients open doors to others.

Fear: Fear of having nothing to replace the deal with if it is declined.

Ego: The desire to prove the agency can handle what others could not.

Alex made an important distinction here: most bad clients do not trick you. You convince yourself. The agency is not the passive victim of a deceptive prospect. It is an active participant in its own poor decision, rationalising away signs that are visible and legible from the start.

He gave a concrete example: a large, well-known brand that the entire team wanted to work with. Everybody internally craved that logo. From the beginning, there were too many stakeholders, no real ownership, and unclear decision-making. They said yes anyway. What followed was a coordination disaster. The logo looked good on the website. The project did not feel good for the team, and it did not perform well financially either.

Discovery as a Decision Point, Not a Delivery Step

The structural shift Alex described at Side is treating discovery not as the first phase of a project but as a filter that determines whether a project should happen at all.

The criteria the discovery phase tests for are the same ones that make a good client: Does the client have clarity about what they want? Do they have genuine ownership? Are they open to being challenged?

If the answers are no, Alex's position is unambiguous. Better delivery cannot fix a broken setup. Excellent execution does not compensate for a client with no internal alignment. The agency's job in discovery is to surface this, not to manage around it.

He gave a positive example of this principle working: a client where everything looked promising on the surface, but during discovery it became clear that different internal stakeholders had completely different visions for the outcome. Rather than pushing through, the agency stopped. Alex said that decision saved months of frustration on both sides and, in hindsight, was validated when he heard from another agency that had taken the project instead and found it to be a nightmare.

The design principle here is important: discovery must be kept commercially decoupled from the main project. It is a separate, paid engagement. This serves two purposes. It ensures the client has skin in the game before a larger commitment is made, and it allows the agency to walk away after discovery without the sunk cost of a full proposal process or an active contract.

The Communication Structure Problem

Alex described a specific scenario involving a hosting partner that illustrates how structural ambiguity destroys projects even when all parties have good intentions.

A hosting company that had referred Side to a client insisted on positioning their own project manager as the primary communication layer between Side and the client. On paper, this was framed as a strategic partnership. In practice, it introduced a filter into every conversation.

The problem was not the person specifically. The problem was that the person lacked deep experience with complex projects, so context was lost, feedback was delayed, and decisions were interpreted rather than transmitted. Over time it became apparent that the hosting company's real motivation was not project success but maintaining control and billing additional project management fees.

The result was more meetings, more friction, more alignment overhead, and no corresponding increase in project value. Alex's diagnosis: this was not a delivery problem, it was a structure problem. And structure problems cannot be fixed by better execution.

He extended this into a broader principle: who decides, who owns, and who is accountable must be made explicit and confirmed at the very beginning of any engagement. If those questions are ambiguous at the start, they will remain ambiguous throughout.

How to Say No Without Simply Saying No

Alex was careful to distinguish between rejection and reframing. The goal is not to say "we cannot do this" but to say "this creates unacceptable risk, and here is a better path that reduces it for both of us."

Some of the practical approaches he described: Raise concerns directly and early. Ask the uncomfortable questions. Many clients will respond positively and clarify things they had not considered. If a prospect is genuinely open to being challenged, they will welcome the questions. If they are not, that is itself important information.

Start with a smaller scope. Rather than committing to a large engagement with an unknown client, propose a smaller piece of work first. This allows both parties to establish trust, observe how the relationship actually functions, and make a better-informed decision about deeper commitment.

Reframe the conversation around risk. Instead of outright refusal, present the concerns as risk factors and offer options for managing them.

Acknowledge that a client's strange behaviour may reflect past trauma. Some clients who act defensively or distrustfully have had genuinely bad experiences with previous agencies. Starting smaller and building trust gradually is a legitimate path with these prospects.

Critically, Alex returned to the theme of asking uncomfortable questions. He described his own internal hesitation, the familiar feeling of "should I ask or shouldn't I, I don't want to push them toward another agency." His conclusion: ask. The upside of a client who is grateful for the question and clarifies everything is large. The downside of a client who reacts badly to reasonable questions is that you have learned something essential before signing a contract.

Protecting the Team as a Leadership Function

One of the more direct statements Alex made was about where leadership accountability lies. Winning clients is part of a CEO's job. Protecting the team from the wrong clients is equally part of the job, and it is the part more often neglected.

The human consequences of bad client decisions compound over time. A developer trapped in a chaotic, politically fractured project is not just producing worse work. They are accumulating frustration, losing motivation, and building a case in their own mind for finding somewhere better to work. Alex named demotivation, frustration, burnout, and departure as the real and predictable downstream consequences of accepting clients who should have been declined.

He also made a point about escalation management. When a client relationship is deteriorating and reaching a point of conflict, it is generally a leadership function, not a developer or project manager function, to step in. One reason this matters beyond organisational hierarchy is that a senior person stepping in brings no prior friction from the daily working relationship. They can engage fresh, from a more neutral position, and attempt to find a constructive resolution without the accumulated weight of weeks or months of difficult interaction.

Alex described instances where he had stepped in personally and found immediately that some clients were not genuinely interested in resolution. They wanted to vent. They were not bringing a problem they wanted solved. Distinguishing between a client with a legitimate grievance who wants to fix the relationship and a client who is simply dissatisfied and looking to exit is itself valuable, because it determines what kind of response is appropriate.

The Fireside Conversation: Practical Applications

Does This Scale Down to Smaller Agencies?

The host raised the question of whether selectivity is a luxury available only to a firm with 130 people and a strong pipeline. Alex disagreed firmly.

For a freelancer or a small agency, the argument for saying no is stronger, not weaker. A small operation with a limited number of active projects has almost no ability to absorb a bad one. A single toxic client can consume all available capacity, generate no margin, bind the best people to a non-functioning engagement, and block the intake of better work.

Alex pointed to real-world consequences he had observed in the industry: agencies that accepted the wrong clients, failed to get paid, faced legal action from those clients, and in some cases went into bankruptcy. The risk profile is asymmetric at small scale. The bad outcome is existential in a way it is not for a larger firm.

His recommendation: start the practice of selectivity now, regardless of size or pipeline pressure.

When a Client Is Not Paying A summit participant shared a real situation: a client refusing to pay a third invoice of $1,000, with the web hosting and domain now out of the agency's control. The participant had already taken down the website using a contract clause, was considering a legal demand letter, and had some pre-law background.

Alex's response was measured. He acknowledged that the participant had done one important thing right: they had a contractual clause that allowed them to act. Many freelancers and small agencies omit this kind of protection because they optimistically assume everything will work out.

On whether to pursue the matter legally, Alex raised the question of proportionality. At $1,000, with the client controlling the domain and hosting, the fight may cost more in time, energy, and focus than the amount in dispute. His suggestion was to consider the retrospective: did you have a gut feeling early on that something was off? If so, that is the lesson to carry forward, and the money may be the price of that education.

He explicitly advocated moving on. Keeping a bad debt case in active mental focus compounds the damage. The opportunity cost of spending cognitive energy on a $1,000 dispute rather than on the next client is real.

How Enterprise Sales and Pricing Actually Work The host asked about the practical mechanics of pricing for Fortune 500 clients, and Alex walked through Side's approach in some detail.

The starting point is always a detailed discovery or workshop, kept commercially decoupled from the main project. The purpose of this stage is to build a sufficiently granular understanding of requirements that the subsequent proposal can be genuinely transparent, with each requirement as a line item with an associated cost.

This approach serves several functions. It makes the proposal legible to a client who would otherwise see only a large total number. It allows the client to make active decisions about scope, prioritisation, and phasing. It makes it visible which elements cost what, so a client can choose to defer the "sauna" or the "marble bathroom" to a future phase rather than cutting scope in ways that damage the core outcome. And it builds trust by demonstrating that the agency has understood the full picture.

For pricing models, Alex expressed a clear preference for time and material over fixed-price contracts, particularly on large or complex projects. Fixed pricing requires building in large contingency buffers, and even then, it rarely reflects the actual outcome as accurately as T&M does. With time and material, if a component takes less effort than anticipated, the client pays less. If it takes more, the context is visible enough that the conversation is more likely to be constructive.

He acknowledged that some clients dislike T&M and prefer the certainty of a fixed price. His response is to make the T&M itemisation detailed enough that clients can understand and interrogate the inputs rather than simply accepting or rejecting a single number.

For productised or platform-based solutions that Side has already built, he described a value-based pricing model rather than time and material, where the price reflects the value delivered rather than the hours invested in building what already exists.

How to Evaluate Trust Before Signing Alex was asked how Side evaluates whether a client is trustworthy before a contract is in place. His answer was consistent with the broader theme: observe behaviour rather than listening to statements.

The signals he watches for include: whether the client invests in understanding their own problem, whether there is a reachable and empowered decision maker, whether the client follows through on small commitments during the sales process (such as sending requested information when they said they would), and how they respond to being challenged or asked difficult questions.

He acknowledged that trust cannot be assessed with certainty. There is no definitive test.

Building trust is an iterative process, the same whether between companies or between people. Small tests, careful observation, and escalating commitment are all part of it.

On contracts specifically, Alex echoed a point the host made: the moment the relationship shifts to a conversation about specific contract clauses, the relationship is probably already over. The contract is infrastructure for a worst case that you hope never materialises. Side's preference is to hold clients to their stated commitments and expectations rather than invoking contractual mechanisms, and to escalate to senior leadership if the relationship is in difficulty.

The Impact of AI on Agency Work Both Alex and the host agreed on a point that runs counter to a common assumption: AI has not significantly shortened the time it takes to deliver a project to a client.

Alex cited a colleague, Alain Schleser, who made the observation that AI makes a single developer faster but does not make a project faster. Alex's estimate was that AI tools improve individual developer productivity by perhaps 10 to 15 percent, with a ceiling of around 20 percent on specific tasks.

The reason projects do not shrink proportionally is that development time was never the dominant variable. Communication, alignment, expectation-setting, decision-making, review cycles, and client-side delays are what govern project timelines. None of these are materially accelerated by AI.

The host illustrated this with a concrete example: a five-page website that used to take three days to build now takes three hours. But the full delivery cycle, including client communication and iteration, was six weeks before and is perhaps five weeks now. The build is ten times faster. The delivery is not.

Alex also offered an interesting practical application: using AI tools like Claude to analyse transcripts or written requirements from client conversations and flag potential red flags. If the transcript of a first client call is run through an AI tool that identifies concerning patterns, that analysis can serve as a useful second perspective on whether a prospect is a good fit.

Specialisation vs. Expansion The final topic was the tension between staying focused on a core specialisation and expanding the range of services an agency offers. This was contextualised by a question about whether Side does SEO or digital marketing alongside its WordPress work.

Alex's answer was direct: no. Side focuses exclusively on enterprise WordPress development, including multi-site architecture, multilingual implementation, and the technical foundations of SEO. Everything else, including SEO strategy, content marketing, and branding, is handled through partnerships with specialist agencies.

His reasoning: you cannot be excellent at everything, and trying to do so spreads focus in a way that undermines quality in your core area while producing mediocre results in the peripheral ones. He cited the history of large conglomerates, including General Motors, as examples of organisations that over-expanded their range and were eventually forced to divest or restructure.

He also acknowledged that Side had tried to expand into hosting and other adjacent services at various points, and concluded that without total dedication and the right people, those efforts never performed at the level the WordPress development practice did.

His instruction to the audience: identify what you do best, stay focused on it, and believe in it. If opportunities appear to expand and the conditions are genuinely right, evaluate them seriously. But do not diversify into adjacent services as a growth strategy if it means dividing attention from what already works.

On the Scale Consortium, Alex noted that the consortium's purpose is to position WordPress as a credible enterprise solution and prevent fragmentation in that space. He did not accept the premise that membership in the consortium requires agencies to turn away non-enterprise tiers of business, though he did not elaborate at length.

The Future: Where the Industry Is Going

Alex was asked for a prediction about where the industry would be in two years, both for Side specifically and for the broader WordPress and agency landscape.

He was honest about the limits of confident prediction. He noted that the current moment of AI disruption resembles the early internet in that nobody truly knew then what the internet would become, and nobody truly knows now what the AI transition will produce. He acknowledged that his own views on the two-to-three-year outlook change every two to three months as new developments emerge.

His most substantive directional observation was that agencies at the enterprise level are already moving from a primarily development-focused model toward a consultancy-focused model. The value is increasingly in expertise, judgment, the right questions, established trust, and network, not in the technical execution of tasks that AI tools are progressively making faster and cheaper.

He drew an analogy to the gap between a Champions League football player and a first-division player. The difference is not large in absolute terms, perhaps five percent. But that five percent represents something qualitatively different: the elite tier. He argued that agencies need to be in that five-to-ten percent of exceptional value delivery, which comes from expertise, personality, and the kind of trusted advisory relationship that no AI tool can replicate.

He also raised an open structural question about the future of websites themselves: as AI changes how people search for and receive information, the premise that every organisation

needs a website as a primary interface may itself be worth questioning. He did not resolve this question, but he named it as a live uncertainty rather than a settled one.

About the speaker Alex Frison SYDE

Alex Frison is with SYDE, an agency focused on high-stakes client engagements. He is known for his views on discovery, client qualification, and knowing when to say no to a project.