A page for a proposed office building asks visitors to request a leasing pack, book a design consultation, download a planning report and join a newsletter. If all four calls to action carry equal weight, even an interested visitor has to work out what the page is for before deciding what to do.
Give the page one defined conversion goal: an action that takes a particular visitor to an appropriate next step. For an architecture practice, that might be sending a project brief ahead of an initial feasibility discussion. For a developer, it might be requesting verified information about available units. That choice shapes the evidence on the page, the form fields and the way results are measured.
Choose the goal before designing the page
Start with the audience and the decision they are ready to make. A landowner exploring whether a site could accommodate a clinic is at a different stage from a public-sector team preparing to appoint designers. A detailed procurement form would be premature for the first visitor and may not collect what the second needs.
State the goal in full: “Qualified visitors with an identified site submit enough information to arrange a feasibility call.” This names the visitor, the action and the useful outcome. “Generate leads” tells you none of those things, so it cannot guide the page copy or help distinguish useful submissions.
Before settling on the goal, check three things:
- Visitor intent: Does the offer match why someone arrived, perhaps through a healthcare-feasibility advertisement or an invitation to prospective tenants?
- Offer readiness: Can the team provide what the page promises, be it an appointment, a current specification or an information pack?
- Decision value: Does the action lead somewhere useful without asking for more commitment than the visitor is ready to make?
One campaign may need separate pages for different intentions. A developer’s investment enquiry and a resident’s question about construction disruption should not enter the same conversion route just because both concern the same building.
Build the message around the next decision
Make the headline specific enough to qualify interest
The first visible message should say what is on offer and who it is for. “Discuss the feasibility of your healthcare site” gives visitors a clearer reason to stay than “Creating spaces for tomorrow.” Supporting copy can set out the scope: an initial discussion of site constraints, clinical accommodation needs and the information required for a formal feasibility study. A short enquiry cannot confirm planning approval or establish that a scheme is viable, and the page should not suggest otherwise.
Specificity also helps prevent the wrong conversion. If the page offers early-stage design services, a headline that sounds like a promise of a completed cost estimate will attract enquiries based on a mistaken assumption. Analytics may count those submissions as successes; the resulting conversations may go nowhere.
Use evidence that addresses the action's risks
The proof visitors need depends on what they are being asked to do. Before requesting an introductory call, they may want to know about the team’s relevant experience, what the discussion involves and what happens afterwards. Before registering interest in a commercial unit, they need current facts: location, intended use, area, availability status and any limits on indicative information.
Useful evidence might be a clearly labelled completed project, a brief account of how a constraint was resolved or an explanation of the design and approvals process. Be exact about project status. A proposed scheme is not a completed building; a submitted application is not permission granted. Use testimonials and project photographs only with appropriate permission and enough context to avoid implying that another project will achieve the same result.
Give the primary action a clear path
One conversion goal does not mean one button. On a longer page, the primary action can appear near the opening message and again after the main evidence. Keep the wording consistent. “Request a feasibility discussion” at the top and “Send project details” beside the form can describe the same process. “Get an instant assessment” promises something else.
Secondary navigation may still be needed for accessibility, legal information or people who are not ready to submit. Those routes should not compete with the primary action through equally prominent buttons and conflicting offers. A privacy-notice link near a form helps visitors make an informed submission; it is not another campaign goal.
Arrange the page in the order a cautious visitor would assess it:
- Confirm the offer and intended audience.
- Explain what the visitor will receive or what the next conversation covers.
- Address material objections with relevant facts and project evidence.
- State what information is needed for the next step.
- Present the action and explain what follows submission.
That sequence is more useful than putting every project photograph ahead of the form. Images should help visitors understand the building, site or service, not delay the decision the page is meant to support.
Ask only for information the team can use now
Form fields affect whether a visitor acts. For a first feasibility conversation, a name, work email, project type, approximate location and short description may be enough. A full budget breakdown, land ownership documents and a detailed programme can deter suitable visitors when those details have not yet been established. They can be collected later, with proper context.
Other fields earn their place by helping the team route or assess an enquiry. A location field is useful if the practice works only in certain regions. A project-type choice can direct school and workplace enquiries to different specialists. Each field should serve the immediate next step, not a vague wish to gather more data someday.
Say what submission triggers. “We will email to arrange a discussion” is clearer than “Submit.” Do not promise a response time the team cannot consistently meet. If a project may involve sensitive information, request a brief outline rather than confidential documents in an open text field, and explain how contact details will be used. Clear labels, usable error messages and keyboard access matter too: a tidy-looking form is no help if visitors cannot complete it.
Keep architectural claims and visuals aligned
Design imagery can make an unbuilt proposal look finished. Label renders as visualisations and distinguish them from photographs of completed work. If a unit’s area, layout or specification may change during design or approvals, give the figure’s status and date rather than presenting it as final. The call to action should reflect that uncertainty: “Request the latest available plans” is more accurate than “Secure this exact layout” when the scheme remains subject to change.
Technical detail should be selective, not missing. An investor assessing a redevelopment opportunity may need the planning status and proposed use before requesting a pack. A client considering a new school may need to understand the difference between early briefing, feasibility, design and statutory approvals. Put qualifications beside the claims they explain, not in a dense note below the form.
Measure the goal, not just the button
Define the conversion event before launch. A form submission should register only after the form is successfully sent, not when someone opens it or clicks its button. For meeting bookings, distinguish completed bookings from visits to the scheduling page. Test events on mobile and desktop, and exclude internal testing where the analytics setup permits it.
Conversion rate can conceal poor fit. Ten unsuitable enquiries may take more team time than three viable ones. Track a few outcomes beyond submission: contactable enquiries, enquiries that match the stated service or property, meetings held and appropriate next steps agreed. Each measure helps locate a different problem. Many submissions but few suitable projects may mean the offer is too broad. Strong engagement but few submissions may mean the form asks too much or the next step is unclear.
Where volumes allow, review results by traffic source. Someone arriving through a healthcare-site campaign will have different expectations from a visitor who searched for the practice in general. Treat small samples cautiously: a rise from two submissions to three is not convincing evidence that a new layout works better. For more on interpreting website measures, see the blog’s guide to measuring website performance for architecture and property projects.
Revise the page against a defined failure
When practical, change one meaningful element at a time and record why. If visitors repeatedly ask whether a proposed development has planning consent, add a plainly dated status statement near the offer before changing the form colour. If enquiries come from outside the service area, make the geographic scope visible in the headline or supporting copy. If qualified visitors reach the form but abandon it, check field requirements and phone validation before rewriting the page.
For a feasibility page, send a test enquiry using only the details a genuine early-stage client would know. Check that the confirmation explains what happens next, the receiving team gets enough context to respond, and the submission appears once—not several times—in the reporting.