All articles

What goes into a website quote?

What affects the price and what to check before accepting a quote.

Compare the same job

Suppose two studios quote for a furniture showroom. Both offers say the site includes a catalogue. One studio expects to publish photographs, descriptions and a phone number. The other has included fabric choices, size combinations and a request for a price that carries the selected configuration through to the salesperson. Both could deliver exactly what their proposals describe, yet the customer would be buying very different tools.

Before comparing totals, give each studio the same example. Choose an actual product or service, describe what the customer sees and say what the employee should receive. Ask each studio to mark what is included, what depends on another supplier and what needs a separate estimate. This short exercise exposes differences that a list of page names can hide. It also gives you a useful basis for discussing a cheaper first release.

Count layouts and decisions

A catalogue with a hundred similar items can use one product layout. A small site with a booking calendar, interactive map and customer account may need several distinct layouts and a separate set of rules for each. Ask which screens are designed individually and which pages reuse a layout. Check whether the estimate covers the versions seen on a phone, including the menu, filters, forms and the page shown when a search has no results.

Bring a difficult example to the design discussion. A short service title and a single image may work in any mock-up. A long translated title, a product with no photo and an item sold in packs will show whether the design can cope with the real catalogue. Clarify how many rounds of feedback are included and who can approve a decision. A single agreed set of comments is easier to price than conflicting changes sent by several people.

Follow one piece of content into the finished page

Take a project photograph from the folder where it lives today. Who chooses the final version, checks permission to publish it, writes the caption, prepares the crop and puts it into the site? Repeat the exercise for a service description or a price table. A proposal that includes an editor and a sample project still leaves open the question of who enters the remaining projects. Multiply a small editorial task by the actual number of records before setting the launch date.

For another language, list the work beyond translation. A contact button may need a different phone number, a picture may contain words and a delivery promise may apply to only one market. Agree who signs off the translated pages on screen. It is possible to approve a perfectly good translation in a document and still find that a button breaks onto three lines or leads to the wrong branch.

Put a boundary around each integration

A line in an estimate that says the site will connect to the till leaves several expensive decisions open. Will it read stock for each shop or one total? Does it also send a paid order to the warehouse? Which system can change the price? Write down one ordinary transaction, one cancellation and one incident in which the connection is temporarily unavailable. Ask which of these situations the estimate covers and how the team will demonstrate the result.

Sometimes a supplier will only make a test account available after a contract has been signed. In that case, ask for a small investigation with a defined outcome. The outcome might be a successful transfer of one sample order and a written list of remaining limitations. Agree what happens to the estimate if the supplier cannot provide the necessary access. This separates an unknown technical dependency from a price increase that nobody can explain.

Separate the launch bill from ongoing costs

Request two lists. The first covers work required to open the site, such as design, development, migration, testing and training. The second covers costs that continue afterwards, such as hosting, domain renewal or a paid extension. For every recurring item, record the billing interval, who owns the account and what happens if the subscription ends. Ask whether prices are introductory and who receives the renewal notice.

Build a simple comparison for your own planning. An initial cost of 2,000 euros plus 40 euros a month adds up to 2,480 euros in twelve months, before any other charges. Those figures are an example, not a studio tariff. Use the same time period and tax basis for both proposals. Keep optional support on its own line, especially when one supplier offers a monthly allowance and the other charges for time used.

Spend the first budget on one complete customer journey

If the price exceeds the available budget, pick a journey you can deliver from start to finish. A showroom might launch with a small, well-described collection and a working request form. It could add a room planner once it knows which products draw interest. If the sales team cannot process a request without the selected size and material, those fields belong in the initial release even if an animated gallery has to wait.

Ask for the saving and consequence of each proposed cut. Postponing a translation reduces the audience at launch. Entering products yourself reduces paid editorial work but assigns hours to your staff. Removing error reporting from a stock connection could leave a shop selling unavailable goods. A useful revision of a proposal tells you what will happen differently on Monday morning. A percentage discount alone cannot answer that question.

Agree on the evidence for delivery

Put a short acceptance example beside each major item. For a form, specify which inbox receives an enquiry and what details appear in it. For a catalogue, ask someone in the business to add a product using the delivered editing screen. For a migration, choose several existing addresses that matter to customers and follow each link on the new site. Write down the expected result while everyone still remembers the agreement.

Before signing, ask how a request for extra work will be approved. A one-line record with the requested change, the effect on cost, the effect on timing and the name of the approver is enough for many small projects. Keep the accepted estimate and the handover notes together. When the business needs an extra branch or payment method later, it will be clear which original decisions are relevant and which part needs a new estimate.