Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

How to add a price estimate step to a web design site so enquiries come pre-qualified

When someone writes “How much for a website?” on a contact form, you usually have nothing to go on. You don’t know whether they want a three-page brochure site or a custom build, or how polished they expect it to look. Y

When someone writes “How much for a website?” on a contact form, you usually have nothing to go on. You don’t know whether they want a three-page brochure site or a custom build, or how polished they expect it to look. You book a call, and only then find out the work is much smaller — or much larger — than you guessed.

A short estimate step on your own site can change the shape of those enquiries. Visitors make a few choices, see a rough price range, and only then leave an email. What arrives in your inbox already has a scope attached.

This is not a formal quote, and you should say that clearly. It is orientation, so both sides can tell whether a conversation is worth having.

Decide what actually changes the price

Don’t start with a twenty-question form. For typical website work, a small set of decisions already separates a simple brochure from a heavier build:

  • Project type, for example one-pager, corporate site, or custom.
  • Number of pages or sections.
  • Craft depth — how considered the design and content need to be.
  • Motion and interaction — static, restrained, or more expressive.

You can add more later (CMS, languages, photography), but every extra control makes the step harder to finish. If a factor only rarely moves your price, leave it for the briefing call.

Write down your own ranges for each type, as a low and a high figure, in the currency you actually quote. If you work in Switzerland, show Swiss francs. Use numbers you would stand behind on a first call, not package prices you have never charged.

Show a range, not a single number

A single figure looks like a promise. A band — “indicative range”, “orientation only” — leaves room for the brief. Put one plain sentence under the number: a formal quote follows a short conversation, and this is not a binding offer.

Update the range as the visitor changes options. People understand the trade-offs when the number moves. A static “packages” page is easier to ignore, because it doesn’t react to what they just chose.

You can do this with a modest amount of front-end JavaScript and a rate table you control. A form, a few lookup values, and a clearly labelled output are enough for a first version.

Ask for contact at the end, not at the start

If the first screen is an email field, many people leave before they have seen a number. Let them explore first. When the range is on screen, then ask for:

  • an email address,
  • an optional note — timeline, references, constraints.

That’s enough. You already have the choices they made and the range they saw. Anything else can wait for the reply you write yourself.

Send yourself an enquiry you can actually use

A useful enquiry contains four things: the options they picked, the range they were shown, their email, and the note. Email is a fine place to start. Confirm the address first, so notifications don’t go to a typo or a mailbox you no longer read.

Decide what happens when you don’t want more leads. If you close the form, say so on the page and point people to another way to reach you. A dead form with no explanation feels worse than no form at all.

Put the step where “Get a quote” already is

A separate pricing page that nothing links to will not change your inbox. The useful places are next to your main call to action, or on the contact page itself. If your site is in English and German, show the step in the same language as the page around it.

If you use Webflow, WordPress, Framer or plain HTML, an iframe or a short script is usually enough. Test it on a phone: the range should stay readable, the form should be usable with a thumb, and a thank-you state should appear after send.

What this will not do

It will not replace a proposal. Unusual work — applications, large e-commerce, long retainers — will fall outside a simple band. Some visitors will still write “please call me” and skip the options. That’s fine. The point is to give everyone else a way to arrive already scoped.

You also take on a small trust problem: if the band is wildly below what you would actually charge, you will spend the call walking the number back. Keep the ranges honest, and keep the “orientation only” line visible.

If you want to try this without building the calculator

Disclosure: I built a small tool that does this, Scopeform. It is an embeddable widget. Visitors pick a project type, pages, craft depth and motion, see a non-binding range, and can send an enquiry; you paste one iframe. The free plan lets you set your own rates and currency (CHF or USD), keeps the default colour and Scopeform branding, and stores five enquiries. I mention it here because it is the implementation I actually shipped, not because this article is a review. The steps above work just as well if you build a simple calculator yourself.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.