Use a fixed package for a repeatable delivery

A fixed package can suit work with predictable deliverables, preparation and revision boundaries. In our example, a customer sends a product, the studio photographs it against an agreed background and delivers a specified set of edited files. Make those conditions easy to read rather than relying on a large price alone.

Start the card with a recognisable customer need. A label such as “Professional” says little about who should choose it. Do not invent distinctions just to fill three conventional pricing columns. The number of choices should follow meaningful differences in the work your business actually delivers.

Explain the scenario behind a starting price

Put the baseline next to “from” pricing. How many products, what kind of shoot and which deliverables does it cover? If travel, a special setup or additional editing changes the total, make that clear before a customer decides to proceed. Do not publish provisional design figures as real prices.

Identify what can increase the scope, such as shooting days or scene preparation. If the site has no working estimation tool, avoid presenting the card like a calculator. A clearly labelled scope discussion may be more accurate than an interface suggesting an instant final total.

Limit the information needed for a custom quote

When assignments vary substantially, requesting a quote can be appropriate. Explain why a conversation is necessary: location, crew, production volume or delivery format may differ. Ask for enough information to begin that conversation, without making the visitor prepare an entire production plan before making contact.

The illustrative studio might start with product quantity, intended channels and a target schedule. The team can refine the scope afterwards. Avoid promising automatic final pricing or confirmed availability when those decisions depend on an actual review of the requirement.

Read a package boundary

Keep essential conditions out of hidden disclosures

The GOV.UK Design System advises against hiding information needed by most users inside a details component. Applied here, the basic scope, important exclusions and explanation of the total should remain visible beside the price. A disclosure can hold supplementary explanation without becoming the only place to understand the offer.

Read comparisons on a phone. If row labels become detached from package values, individual cards may communicate the options more clearly. State billing frequency and the duration of any recurring service. A business owner should approve commercial conditions; the designer should not invent terms to fill a layout.

Evaluate the quality of the resulting conversation

Give a visitor two different requirements and ask them to choose an option. Then listen as they describe what they think is included. Misunderstood scope needs a better explanation or offer structure, rather than only a different button colour. Record the specific misunderstanding before revising the page.

Connect this work with the service-page content sequence. Our project examples can help discuss visual approaches. During website design, derive the pricing model from real operations and avoid treating a layout as a guarantee of enquiries or sales.

Frequently asked questions

Is it always wrong to omit a public price?

No. A custom quote may suit highly variable work. Reduce uncertainty by explaining the factors affecting scope and the information needed for a useful conversation.

Do we have to offer three packages?

No. One understandable service or two genuinely different choices may be sufficient. Package count should reflect actual delivery differences, not a visual convention.

Sources & further reading

GOV.UK Design System — Details
Web design & developmentLet’s discuss this service