There’s a phrase that should trigger an immediate 40% surcharge on your quote. Five innocent words, delivered with the serene confidence of someone who has never once opened a project management tool in their professional life: “It’s really quite simple.”
By the time they finish explaining what “simple” means, you’re staring at three interconnected platforms, a bilingual version for the Portuguese market, two rounds of user testing with real customers (their cousin and their assistant don’t count), a launch video the CEO wants to post on LinkedIn, and a microsite that needs to integrate with a CRM nobody on their team knows how to use. Oh, and the timeline is eight weeks because “we told the board we’d launch in Q3.”
Welcome to one of the great lies of the creative industry. Not malicious. Not even conscious. Just the eternal optimism of someone who has never had to build the thing they just described.
Why “Simple” Is a Threat Disguised as a Brief
The client who opens with “it’s simple” isn’t trying to deceive you. They genuinely believe it. In their mind, they can already see the finished product — clean, functional, beautiful — and they’ve simply omitted from their mental image the 400 hours of decisions, revisions, stakeholder reviews, technical constraints, and late-night Slack messages that stand between concept and launch.
This is not stupidity. It’s the gap between consuming a product and making one. Everyone who has ever eaten at a restaurant knows what good food tastes like. That doesn’t mean they know how to run a kitchen. The client who says “it’s simple” is the person who ate at a Michelin-starred restaurant and came home confident they could replicate the soufflé.
“Simple” is a brief written in the future tense — a description of how it will feel to use the finished product, not a description of the work required to create it.
Your job, unfortunately, is to live in the present tense.
The Anatomy of a “Simple” Project
Let’s conduct a brief autopsy. The client says they need “a simple website refresh.” Here is what “simple” expands into once the kickoff meeting is done:
A homepage that communicates three different value propositions simultaneously, because the Sales team, the Marketing director, and the CEO all have different ideas about what the company actually does. A contact form connected to a CRM that IT hasn’t upgraded since 2019. A blog section that needs to import 340 old posts without breaking the URL structure. Mobile optimization for “every device” — which turns out to include a Samsung Galaxy S8 that the Finance director refuses to replace. Accessibility compliance for the European market, flagged on day six by Legal, who wasn’t in the kickoff. And, inevitably, a version in English and another in Spanish because “we have clients in Latin America,” which was not mentioned in the original brief.
None of this is unusual. None of this is unreasonable. But precisely zero of it was in the original “it’s simple” framing that set your timeline and budget.
The scope creep didn’t arrive all at once. It came in through the side door, one “while we’re at it” at a time, each individual request perfectly logical in isolation, catastrophic in aggregate.
The Clarification Chain and Other Forms of Slow Bureaucratic Torture
Once you’ve accepted the project — because the budget looked reasonable for “something simple” — you’ll enter what is technically called the Discovery Phase and what is emotionally called the Phase Where You Realize How Much You Didn’t Know You Didn’t Know.
You send a questionnaire. You get partial answers three days later, with three questions answered and two new ones added. You schedule a call to clarify. On the call, three new stakeholders appear who have not read the questionnaire. The stakeholders disagree with each other on fundamental questions about the project. Someone suggests “another alignment call” to resolve the disagreement. The alignment call requires a preparation document. The preparation document generates comments. The comments require a response document.
Forty-seven emails later, you have a brief that is 11 pages long, covers all the things the original brief left out, and bears no relationship to the timeline or budget agreed at the start. Nobody has lied to you at any point. The project was always this complex. It just wasn’t described that way.
This is why the brief nobody reads is sometimes preferable to no brief at all — at least it forces someone to write down what they actually want before you start building it.
Why Clients Say “Simple” (And What They Actually Mean)
Four things are happening simultaneously when a client describes a complex project as simple:
Wishful thinking. They want it to be simple. If it sounds simple, maybe it will be simple. If you agree it’s simple, you’ll quote a simple price. This is not strategy — it’s magical thinking with a budget attached.
Comparison to the wrong reference point. The client is comparing this project to a previous project that went smoothly. They forget the two years of painful iteration that preceded the smooth experience. The smooth version felt simple because all the complexity was already solved.
Genuine ignorance of the craft. Most people have no idea how long anything creative takes. They’ve been told by productivity gurus that focus eliminates friction. They believe a redesign that took another agency six months “should” take four weeks because they’ve seen faster turnarounds in YouTube tutorials.
Anxiety about the quote. “It’s simple” is sometimes a preemptive negotiation tactic. If they establish simplicity before you quote, they have a reference point to push back against your fee. “But you agreed it was simple.”
How to Defuse the Simplicity Bomb Without Losing the Client
You don’t win this argument by proving the project is complex. You win it by making the complexity visible before it becomes your problem.
Scope documentation before kickoff. Not a one-page summary — a proper breakdown of deliverables, assumptions, dependencies, and what happens when any of those assumptions prove false. Slow down the “yes” to speed up the delivery.
Ask the question that clients hate: “What happens if we launch on time but the CRM integration isn’t ready?” Watch the simplicity evaporate. The question doesn’t kill the project — it kills the illusion that there are no trade-offs.
Price the complexity, not the brief. If the brief says “simple website refresh” and your experience says that always means three months of scope expansion, quote three months. Justify it. Lose the client who wanted a four-week quote, or deliver the four-week version and let them live with what four weeks actually buys.
The brief that doesn’t make you cry is not the client’s responsibility to write. It’s yours to extract. The only person surprised by the complexity of a “simple” project is the creative professional who didn’t ask enough questions before starting.
The Simple Truth About Simple Projects
There are no simple projects. There are well-scoped projects and poorly-scoped ones. There are projects with aligned stakeholders and projects with seven people who have never agreed on anything in their professional lives. There are projects with realistic budgets and projects where the client’s mental image of the finished product costs three times what they’re willing to pay for it.
“Simple” is not a project descriptor. It’s a feeling — the feeling the client wants to have when it’s done. And feelings, as any strategist will tell you at great length, are not deliverables.
The next time a prospect leads with “it’s really quite simple,” smile, nod, and open your laptop. You’re about to write a very long scope document. Or you can save yourself the drama — grab a KPI Shark for your desk as a reminder that complexity is always circling beneath the surface, and it’s better to see it coming.
Simple projects exist. They just don’t start with “it’s really quite simple.”