How to Build a Pricing Page When Every Project Is Different

A useful pricing page does not need one price for every project

You can present pricing clearly without publishing one price for every project. Explain how you price, what makes the scope vary and what a prospective customer can expect after enquiring. The page should help visitors judge whether the work may suit their needs and budget, not suggest that a final quote is possible before you understand the project.

Choose the clearest boundary your work supports. If you deliver the same defined service repeatedly, a fixed package price may be appropriate. If the core service is consistent but some requirements vary, a starting price or indicative range can set expectations, provided you explain what changes the final quote. If the work is shaped too heavily by each brief, say that pricing is quote-led and describe how you will scope it.

For example, a service business might offer a standard package for a straightforward job, while quoting separately when a customer needs additional locations, a more complex approval process or work with another supplier. A visitor can then see why the quoted price may differ without being left to guess whether every request is treated as an entirely new kind of project.

Whatever format you choose, connect the price to the work. Name the details you need to assess, state what the quoted scope includes and identify options or separate work. Then explain the next step: what the visitor should send, whether you will discuss the brief, and how they will receive a proposal. Clear expectations let visitors compare the described scope with their needs before enquiring.

Choose the pricing format that matches how repeatable the work is

Choose the format according to how consistently you can define the work before speaking to a prospective customer. The more project scope changes the final price, the more the page needs to explain the variables and the quoting process rather than imply a single figure applies to everyone.

You can use different formats for distinct services. For example, one service may have defined packages while another needs a tailored quote. Label each service clearly so visitors can see which pricing approach applies to the work they are considering, rather than assuming one format covers the whole business.

Explain the project details that change the price

Replace “every project is different” with the few details that make a meaningful difference to your work. Choose factors you can explain in terms of what your team needs to do, rather than listing every possible complication. A visitor should be able to see which details they already know and which may need a conversation before you can assess their effect.

For example, a website service might explain its main price drivers like this:

• Page types and functionality: A set of standard information pages is different in scope from a booking journey or other bespoke feature, which needs its own design and testing.
• Content and preparation: Existing, usable copy and images may require less preparation than material that needs to be gathered, organised or written. Say what you need the client to provide and what your service can take on.
• Existing website and migration: Moving content from an existing site may involve checking what can be reused and how it should be organised. The effect depends on what is there and what needs to change.
• Connections to other systems: A required connection may affect the work, but its effect might not be clear until you know which system is involved and what information needs to pass between them.
• Locations or decision-makers: If a project covers several locations or needs input from multiple people, explain that this may involve extra coordination or approval.

Keep the distinction between known drivers and open questions clear. You may know that additional page types or locations add work, while the effort involved in a migration or system connection may depend on information gathered during scoping. Do not imply that a factor changes the price in a fixed way if you cannot assess that from the enquiry alone.

Make each point specific to your own process. If your team does not prepare content, connect systems or coordinate across locations, those factors will confuse rather than help. A short, relevant list is more useful than an exhaustive inventory of technical possibilities.

Where useful, show the relationship in plain language: “The number and type of pages affect the design and build work. If your site needs a connection to an existing system, we will discuss what information needs to move before assessing that part of the scope.” This gives visitors a reason for variation without pretending to know the full scope before they enquire.

Make inclusions, options and separate work easy to distinguish

Make it clear what a visitor is being invited to buy. A package, starting point or indicative figure is only useful when its scope is visible beside it, so readers can tell what is included and what would need to be discussed separately.

• Describe the core outcome and deliverables. Use terms a customer will recognise, such as a completed design, a set of agreed documents or a working service. State the main items they will receive and, where relevant, what your business will do to produce them. Avoid relying on internal service names that do not explain the result.
• Set practical boundaries. Clarify limits that materially affect what is delivered: for example, whether the offer covers one location or several, a defined set of pages or content supplied by the customer. Make the boundary specific enough to prevent a visitor assuming broader work is included, without listing every minor task.
• Separate optional additions from the core offer. Label extras as options rather than placing them in a way that makes them appear included. Explain that selecting an option may change the quote, and say whether the customer can decide later if that is how your process works. If an option depends on the project, say so rather than presenting it as available in every case.
• Name likely exclusions or separately scoped work. Include items visitors could reasonably expect to be covered but that are not part of the offer, such as specialist content, third-party services or ongoing support, where those boundaries apply to your work. Be precise about what is outside scope and what can still be discussed as additional work.
• Mark what is not yet confirmed. If the scope depends on an initial discussion, identify the points that will be agreed then, such as the required deliverables or who supplies particular materials. Do not present a partial list as a final specification; distinguish confirmed inclusions from items awaiting clarification.
• Keep the price attached to its scope. Put the relevant package, starting point or estimate next to the inclusions and exclusions it describes. If a figure is an example or baseline, label it clearly so visitors do not mistake it for a different offer. Keep the explanation focused on boundaries that change the customer's expectations, rather than burying the offer in caveats.

Show what happens from the first enquiry to a scoped proposal

Set out what an enquiry starts, what visitors may need to provide and when the price can be set. Describe the steps your business actually follows, and leave out any follow-up or timing promise you cannot deliver consistently.

