Skip to content
Interface language: English
Design / Signal

B2B service pricing on a website: fixed price, range or individual quote?

Show service prices when scope varies: select a presentation model, explain assumptions and create an honest path from pricing to enquiry.

Article language: English

Concept photograph: a woman in a light-coloured blazer opens a small stone chamber beside an opal lamp.
In this article

“How much does it cost?” can be a question about budget, scope or whether further discussion makes sense. “It depends” is true, but leaves the client at a closed checkout without opening hours. On a B2B page show a fixed price, a meaningful range or the pricing method, according to how repeatable the service is. For each option explain what the amount covers and what changes it. Contact can then clarify the task instead of guessing its order of magnitude.

A rigid price without assumptions can also promise work the company does not provide. Pricing design should connect the sales model, copy and enquiry handling. These working frames help decide what to disclose and how; they do not recommend price levels for a particular company.

What question should the pricing section answer?

Start with customer conversations. Do they want to compare packages, obtain an indicative budget or understand billing? Record questions from people who declined too. A lack of contact may result from unknown cost, but also unclear scope or an unsuitable service. Do not automatically attribute it to price.

Choose one primary task for the section. For a simple service it may be choosing an option; for a complex project it may be recognising scale and preparing the right enquiry. In both cases a visitor should learn what they are buying and what step leads to binding terms.

Connect the section to your B2B service-page structure. The guide to B2B service-page structure and evidence (in Polish) discusses how to organise the offer. An amount detached from outcome, limits and responsibility is hard to interpret. Before drawing package cards, write one sentence about each audience and scope. If the sentences are nearly identical, the division needs work.

When should you show a fixed price, range or calculation method?

A fixed price suits a service with repeatable inputs and a clearly bounded result. Describe its limits: number of materials, feedback rounds, language versions or offer validity. When these parameters strongly affect effort, consider a range or an example scope with an indicative price.

Ranges need meaning. Explain which option corresponds to the lower boundary and what leads toward the upper. A very wide range without examples says little. If an honest range cannot be shown, explain the billing unit and cost factors and offer a discussion of the specific task. If adding an interactive estimate, define its calculator assumptions: the reader should see the inputs and how the result differs from a confirmed quote. The guide to calculator assumptions and units (in Polish) discusses how to present them.

A price preceded by “from” also needs conditions. The base option should actually be available on the stated terms. If nearly every order needs a mandatory addition, include it in the presentation. Agree final sales terms with the offer owner rather than creating them independently in the visual layer.

What must appear beside the amount?

Show currency, unit, billing period and the tax presentation appropriate to the offer. If the unit itself is unclear, first decide whether you sell time, an outcome or access to a service, then show its price. The article on choosing a service sales unit (in Polish) discusses those alternatives. The business owner must confirm these details. Also state whether the charge is one-off, recurring, usage-based or includes a separate preparation stage. A client should not have to assemble the full picture from footnotes scattered across the page.

Separate included from optional elements. For example, a design may include file delivery while an additional photo shoot is a separate order. Describe client dependencies such as supplying approved copy. Do not hide them under the ambiguous “materials supplied by the client”.

The article on writing service-page copy (in Polish) explains how scope becomes part of a concrete promise. Apply the same principle to pricing: a clear item name, its boundary and the consequence of change. If a long glossary is needed, improve names before designing the section.

How do you build packages that help people choose?

Each package should solve an identifiable task. Rather than distinguishing options only by screens or hours, describe the client's situation and scope of responsibility. Internal work units are needed for calculations but do not always explain service value to a buyer.

Compare options on the same dimensions. If one description lists support, another meeting count and a third only a slogan, the reader cannot choose. Establish common fields: outcome, inputs, stages, limits and subsequent support. Also show who will find an option insufficient.

A “recommended” label needs a scenario-based reason. State it, for example: for a team needing design and implementation in one scope. Do not call a package most popular without data. Such a label makes a sales claim for which the company should be accountable.

How might a presentation model be chosen in a hypothetical case?

This scenario is hypothetical. A studio prepares materials for industrial companies. Some orders involve editing an existing offer; others require interviews and creating content from scratch. One price per “page of text” conceals the difference and produces incomparable enquiries.

The team separates two scopes. For editing it approves a price at a specified volume and input quality. For creation it shows an indicative range and three factors affecting the quote. Each option states what example document is needed to confirm scope.

