The conversation had been going well.
The potential client had explained why their WordPress website was becoming a problem. Staff struggled to update it. Enquiries had slowed. Important pages no longer reflected what the organisation actually offered.
They clearly needed help.
Then they asked the apparently simple question.
“What would you charge to redesign it?”
You explained your process. Discovery, strategy, design, development, content migration, technical SEO, performance optimisation and launch support.
Nothing you said was wrong.
But the conversation changed.
The client stopped discussing their problems and started comparing your list of tasks with proposals from other WordPress freelancers.
A few days later, they disappeared.
Clients Cannot Value What They Cannot Interpret
Clients do not buy web design tasks. They buy a clear path from a problem they understand to an outcome they value.
The deliverables matter, but primarily as evidence that you understand how to move them from one side to the other.
This distinction is easy to forget when you have worked with WordPress for years.
You understand why a redesign might require template reconstruction, block pattern development, plugin rationalisation, redirect planning and improvements to the editorial experience.
To you, these are meaningful pieces of work.
To the client, they are unfamiliar terms sitting beside a price.
The client does not know which parts require experience, which reduce risk or which will make the website easier for their team to manage three years from now.
They may still buy.
But if they cannot appreciate the value of the work, they will make their decision based on whatever signals they can grasp.
Price is usually one of them.
WordPress Services Are Difficult to Compare Properly
WordPress creates an unusual commercial problem for experienced freelancers.
The platform is familiar enough that clients often feel they understand what is involved. They have heard of themes, plugins, page builders and hosting. They may already update pages themselves.
A website proposal can therefore appear to contain a collection of recognisable tasks:
- Install WordPress
- Customise a theme
- Build ten pages
- Add a contact form
- Improve the SEO
The wording makes substantially different services look interchangeable.
One freelancer may be configuring an existing theme and inserting supplied content. Another may be rebuilding the organisation’s information architecture, resolving years of accumulated plugin decisions and creating an editing system that staff can use without damaging the site.
On paper, both may be selling a WordPress redesign.
That is not the client being careless. It is a natural result of presenting the work in a form that conceals the difference.
The more experienced freelancer often has the harder offer to explain.
Experience reveals complexity. It exposes dependencies, risks and decisions that a less experienced provider may not yet recognise.
But when all that knowledge is translated into a longer list of deliverables, the experienced freelancer can appear more expensive without seeming more valuable.
That is where the comparison begins to fall apart.
Your Description Teaches Clients How to Compare You
The way you describe your services does more than communicate what you offer.
It teaches the client how to compare you.
If your proposal centres on page counts, templates, plugins and development hours, the client will compare page counts, templates, plugins and development hours.
If your care plan is described as WordPress updates, backups, and security monitoring, it will be compared with every inexpensive care plan that offers the same three labels.
The comparison may be technically absurd, but it is still the comparison you enabled.
Once a client has reduced the decision to visible deliverables, the deeper judgement behind the work becomes difficult to recover.
Your knowledge of WordPress permissions, editorial behaviour, plugin risk, accessibility and long-term maintainability remains invisible.
The client cannot assign value to judgement they cannot see.
They can only decide whether the visible outputs appear worth the visible price.
More Detail Does Not Always Create More Clarity
The common response is to explain more.
A freelancer notices that clients do not appreciate the complexity of the work, so the proposal becomes longer. Every phase is documented. Every technical responsibility is named. Every deliverable is separated and described.
This feels transparent.
Sometimes it is.
But detail and clarity are not the same thing.
A client reading about custom post types, reusable blocks, schema markup, Core Web Vitals and plugin licence management may understand that substantial work is involved.
They may still have no idea what meaningful difference that work will make to their organisation.
The detail proves that the freelancer knows WordPress. It does not necessarily help the client decide.
There is a particular kind of proposal that receives compliments but not approval. The client says it is comprehensive, professional and clearly considered.
Then they choose someone else.
I have learned to become slightly uneasy when the strongest response to an offer is admiration for the proposal itself.
The document has demonstrated effort, but it may not have made the service easier to buy.
What Changed When I Stopped Proposing First
For a long time, I treated the proposal as the place where I worked out what a potential client needed.
We would have an initial conversation. I would listen to their problems, inspect the existing WordPress site and then create a detailed proposal explaining what I believed needed to happen.
The proposal carried a lot of weight.
It had to establish the problem, explain my thinking, define the work, justify the price and persuade the client that it all belonged together.
That is a great deal to ask from a document.
What changed for me was introducing a paid strategy session before creating the proposal.
The session was not simply another deliverable added to the project. It changed what I could propose.
Instead of packaging a collection of WordPress tasks around an assumed website build, the client and I could first examine the problem together.
We could discuss why staff found the website difficult to update, where enquiries were being lost, which content still mattered and what the organisation genuinely needed the website to do.
Sometimes the apparent need for a redesign became a more specific problem with content, structure or internal ownership.
Sometimes the required project became larger.
Sometimes it became smaller.
The important difference was that the eventual proposal no longer had to introduce an unfamiliar solution to a problem I had defined for the client.
We already shared an understanding of the problem.
That made the proposed service much easier to understand.
Package the Journey, Not Just the Production
A useful service package connects four things:
The problem the client recognises, the change they want, the work required and the boundaries of your responsibility.
These elements need to make sense together.
If a client tells you their WordPress website is difficult to manage, they are not initially looking to purchase block patterns, custom post types or staff training.
They want a website their team can manage without every content change turning into a support request or a small act of courage.
The block patterns, content structures and training may be essential. But they are evidence of how you will create that change.
They are not the reason the client wants to buy.
This does not mean hiding the technical work or dressing it up with vague promises.
It means giving the work a clear reason to exist.
What Clearer Packaging Looks Like
Consider a service described as:
WordPress website redesign including discovery, custom design, development, technical SEO, content migration and training.
The description tells the client what work will happen.
It does not tell them why those parts belong together or what kind of problem the freelancer is prepared to solve.
A clearer package might instead be framed as:
Rebuild an increasingly difficult-to-manage WordPress website into a clearer publishing system that staff can confidently maintain.
The service can still include discovery, custom templates, block patterns, content migration, SEO work and training.
The difference is that the client now has a way to interpret those deliverables.
The content audit determines what should be migrated.
The templates create consistency across important page types.
The block patterns give staff safer ways to publish new content.
The training helps the team use the new system without immediately rebuilding the old problems inside it.
The deliverables have not disappeared.
They now form a coherent journey towards an outcome the client understands.
The same principle applies to smaller services.
A WordPress care plan could be described as updates, backups and monitoring. Or it could be positioned as ongoing technical stewardship for an organisation that depends on its website but lacks internal WordPress expertise.
A website audit could be described as a report covering performance, SEO and usability. Or it could help an organisation understand why its existing WordPress site is underperforming before it commits to another expensive rebuild.
A paid strategy session could be presented as a ninety-minute workshop. Or it could give a client enough clarity to make a sensible decision about what their website actually needs next.
The underlying work still matters.
Packaging simply makes its purpose visible.
Clients Still Need to Know What They Will Receive
Packaging services around problems and outcomes does not mean removing detail from your proposals.
Clients still need to understand what you will do, what they will receive, and what is outside the scope.
The difference is the order in which that information makes sense.
When a client understands the problem being addressed and the intended change, the deliverables provide confidence.
Without that context, the same deliverables become items to question, compare and remove.
- Strategy becomes an optional workshop.
- Technical SEO becomes a line item.
- Content migration becomes something the client might handle internally.
- Post-launch support becomes an extra they can remove.
Eventually, the service can be reduced to the only part they clearly recognise.
Building the website.
The scope narrows, but the client’s expectations often do not.
If the finished site fails to improve enquiries, editing or operations, the client may not remember every part they removed from the proposal.
But they will remember who built the website.
A carefully written scope may establish why the result fell short. It will not necessarily preserve the client’s trust.
Clear Packaging Creates an Honest Decision
Clear packaging does not guarantee that a client will buy.
Some clients genuinely want the cheapest possible WordPress website. Some have already decided what they need and only want someone to execute it. Others will reject any service containing strategic work they cannot immediately see.
Clarity may make those clients leave sooner.
That is not necessarily a failure.
A clear package helps both parties recognise the nature of the engagement before expectations become tangled.
It also prevents the freelancer from using ambiguity to win the work.
Broad promises such as “a website that grows your business” may sound valuable, but they leave plenty of room for disappointment. A website alone cannot repair an unclear offer, create a steady supply of useful content or make an organisation follow up its enquiries.
A professional service package does not promise certainty.
It explains the change the work is intended to support, the contribution the freelancer will make and where the client’s own responsibility remains.
That gives both parties a more honest decision to make.
Your Package Should Reflect What You Are Really Selling
Experienced WordPress freelancers often sell judgement while describing production.
We talk about designing templates when the valuable work is deciding which content deserves a template.
We talk about selecting plugins when the valuable work may be recognising that the organisation should not depend on another plugin.
We talk about improving the editing experience when the valuable work is understanding how staff actually publish, approve and retire content.
We talk about maintenance when the valuable work is noticing that a website is becoming operationally fragile before something visibly breaks.
The deliverables are real. They are simply not the whole service.
If the meaningful part of your work is the judgement that shapes those deliverables, your package needs to make that judgement visible.
Otherwise, the client is left comparing the outputs alone.
The Offer Is Part of the Work
Packaging is not something you apply after designing the service.
It is part of designing the service.
A clear package shows the client which problem you are prepared to engage with, what meaningful change the work is intended to create and why the individual parts belong together.
That does not require a clever service name or three neatly priced tiers.
It requires you to understand what the client is actually trying to change.
The practical question is not simply:
“Have I explained everything I will do?”
It is:
“What does the client now believe they are buying?”
If the answer is a collection of WordPress tasks, they will compare those tasks with someone else’s.
If the answer is a clear, credible journey from a problem they understand to an outcome they value, the conversation becomes different.
They may still decide not to buy.
But at least they will be deciding whether they trust you to solve the right problem, rather than whether ten pages should really cost that much.
I write regularly about the commercial decisions behind a sustainable WordPress freelance business. Join The Freelancer’s Edge newsletter for more considered thinking on services, pricing and working with clients.