1. Enquiry: Invite the visitor to say which service they are considering, what they want to achieve and any important constraints. If they have relevant material, such as a brief, drawings or existing content, let them know they can share it, but do not make a finished specification a condition of getting in touch. If you ask for a budget indication, explain that it is optional information, not a commitment.
2. Initial review or conversation: Explain how you decide whether the request is a likely fit and what happens next. This might involve reviewing the enquiry or arranging a conversation, depending on your actual process. Visitors should know if you may need to ask follow-up questions before you can discuss scope or price.
3. Clarify the scope: Set out the details that still need to be agreed, such as the intended outcome, deliverables, existing materials, dependencies and any options that could change the work. Make clear that an initial enquiry gives you a starting point; it does not necessarily establish the final scope. Invite visitors to say what is undecided so they do not feel they need to solve every detail before contacting you.
4. Prepare the proposal: Tell visitors what they can expect once there is enough information to scope the project. The proposal should make the agreed work and price understandable, and identify any assumptions or choices the visitor still needs to consider. Do not suggest a firm quote is possible before the necessary scope has been clarified.
5. Visitor decides what to do next: Explain how they can respond to the proposal, whether they want to proceed, ask for clarification or discuss a change. Keep this description aligned with the way your business handles proposals and any subsequent decisions.

Keep the enquiry form proportionate: ask only for details that help you assess fit or prepare for the next conversation. Use open prompts such as “What would you like the project to achieve?” and allow visitors to explain constraints or uncertainties in their own words. A clear action such as “Discuss your project” or “Request a quote” tells them what they are asking for; the surrounding copy should set expectations about the next step without inventing a response time.

Use this decision tree to choose and assemble the page

Work through the questions separately for each service. The right format depends on how reliably you can define the work before a customer has discussed their project with you.

1. Are the deliverables and boundaries stable from one project to the next?

   • Yes: use fixed packages if you can describe what each includes and where the scope ends. For example, a service with a consistent set of deliverables may suit named tiers. Make the differences between tiers clear, rather than relying on labels such as “standard” and “premium” without explaining them.

   • No: go to the next question. If the work regularly changes after you understand the brief, consider a more flexible pricing route.

2. Can you give a useful, supportable baseline?

   • Yes: show a starting price, and state exactly what that baseline covers. Name the assumptions and boundaries that make it applicable. Explain that requirements outside those boundaries may change the quote, rather than leaving visitors to guess what “from” means.

   • No: continue to the next question. A starting price that does not correspond to a recognisable scope can mislead visitors and make comparisons harder.

3. Do similar projects sit within a range you can explain?

   • Yes: give an indicative range and identify the main factors that move a project towards one end or the other. The range is useful only if it reflects work you can actually scope; explain that the proposal depends on the specific brief.

   • No: use quote-led pricing. Say why the scope needs to be understood first, such as differences in deliverables, requirements or existing materials. Make clear what information you need before preparing a proposal, so “contact us for a quote” is not the whole explanation.

If you offer several services, do not force them into one pricing format. A repeatable service might have packages, while a more variable service uses a range or a scoped quote. Give each service its own route, and make the relevant pricing information easy to find from its page.

Whichever route you choose, finish the pricing page with the same practical checks:

• Define the scope boundaries. State what kind of project the price format applies to and what falls outside it.

• Name the main price drivers. Explain which details can change the work or the quote, using factors customers can recognise when describing their project.

• Separate what is included from what is optional or excluded. Make clear whether an additional requirement is an option, a separate piece of work or something that needs to be assessed during scoping.

• Explain the quoting steps. Tell visitors what happens after they enquire: what information you will review, whether you may need to clarify the brief, and how you will present the proposed scope and price.

• Give one clear enquiry action. Tell the visitor what to do next and what useful information to include. Ask only for details that help you decide whether the project is a fit and what needs to be scoped.

Before publishing, read the page as someone deciding whether to contact you. They should be able to tell which pricing route applies, what it covers, what could change the quote and what happens next.

Review the page before inviting enquiries

Before publishing, review the page as if you were a prospective customer deciding whether to enquire. The price format should reflect how much the work varies, and every stated boundary should be something your business can explain and support.

• Check the pricing format. Does it match how repeatable the service is and how much scope affects the final quote? If the work varies too widely for a meaningful figure, explain why it is quote-led rather than implying that a single price will apply.
• Check what the price covers. Make the relevant deliverables, scope limits and assumptions easy to find beside the price statement. A visitor should not have to infer whether a figure applies to their project.
• Check what can change the price. Name the main project details that affect the quote and say where options, exclusions or work requiring further scoping may apply. Remove boundaries your business cannot consistently honour.
• Check the quoting steps. Make sure the page describes the process your business actually follows, from enquiry through any scope clarification to a proposal. Do not promise a call, assessment or document unless that is part of your normal process.
• Check the enquiry action. Tell visitors what to do next and ask only for information that helps you assess the enquiry. Confirm the form and contact details work, and that the request reaches the person responsible for responding.
• Check whether extra requirements apply. If your customer type or offer may bring specific requirements, confirm the current position with an appropriate official source before publishing. Do not assume that guidance for one situation applies to every quote-led service.

Ask someone unfamiliar with the service to review the page. If they cannot tell what is included, what might change the price or what happens after they enquire, clarify those points before inviting more enquiries.

If you want help building or improving the page, request a website quote.