The visitor has a price question. The form has questions about their company, team size, budget, telephone number and preferred time for a call. It is an impressively thorough conversation with someone who has not yet learned whether the service is remotely suitable.
I think we can make that first exchange kinder.
Not every service can publish a fixed price. Some need a site visit, a specification or a better understanding of the work. The useful question is what the business can explain honestly before asking the visitor to begin that process.
An SEO or AEO brief can start there, with the actual uncertainty rather than an ambition to sound authoritative.
“Can you just put a number on the page?”
Sometimes, yes. Sometimes a number without its conditions would be more misleading than helpful. Establish which arrangement applies with the colleague responsible for pricing and delivery.
If there is a published starting price, explain what it includes and what changes it. If work is quoted individually, describe the factors that determine the quote and what information will be needed. If an assessment has a charge, make that clear before the customer commits to it.
The explanation should help someone decide whether to continue, not merely persuade them to surrender a telephone number.
“Won't that reduce enquiries?”
It might reduce some requests. That observation would need interpretation. A person who learns that the service cannot fit their situation has received an answer. They are not necessarily a lost opportunity that the page should have kept confused for longer.
It might also change the character of the enquiries that do arrive. People may bring better context. Or an explanation may raise a new misunderstanding that needs correcting. Listen to the receiving team and keep the comparison fair before declaring that the new page has transformed lead quality.
I like drafting the first reply before finishing the page. If the reply repeats information the business could have provided earlier, consider putting that information in the answer. If it needs a detail only the customer can supply, explain the detail and why it matters.
“Should this become an FAQ?”
Use the form that makes the answer easiest to understand. A short question and answer may fit. A worked description of the quoting process may be better. Do not hide a meaningful condition in an accordion merely because the template has space for another frequently asked question.
For Google's AI Search features, the official guidance does not require special additional schema. A clear answer should earn its place through its usefulness, not through a promise that a particular format makes an engine cite it.
The service approach described on groas's business page includes SEO and AI search. When briefing that sort of work, give the writer an approved explanation of the price boundary and a person to consult when the boundary changes.
“What belongs on the form afterwards?”
Ask what the next person needs to continue the conversation. Preserve information the visitor has already selected. Avoid requiring a confident answer to a technical question they may reasonably not understand.
Where a photograph or specification is useful, offer a manageable way to provide it. The enquiry should arrive with enough context for a thoughtful reply, while the customer understands what submitting it does and does not arrange.
I would like the page to let someone approach the business without feeling they have applied for an interview. We can explain a price uncertainty without creating a personal interrogation around it.
A good answer may be modest. So may the first form. There is a person at each end of both, which is a damn useful thing to remember while optimising them.
A thought worth keeping?
