🏷️ Category: Pricing & Commercial Thinking → Pre-Quote Strategy
Hey {{contact.first_name|Friend}}
“Just a simple website.”
Four words that can make a freelance web project sound neat, tidy, and harmless.
This is usually when the danger music should start playing.
A few pages. A cleaner design. A contact form. Maybe some basic SEO setup and a handover video. Nice and straightforward.
Except sometimes that “simple website” isn’t really the project.
It is the visible symptom.
I have learned to be suspicious of the word “just”.
“We just need to look more professional.”
“We just need better enquiries.”
“We just need to update the content.”
“We just need something simple.”
Earlier in my freelance life, I would hear that and think, brilliant, clear brief. I can quote this quickly. Helpful freelancer points for me.
The client has told me what they need. I’ll give them a scope. Everyone moves forward.
Efficient.
But sometimes I was quoting the client’s first description rather than the real problem.
That is an easy trap to fall into because clients usually describe website problems using the language they understand.
They see the website. They see the pages. They see the design. They see the menu. They see the contact form that looks like it has survived three economic downturns and one forgotten plugin update.
So they ask for a new website.
Fair enough.
But beneath that request, there may be something bigger at play.
The site may not just look dated. It may be creating a trust problem.
The navigation may not just be messy. It may be hiding the client’s most valuable services.
The homepage may not just need a redesign. It may need to explain a business that has changed since the website was first built.
The contact form may not just need to work. It may need to help qualify better enquiries.
This is where a $2,000 website brief can quietly be carrying a $10,000 business problem.
Not always, of course.
Some small projects really are small projects. A basic site, a contained scope, a simple outcome. Nothing wrong with that.
The danger is assuming the size of the brief tells you the size of the problem.
That assumption can cost you.
It can lead to underquoting, yes. But more importantly, it can lead to building the wrong version of the right thing.
The website gets delivered. The pages are built. The design is better. The client is technically given what they asked for.
But the deeper issue remains.
They still attract poor-fit leads. They still struggle to explain their offer. They still fail to build trust quickly. They still have a website that exists, but doesn’t really change much.
That is frustrating for everyone.
The reframe is simple:
The brief is not the diagnosis.
The brief is the opening clue.
When a client says they need a simple website, they are giving you their current interpretation of the problem. Your job is not to dismiss it, inflate it, or bury them under strategy jargon.
Your job is to test it gently.
Ask better questions before you quote.
✅ What has changed in the business?
✅ Why is the current website no longer good enough?
✅ What kind of enquiries are they trying to attract?
✅ What happens if they do nothing?
Those questions move the conversation away from “what pages do you need?” and towards “what does this website need to change?”
And that is where better pricing starts.
Not from charging more because someone on LinkedIn told you to “know your worth”.
From understanding what the project really is.
Pause For a Second
Before you quote your next “simple website”, ask yourself:
Am I pricing the thing the client asked for, or the problem the website actually needs to solve?
That one question can change the whole conversation.
I wrote more about this idea on the blog if you want the longer version:
Your $2,000 Website Is Probably a $10,000 Project in Disguise
Your Thoughts
Hit reply with one word:
Surface or Deeper.
Which one best describes how you usually approach new website enquiries?
No need to explain unless you want to.
Wil.
You’re reading 🧭 The Freelancer’s Edge — my fortnightly newsletter for freelance WordPress designers and developers.
Want to revisit past issues or share the love? 👉 Browse the archive here
