“Generate 50 new projects this year” is a poor website goal for an architecture practice that can take on only six. It gives the website team little direction, too: a request for a small renovation and an inquiry about a complex public building would count equally, though they call for different expertise and capacity. A useful goal identifies the work the business wants, what a visitor should be able to do, and how the team will tell whether the site is helping.
For architects, developers, and property teams, a website usually supports a long decision rather than closing a sale. Prospective clients may first need to check whether a firm handles their building type, works in their location, understands approvals, and can explain its process. Investors and public-sector clients may visit to assess credentials or find relevant project experience. Those tasks call for different goals.
Start with a business constraint, not a traffic target
Before choosing a metric, establish what the organization can deliver in the next planning period. A practice at capacity may need better-fit inquiries, not more of them. A developer marketing one property may need qualified tour requests; a building owner may want occupants to find accurate information online rather than call about routine matters.
Write down the desired work, geographic limits, typical project scale, and who decides whether to proceed. Account for staff available to respond, the number of new commissions the team can absorb, and the point at which a prospect is ready to talk. Otherwise, a goal to “double leads” may simply create an unmanageable queue.
Choose one primary outcome for a defined period, with a few supporting goals. An architecture firm might prioritize inquiries about occupied-building refurbishments in two service areas. It could also help visitors understand its experience in operating buildings and make a first consultation easier to arrange. “More website traffic” is not an outcome unless the business can say why that traffic matters.
Separate outcomes from actions the site can influence
A signed commission may be the business outcome, but it also depends on budget, procurement rules, timing, and conversations away from the website. The site has more direct influence over whether visitors find relevant evidence, understand the next step, and submit a usable inquiry.
A simple goal map keeps those levels separate:
- Business outcome: Win work that fits the practice’s capacity and expertise.
- Visitor task: Decide whether the team has relevant experience and what an initial discussion requires.
- Website action: Read a relevant project account and submit an inquiry with the building type, location, stage, and approximate timeline.
- Measurement: Count qualified inquiries and record which pages or routes assisted them.
That website action is an indicator, not proof that a commission will follow. A property website can measure viewing requests, but signed leases still depend on price, availability, and negotiations. Keeping the distinction clear makes the figures easier to interpret.
Define “qualified” before counting inquiries
Raw contact-form submissions mix prospective clients with suppliers, job applicants, spam, and requests outside the firm’s remit. Decide in advance what makes an inquiry relevant. Criteria might include project type, service area, decision-maker involvement, project stage, and whether the requested services fit the team’s scope. A missing budget need not rule out a legitimate early-stage inquiry.
For a public or institutional practice, a tender notice may need its own category rather than being counted as a direct client inquiry. It can be valuable even if procurement takes months. Record categories consistently so different staff members do not classify the same kind of contact differently.
One workable definition is: “An inquiry from a prospective client or authorized representative about a building type we serve, in a location where we work, with enough detail to identify a next step.” Unlike a conversion rate alone, that definition can be checked against the correspondence.
Establish a baseline before setting a number
Gather three to six months of available evidence, or a full year if demand has strong seasonal patterns. Look at form submissions, calls logged by staff, appointment requests, and which inquiries advanced to a meeting. Analytics can show visits and on-site actions, but offline conversations and referrals often explain what brought someone to the site.
Check the records before calling them a baseline. Have test submissions and spam been excluded? Are calls recorded? Could a repeat visit from an existing client be mistaken for a new prospect? Can the team distinguish a residential design request from an unrelated commercial solicitation? If tracking is incomplete, mark the baseline as provisional rather than treating it as precise.
Suppose a practice logged 24 relevant inquiries in the previous six months, held 12 first meetings, and accepted four commissions. If it can accommodate only two additional commissions in the next six months, aiming for 100 inquiries is unlikely to help. A provisional goal could be 30 relevant inquiries while maintaining the current share that reaches a first meeting. That assumes broadly similar demand and staffing; it is a planning test, not a forecast.
Choose measures that show whether people can make progress
Use a few measures at different points in a visitor’s decision process. A crowded dashboard can obscure the decision the team needs to make.
| Goal | Practical measure | Important limitation |
|---|---|---|
| Attract relevant prospective clients | Qualified inquiries by project type and service area | Not every client uses the form or mentions the website |
| Help visitors assess fit | Inquiries that reference a relevant project or service | A visitor may have read useful pages without naming them |
| Make contact easier | Completed forms and reported contact difficulties | A higher form count says little about inquiry quality |
| Support existing clients or occupants | Recurring questions received by staff | Fewer questions may have causes unrelated to the site |
Page views and time on page provide context, but neither proves understanding. Someone may leave quickly because the answer was clear, or stay because it was hard to find. Compare those figures with the questions people ask in calls and emails.
Set a target that the team can test and revise
Give each goal a timeframe, an owner, a definition, and a review date. “Increase qualified inquiries for school refurbishment projects from four to six per quarter by the end of the next two quarters” is testable if the team already records them. “Become the leading education architect online” has no agreed measure or boundary.
Set the size of the target against the baseline, available capacity, and planned changes. If inquiry quality has never been measured, the first goal may be to classify every incoming request for one quarter. If visitors struggle to tell whether a firm handles permit coordination, clarify that service and monitor the questions that follow rather than promise a percentage increase in traffic.
Keep deliverables separate from results the website team can only influence. A content team can publish accurate service information and check that forms work; it cannot guarantee that a public client will release a tender on schedule. Note major external changes, such as a new office location or a shift in the property market, when reviewing results.
Give each goal a specific site change
A goal without a proposed change is just a reporting exercise. Connect it to a visitor problem and an action the team can control. If prospects regularly ask whether a firm can work while a hospital remains operational, explain the scope and constraints of that experience in relevant project material. If the inquiry form gives staff too little information to respond, add a few purposeful fields without demanding a complete brief from someone still exploring options.
For a commercial property, a reasonable goal might be to reduce inquiries about settled facts, such as access arrangements or available floor area. Keep those details current and easy to find, then track repeated basic questions while checking that the published information remains accurate. For an architecture practice, the useful change may be a clearer account of when the team gets involved in feasibility, approvals, and construction-stage work.
Assign someone to maintain the information. Planning status, availability, project stages, and contact routes can change faster than the next scheduled website review. If details go stale, poor results may reflect a missing update process rather than a flawed goal.
Review results without mistaking correlation for proof
Monthly checks can catch broken forms, missing notifications, or a sudden rise in irrelevant submissions. A quarterly review is often more useful for assessing inquiry quality when projects have long lead times. Apply the same definitions each period and read the inquiries themselves, not just the charts.
If qualified inquiries rise, ask what else changed: website content, referral activity, market demand, or the way staff classify leads. If submissions rise but suitable meetings do not, examine the requests and the expectations set by the pages visitors used. If few people make contact but those who do are consistently well matched, improving the response process may matter more than chasing traffic.
Keep a short decision record with the baseline, target, site change, result, and next adjustment. After a quarter of tracking, for example, a team might find that half its relevant contacts omit the project location. It can add a location field to the inquiry form, then check whether completed forms give staff enough information to route each request correctly.