It tests several hypothetical orders. People outside the project assign each to an option and identify unknowns. If they choose incorrectly, the studio first improves descriptions. It does not add a third package merely to keep cards symmetrical. Understanding the offer is the criterion.

How should comparison work on a phone and with a screen reader?

On a large monitor packages are easy to place side by side. On a phone a client often sees only one at a time. Use consistent field names and keep explanations close. Check that billing information remains beside the amount in a single-column layout.

Aeneia conceptual photography

If using a real data table, associate cells with headings. Colour or position alone cannot communicate relationships, as the W3C tables tutorial explains. Cards also need readable structure. Do not replace text with icons whose meaning must be guessed.

Check enlargement, contrast and keyboard access to notes. An important limitation cannot appear only on mouse hover. Include pricing in website accessibility acceptance, particularly when a comparison scrolls horizontally or contains expandable details.

For a broader accessibility check, including keyboard use and contrast, see the website accessibility guide (in Polish).

What follows selection of an option?

A button should explain its consequence. “Ask about scope” suggests a conversation; “I order” creates an expectation of placing an order. Match wording to the real process. The following form should preserve the selected option's name while allowing a change and added context.

Ask for information needed to confirm the quote, not the company's entire history. If the count and condition of materials affect price, ask about those. Explain what the team will do after receiving the enquiry. Do not promise a response time the service team cannot sustain.

Walk through the whole B2B contact-form process (in Polish), from price card to actual receipt. An analytics entry or success message does not prove delivery. Test a long message, invalid address and retry after failure too.

How do you assess effectiveness without confusing contact count with quality?

Before changing prices establish a baseline: what enquiries arrive, which information is missing and why scope is later revised. Observe the same questions after publication. A fall in form count alone does not decide whether the change harmed results; fewer contacts may fit the offer better.

Likewise, more button clicks do not mean more sales. The sales team should confirm whether clients understood the pricing model and their expectations matched published terms. Record repeated misunderstandings as specific sentences to improve, not the broad judgement “people do not read”.

When comparing presentations, do not change price, scope and copy simultaneously without identifying the differences. You will not obtain a reliable answer about what helped. A small site may primarily need qualitative conversation analysis. Not every company has traffic sufficient to resolve a quantitative experiment quickly.

Who approves and updates the price list?

Name the rate owner, copy editor and publisher. Even if one person holds all roles, separate their tasks in the instructions. A price change requires checking cards, pages, attachments, forms and language versions. Updating one place does not guarantee consistency elsewhere.

Keep the date and approved scope of the change. Before publication open several representative customer paths. After release confirm the public view outside an administrator session. Also establish what happens when a wrong amount is noticed: who stops further publication and who explains the situation in ongoing conversations.

Include these needs in the premium website brief (in Polish). The design can then support rate changes and options from the start. Manually editing many copies of one price is an organisational cost that eventually matters more than card colour.

Prepare an answer for individual scope too. A client who fits no package should still know whether the company can discuss the task. Describe example reasons for a separate quote and materials needed. Avoid sending everyone to the most expensive option without understanding the work.

The enquiry handler should explain the difference between an extra charge for additional work and a change to a project's underlying assumption. Recording that distinction in the offer limits mismatched expectations during delivery. Also test a reduced scope: can the client knowingly omit an element, or is the package indivisible? The company decides; the page must communicate it clearly.

Before approving packages, check your service comparison on a phone. The guide to service-comparison tables on mobile (in Polish) discusses how to keep the criteria readable. A narrow screen should not separate values from option names. A client should compare terms, not exercise memory while scrolling a table both ways.

When new expectations arise after a quote, a separate process for agreeing scope changes helps. Distinguish a correction within the agreement from extra work requiring cost and timing confirmation. The public price list and later conversation then retain a shared meaning. The article on project scope changes (in Polish) separates a request, its assessment and agreement.

What should pass final acceptance?

Use a short checklist:

  • The pricing model reflects service repeatability and communicates expense scale.
  • The amount has a unit, period and confirmed tax presentation.
  • Base scope, extras and client dependencies are visible before contact.
  • Packages can be compared on the same criteria on phone and large screen.
  • The form preserves the choice and reaches the person preparing the offer.
  • The company has an update owner and a way to correct errors.

To discuss how the offer and pricing are presented on a website, see Aeneia Design.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear