You are looking for someone to build a website, handle your accounting, or photograph an event. Their work looks good. The service sounds right. Then you get to pricing and find a button asking you to book a call.
You still have no idea whether you are considering a €500 service or a €5,000 service. Before you can decide whether the conversation makes sense, you have to arrange one.
If you run a service business, there can be good reasons for quoting individually. But I think you should give people as much useful pricing information as you can reasonably stand behind. A fixed price is one option. A realistic range, a minimum project budget, or an example with a clearly explained scope can also help.
Your website should give someone enough information to decide whether a conversation about price is worth having.
Why “every project is different” only answers part of it
Every project can be different. That still leaves room to explain what the differences cost.
A website with five service pages, supplied content and a contact form is a different job from a multilingual site with bookings, payments and a CRM connection. Publishing one price for both would make very little sense.
But you can explain which projects you take on, where your work starts, and which requirements change the budget.
The person visiting your website might not be asking for an exact quote. They might simply need to know whether they can afford to work with you.
Those are different levels of certainty. You may need a detailed brief to promise a final price. You should need considerably less information to explain your minimum engagement or describe the kind of budget a particular service requires.
If even an approximate figure would be unreliable, explain why. Tell people what you need to inspect or understand before estimating the work.
“Contact us for pricing” leaves all of that unexplained.
Choose a pricing format that matches how you work
You do not need to force your services into three packages because another website has three pricing cards.
Start with how you actually quote and deliver the work.
| How you sell the service | What you could show | What needs explaining |
|---|---|---|
| A defined service with repeatable scope | Fixed price | Deliverables, limits and additional charges |
| A basic service with optional additions | Starting price | What the starting price buys and what increases it |
| Projects that fall into recognisable groups | Typical range for each group | The assumptions behind each range |
| Highly variable custom projects | Minimum engagement and scoped examples | What makes each example relevant |
| Work that requires investigation first | Assessment process and any assessment fee | What the customer receives and how the later quote works |
You can combine these. A business might publish a fixed price for an initial assessment, a range for implementation, and a separate monthly support fee.
That can be much more useful than pretending every customer needs the same package.
Fixed prices work when the scope is clear
If you sell a defined appointment, workshop or inspection, a fixed price can make the decision straightforward.
The description still matters. Someone needs to know the duration, what they receive, what they must supply and what happens if they need additional work.
For a website service, “landing page” alone is a weak definition. Does it include writing the copy? Connecting a form? Setting up analytics? How many revisions are included?
A price attached to an unclear deliverable creates plenty of room for disagreement later.
Ranges work when you explain what moves the price
A range should help someone locate their project.
Imagine a hypothetical service priced between €3,000 and €6,000. The useful explanation is what puts a project near either end: supplied content versus copywriting, a standard enquiry form versus a booking integration, one language versus several.
Without that explanation, you have given the visitor two numbers and another question.
If your range is so broad that almost any project fits inside it, divide the work into more meaningful categories. A small business website and a custom customer portal deserve separate explanations.
Examples work when the scope is genuinely comparable
An example can show how the decisions add up.
You might describe a project’s deliverables, what the client supplied, which integrations were included, and the resulting cost. A reader can then compare their requirements with something concrete.
Use real projects only when you can share those details appropriately. If you create an illustrative example, label it clearly. An invented example should never look like a completed client project.
Also explain when the price applied. An old project can still demonstrate scope, but readers should not have to guess whether its price remains available.
Be careful with “starting from”
A starting price is useful when someone can actually buy a worthwhile service at that price.
It becomes frustrating when the advertised starting point excludes things a reasonable buyer would assume are necessary.
For example, imagine a hypothetical website package advertised from €800. During the call, the buyer discovers that mobile adjustments, a working contact form and launching the website are all additional charges.
The initial number did very little to help them budget.
There is nothing wrong with a limited service. A single-page website using supplied content can be a perfectly sensible offer. Just describe it accurately and put the important limits beside the price.
Before publishing a starting price, ask:
What they receive
What does someone actually get for this amount?
Who it is for
Who is that version suitable for, and who should look at a larger scope?
A real fit
Can you show a realistic project that was delivered at that price?
What raises it
Which common requirements increase the cost?
Costs elsewhere
Are there unavoidable costs the starting price does not include?
If almost every suitable customer needs a substantially larger budget, a typical range may describe your work more honestly.
Pricing that still misleads people
A number on the page can still send someone into the call with the wrong picture.
Contact us for pricing
It hides the minimum, the range and the reason a number is not available yet.
A starting price that leaves out the basics
Mobile layout, a working form and actually launching the site should not be surprise extras.
A range that fits almost anything
If a small site and a custom portal both sit inside it, split the work into clearer groups.
An example dressed up as a client job
An illustration is fine when it is labelled. It should not look like work you completed.
A number nobody maintains
Outdated pricing creates a problem at the start of the relationship, before any work begins.
Explain what the customer is paying for
A visitor comparing prices also needs to compare responsibility.
For website work, two proposals can both say “business website” while including very different amounts of planning, writing, development, testing and support. One assumes the client supplies finished content. Another includes interviews and copywriting. One connects the website to an existing system. Another leaves the client to figure that out afterwards.
The price makes more sense once those differences are visible. If you are comparing website quotes from the buying side, the same problem shows up in what a small business website actually costs: the number only means something after you know what is included.
This is also where you should explain recurring costs. Hosting, software licences, maintenance and support can affect what the customer pays after launch. State which costs are included, which are optional, and which are paid to another provider.
Make the currency and tax treatment clear, too. Someone should not have to reach the proposal stage to discover that they misunderstood the number on your website.
You do not need an enormous pricing page. You need enough detail for a fair comparison.
What if showing prices scares people away?
It might. The useful question is which people leave and why.
If your minimum project budget is well beyond what someone can spend, discovering that early can save both of you time.
But you should not assume everyone who leaves after seeing a price was a bad prospect. A suitable buyer might leave because the page failed to explain the scope, because a package sounded too restrictive, or because they misunderstood a recurring charge.
Price can expose a communication problem as well as a budget mismatch.
That is why I would put the relevant work, deliverables and explanation close to the number. Give someone a reasonable chance to understand the offer before expecting them to judge its value.
Also, asking about cost does not automatically make someone a difficult client. A serious buyer can have a budget and want to use it carefully. You probably do the same when buying services for your own business.
What about competitors seeing your prices?
Publishing prices does give competitors information. That concern is reasonable, particularly if you sell a tightly defined service that is easy to compare.
You need to weigh that against how much uncertainty you are leaving for potential customers.
You can publish a minimum budget without exposing your entire quoting process. You can explain typical project costs without sharing your margins. You can show what is included without publishing every internal calculation.
A competitor may still advertise a lower number. Your website should make it possible for a buyer to understand whether the offers include the same work.
If the only visible difference is the price, look at how clearly you explain your service. Claims such as “premium quality” will not tell someone whether you write the content, test the booking process, train their staff, or support the launch.
Those details give them something useful to compare.
When the final price should stay private
Some work cannot be estimated responsibly until someone investigates it.
Repairing an unfamiliar website is a good example. Before examining the code, hosting and integrations, you may not know whether the problem is a small configuration issue or something that requires substantial rebuilding.
You should explain that uncertainty. A public repair price could create expectations you cannot meet.
Even then, your website can answer practical questions:
- Is the initial conversation free?
- Is there a paid investigation?
- What does that investigation produce?
- Will the customer receive a quote before further work begins?
- Is there a minimum engagement?
- What information should they send?
Custom pricing becomes easier to accept when the process is understandable.
For large or unusually complex work, the most useful public information may be your typical project scope and how you establish a budget. Publish numbers only where you have a reasonable basis for them.
Put the price next to the service
A dedicated pricing page can help, but the relevant service page should also provide context or a clear route to it.
If someone is reading about a website rebuild, let them find the budget guidance for that work. Do not make them interpret a general price list containing everything from maintenance to custom development.
Keep the explanation close to the action you want them to take. After reading the scope and price guidance, a visitor should know whether to request a quote, book an assessment, or send a brief.
The wording of that next step matters. “Request a project estimate” explains more than “Let’s talk.” If you need information before estimating, say what to include.
And keep the numbers maintained. Assign someone to review them when your services, supplier costs or quoting approach change. Outdated pricing creates an avoidable problem at the start of a relationship.
Measure what happens after the enquiry
Publishing prices may change both the number and the type of enquiries you receive.
Imagine a hypothetical business receiving 20 enquiries and winning four projects. After adding pricing guidance, it receives 12 enquiries and still wins four comparable projects.
That could be useful if it spends less time preparing unsuitable quotes. But it is only an example, and a smaller enquiry count alone proves very little.
You need to look further:
- How many enquiries match the work you want?
- How often is budget the reason a conversation stops?
- How many proposals become paid projects?
- What are those projects worth, and are they profitable?
- How much time goes into quoting and follow-up?
If enquiries fall and suitable projects also disappear, investigate. The price presentation may be unclear, the offer may be uncompetitive, or something else may have changed.
Give the comparison enough time to include your normal sales cycle. A quiet week after editing a page is weak evidence, especially for a business with relatively few enquiries.
Start with the service you can explain
You do not need to publish a complete price list in one go.
Choose one service with a reasonably predictable scope. Explain what it includes, choose a pricing format you can support, and make the additional costs clear. Then review the questions people ask and the projects that follow.
For more variable work, explain the quoting process and use examples where they help.
Final takeaway
Publish the pricing information you can stand behind, and explain what you still need to know.
Read your service page as someone who has never hired you. Can they work out whether the service is relevant, whether the likely budget is within reach, and what happens after they contact you? Those are useful questions for your website to answer before the first call. If you are the one comparing website quotes, start with scope and recurring costs in how much a small business website costs, then decide whether the conversation is worth booking.
Frequently asked questions
Should every service business publish exact prices?
Exact prices make sense when the scope is sufficiently defined. For variable work, a realistic range, minimum engagement or scoped example may be more useful. If investigation is necessary, explain the process and any assessment fee.
Can I show prices if every project needs a custom quote?
Yes. Explain that the public figures are guidance based on stated assumptions and that the final quote depends on agreed requirements. Give readers enough scope detail to understand whether the guidance applies to their project.
Will publishing prices reduce enquiries?
It can reduce enquiries from people whose budgets do not fit, but it could also discourage suitable buyers if the offer is poorly explained. Assess the quality and outcome of enquiries alongside their number.
Is a starting price better than a price range?
A starting price works when the entry-level service is clearly defined and genuinely available. A range is often more informative when suitable projects regularly vary in scope. Explain the inclusions and cost drivers whichever format you choose.
What if I cannot publish any reliable price yet?
Explain how you calculate the quote, what information you need, whether investigation costs anything, and when the customer will receive a price. That gives them a clearer basis for contacting you while you work out whether useful public pricing is possible.
