It begins, as all great catastrophes do, with five innocent words: “I just need something simple.” These words are spoken in the same casual, breezy tone one might use to order a coffee. And like a coffee order that becomes “oat milk, extra shot, no foam, 140 degrees, in a 12-ounce cup for a 16-ounce drink,” the project that follows is rarely what was advertised.
I have been building software for over 12 years. And in all that time, the most dangerous, budget-destroying, timeline-obliterating phrase I have ever encountered is not a complex technical requirement. It is eight words and an invoice that will give you an eye twitch:
“I just need a simple website. Nothing fancy.”
The Client Phrasebook
Every client speaks a dialect of English that sounds perfectly normal until you start building. Here is a brief translation guide:
”Just 5 pages — Home, About, Services, Contact, Blog.”
…plus a client portal, booking system, custom chat widget, and 300 blog posts to import “somehow.”
”Make it look like Apple’s website. But more colorful. And friendlier.”
They want a $500,000 design budget executed for $299. The reference is Apple. The budget is a gas station sandwich.
”We don’t need anything fancy — no AI or anything.”
Two weeks later: “Can it recommend products like Amazon and chat with visitors like ChatGPT?”
”Content is almost ready, just needs finishing touches.”
The content does not exist. It will arrive as a Word doc on Day 29, formatted in Comic Sans.
The Scope Creep Lifecycle
The Budget Nobody Wants to Discuss
Here is the thing about budget conversations: nobody wants to have them, so they don’t, and then everyone suffers quietly. The client thinks they’re being reasonable. The developer thinks they’re being underpaid. Both are correct.
I have built AI systems that generated 35% revenue lifts for Fortune 500 clients. And the hardest conversation I have ever had in this industry is not about model architecture — it’s convincing a new client that “something simple” requires a scope document before I open my laptop.
The irony of software development is that the simpler something looks on the outside, the more complex it usually is on the inside. A beautiful, minimal website isn’t simple — it’s the result of someone hiding extraordinary complexity behind a well-designed interface. The client is standing on the surface saying “there’s hardly anything here!” while the developer quietly drowns in API integrations below.
What to Actually Do About It
If you’re a client reading this: your developer is not being difficult when they ask for requirements. They are trying to save you from yourself. Sign the scope. Respect the timeline. Do not email at 11pm with “one small thing.” The small thing is never small. It is a database migration wearing a trench coat.
If you’re a developer reading this: charge what you’re worth, document everything in writing, and build in a scope-change clause before you write a line of code. The single biggest quality-of-life improvement I’ve ever made was not a new framework. It was a contract template.
The most valuable thing I offer clients isn’t code — it’s clarity. What will we build? What will it do? What happens when you change your mind in week three? Answer those questions upfront, and the “simple website” becomes a manageable project instead of a cautionary tale.
You’re welcome. Go write a scope document.