"It should be easy, right?"
This is the most dangerous phrase in software development.
Every time a client says it, I know we're heading for trouble.
Why "Easy" Is Never Easy
When a client says "it should be easy," they're looking at the happy path.
User clicks button → thing happens → done.
But that's not software. That's a fairy tale.
Here's what "easy" features actually involve:
→ Authentication — who can access this? → Authorization — what are they allowed to do? → Validation — what if they enter bad data? → Error handling — what if the API is down? → Edge cases — what if they do it twice? Or zero times? → Testing — how do we know it works? → Integration — how does it affect other features? → Performance — what if 1,000 users do this at once? → Security — can this be exploited? → Rollback — what if we need to undo it?
The "easy" button click is 5% of the work. The other 95% is handling everything that can go wrong.
When Agencies Agree
The real disaster happens when agencies agree that something is "easy."
Why? Because they want the sale. They want to sound capable. They want to avoid the awkward conversation about complexity.
So they say: "Oh yeah, totally easy. We can knock that out."
Then the project blows up.
Scope expands. Timeline slips. Budget doubles. Client gets angry. Agency gets defensive.
All because nobody wanted to say: "Actually, it's more complex than it looks."
The Right Response
When a client says "it should be easy," here's what we do at ScopeForged:
We explain what's actually involved.
Not in a condescending way. Not to inflate the estimate. But to educate.
"Here's what needs to happen behind the scenes. Here are the edge cases. Here's why it takes time."
Clients respect honesty more than false reassurance.
They'd rather know upfront that something is complex than discover it halfway through when the timeline explodes.
Real Example
Client: "We just need a simple file upload. Should be easy, right?"
Us: "Let's walk through it:"
→ What file types are allowed? → What's the size limit? → Where do files get stored? → Who can access uploaded files? → What if the upload fails halfway? → How do you handle viruses or malicious files? → Do you need versioning? → What about mobile uploads? → How do you handle concurrent uploads? → What's the retention policy?
The client didn't think of any of this. That's fine — that's our job.
But if we'd said "yeah, easy," we'd both be in trouble when those questions came up mid-build.
The Trust Signal
When you tell a client something is more complex than they thought, you might worry they'll think you're padding the estimate.
The opposite happens.
They trust you more because you're showing them the reality of the work.
You're not trying to win the sale with false simplicity. You're giving them the information they need to make a good decision.
That's the foundation of a good client relationship.
Never Agree That Something Is Easy
Even when it actually is straightforward, I don't say "easy."
I say: "That's a well-defined problem with a clear solution. Here's what's involved."
Because "easy" sets the wrong expectation. It implies it's trivial. That it should be free. That it won't take time.
Software is never easy. It's just varying degrees of complex.
How do you handle "it should be easy" from clients?
#softwaredevelopment #consulting #projectmanagement #clientrelations
→ scopeforged.com
Philip Rehberger Founder, ScopeForged scopeforged.com
