“We need a new website because the current one does not bring leads” is a common starting point. Before committing to a redesign, define what counts as a useful inquiry and how the business will know if the new experience changed anything. Without a baseline, a launch can feel successful because it looks better—or unsuccessful because total form submissions did not rise—even when the quality or source of conversations changed.
An owner in a small-business forum asked how to turn website traffic into serious inquiries and described possibilities such as clearer positioning, focused service pages, examples, and an easier contact process (discussion). This is a self-reported discussion, not a controlled case study. It demonstrates the questions business owners ask, but cannot establish that any one site element causes qualified leads.
Define “qualified” with sales and delivery teams
Agree on the traits that make an inquiry appropriate: service need, location, budget range, timeline, decision role, or fit with the company’s actual capabilities. Avoid defining quality only as “someone who can afford us.” The business may value early-stage conversations, a new market, or a smaller first engagement.
Use a simple classification that staff can apply consistently: qualified, potentially qualified, and not a fit, with a reason. For example, a lead may be outside the service region or looking for a service the business does not offer. Keep free-text notes for nuance. Review a sample of inquiries together so sales, marketing, and operations classify them similarly.
Do not collect sensitive details merely because they might be useful later. Limit access to lead data and keep a retention policy appropriate to the business and applicable privacy obligations. A baseline should improve decision-making without creating a spreadsheet that stores unnecessary personal information. Where possible, report aggregated patterns rather than sharing individual inquiry contents across teams.
Measure the current path
For a suitable period, record unique inquiries, qualified inquiries, inquiry source, landing page, device, service requested, and eventual next step. If the company closes sales slowly, track stages such as contacted, meeting held, proposal sent, won, and lost. Use consistent definitions and check that form and call tracking work.
Calculate rates with clear denominators. Qualified inquiries per 100 sessions is different from qualified share of all inquiries. Neither is a complete measure of business success. Include response time and follow-up, because a delayed reply can waste a good inquiry regardless of website quality.
Segment where data permits, but avoid overinterpreting tiny samples. A handful of leads cannot support a confident channel comparison. Note seasonality, staffing changes, promotions, and shifts in ad spend. If traffic is low, combine counts with structured review of inquiry content and customer conversations.
Record what the current site promises
Save the main page, service pages, contact form, and key analytics snapshot before changes. Note which queries or campaigns drive traffic and where inquiries begin. Capture common customer questions and objections. This makes it possible to distinguish a site change from a change in marketing, pricing, offer, or sales process.
Check whether existing pages accurately describe scope, audience, process, proof, and next steps. A redesign can improve how those facts are organized, but it cannot repair an unclear offer or a weak follow-up process by itself. If a service has no clear distinction or the company cannot explain who it serves, resolve that positioning question before choosing page layouts.
Set a realistic measurement plan with the redesign team
Before launch, agree on the primary outcome and guardrails. A primary outcome might be qualified inquiry completions. Guardrails could include total inquiry volume, form completion, lead quality, response time, and accessibility issues. Define the measurement window and how the team will annotate campaigns or operational changes.
If the site receives enough traffic, test focused changes where feasible. A full site rebuild often cannot be randomized cleanly, so use an annotated before-and-after comparison and state its limits. If the result changes, investigate concurrent factors rather than attributing everything to design. If it does not change, review whether traffic quality, offer, sales handling, or market conditions dominate.
Agree on who owns the measurement after launch. Someone should verify analytics, maintain lead classifications, and bring sales feedback into regular reviews. If the team only checks results once at launch, it may miss a delayed effect or a deterioration in lead quality. Keep a brief changelog of campaigns, site releases, staffing shifts, and pricing updates so later comparisons have context.
Use the baseline to make better decisions
A baseline is not a promise that the site will improve inquiries. It is a way to learn whether the business is attracting suitable visitors, whether they understand the offer, and where a digital experience may be adding friction. It also gives the project team a concrete brief instead of a vague request to “make the site convert.”
One founder’s forum discussion can prompt the right questions, but your own data and customer conversations should shape your answer. Keep the baseline simple enough that the team will maintain it. Measure inquiry quality and business follow-through, not just form counts or aesthetic approval.