Should contractors show prices on their website? A field guide

Start with what you can know before visiting the property. A fence contractor can ask about material, height, approximate run lengths, and gates. Those answers describe a substantial part of the intended project. They do not necessarily confirm every measurement, access condition, or item of removal work. The price presentation should reflect that difference instead of treating all submitted details as verified facts.

Divide your offer into parts that are repeatable and parts that require review. A standard product choice may follow established rates. Difficult access or unusual ground conditions may need further information. Write down how your company currently handles those items. If the rules are not settled internally, a website cannot resolve the uncertainty simply by displaying an amount with more digits.

For each service page, choose a result that matches the information available. It could be a package price, a range, a starting amount, or a request for a detailed estimate. Explain what the visitor will receive before asking them to work through project questions. This makes the promise of the page consistent with the final screen and gives your team a clear starting point for follow-up.

A fixed package is easiest to understand when its boundaries are visible. State the product, dimensions or quantity, included equipment, and included work. A fence panel package is not automatically the same thing as a completed fence installation. If installation is included, define its assumptions. If delivery or removal is separate, do not rely on the customer to infer that from an unfamiliar product name.

Think through the choices that change the package. A different height, additional gate, or upgraded finish may create a different configuration. Your calculator should use the relevant rates and show the selected scope. It should not keep a base package label while silently adding work that the customer cannot identify in the summary. The amount and the description need to tell the same story.

Use fixed pricing where your process supports it, without turning every service into a supposedly standard package. If a selection falls outside the defined offer, provide a clear next step. That might be a conversation about a custom requirement. The customer should understand why the standard result no longer applies, and your staff should receive the details already entered so the discussion does not start over.

A range communicates an estimate with room for defined uncertainty. Explain which factors can move the result within or beyond that range. For a fence project, the submitted lengths may be approximate and the ground or access conditions may need review. The range should come from your pricing approach and configured assumptions. It should not be an unexplained cushion added to avoid describing what is unknown.

A starting price describes the entry point for a stated scope. It needs a recognizable baseline: material, quantity, equipment, and included work. Without that baseline, visitors cannot tell whether the amount is relevant to their property. If almost every meaningful selection adds scope, show the configured result clearly rather than continuing to emphasize only the original starting figure throughout the experience.

Place qualifications near the estimate. Identify what has been selected, what is included, and what remains to be verified. Avoid using a long, distant paragraph as the only explanation of an important limitation. Your salesperson should be able to see the same assumptions in the request and PDF. That consistency matters when a customer returns later and asks why a revised estimate differs from the first one.

Use the fence installation example to build a product comparison. These are demonstration scenarios, not customer jobs. First choose the same material for the runs. Then compare a version with a different street-facing material while keeping the side and rear selections unchanged.

Review the selected heights and gates in each version. A request with a driveway gate is not the same scope as one containing only fence runs and a walk gate. The summary needs to preserve those choices so a homeowner can understand why two estimates differ. A single headline rate cannot explain every combination.

Next, look at removal, slope, and access questions. Changing the desired material is a product decision; reporting difficult equipment access is information about the jobsite. Both can affect the configured estimate, but they require different follow-up. Your estimator can confirm a product preference in a conversation while site conditions may require inspection.

The visual layout does not establish surveyed boundaries or verify measurements. Use approximate lengths as inputs with an appropriate explanation. If the homeowner cannot answer a site question, make that uncertainty visible. A completed field should not quietly turn into a confirmed fact in the PDF or the estimator's request.

Contact details belong at a point that matches the promise of the page. If you offer to email a saved estimate, explain what the customer will receive. If the amount appears only after the contact step, say so before the visitor starts making selections. The relationship between the requested information and the result should be easy to understand without searching for an explanation.

You can also collect project details without showing an amount. This can be appropriate when the scope needs personal review, but the page should describe the result as a request for an estimate. Do not label the opening button as an instant price if the final screen contains only a confirmation that someone will respond. Clear wording matters as much as the order of fields.

Limit questions to information you will use. A preferred time frame might help with follow-up, while a technical detail the homeowner cannot verify may belong in a later conversation. Review what your staff actually needs to take the next step. For unusual projects, provide a way to explain the exception instead of requiring the visitor to force it into a standard set of options that misrepresents the job.

Prepare the result around four statements your estimator can recognize later:

• Selected: name the material, height, runs, gates, and options.
• Included: identify installation, removal, haul-away, or other work only when it belongs in the selected scope.
• To verify: identify approximate measurements and site assumptions.
• Next step: explain what your company will review after the request.

For example, an illustrative scope note could say: “Estimate based on the selected fence runs and gates. Removal is included only where selected. Measurements and access conditions need confirmation before the final project scope is agreed.” Adapt the wording to your process; this is not a universal promise about every fence package.

Offerandum sends the selected configuration with the request and PDF. The PDF quote feature supports keeping a record of what was chosen. Ensure the document preserves the same meaning as the on-screen estimate.

Ask the estimator to read a trial request without opening the calculator. They should be able to tell which work is included and what remains unknown. If they cannot, fix the scope description before adding more required questions. The objective is a request that can be discussed accurately, not just a longer record.

Use a configured price when the submitted choices define the priced scope. Use a range when you can describe the scope but specified assumptions still need checking. Use a starting price when you are presenting a defined entry package. Use an estimate request without an amount when the information is insufficient to price the work yet.

These choices can coexist across services. A standard product package and a site-dependent project do not need identical result screens. What matters is that the opening promise matches what the visitor receives and that your staff can explain the amount or the remaining review.

After launch, note recurring misunderstandings. If customers think tear-out is included when it is not, improve the inclusion statement. If they cannot provide a measurement, review how the question is asked. Those observations identify a specific change; they do not establish a guaranteed increase in lead volume.

For a broader comparison of the information collected, see instant quote form versus contact form . If your next task is implementation, compare the ways to add a calculator to your website . Decide what the estimate means before deciding where to put the code.

Share how your company estimates work to plan a calculator with the right scope and pricing presentation.