Can a Serious Visitor Reach the Next Step?

Your website does not need to persuade every visitor to contact you. It does need to help the right visitor decide whether a conversation makes sense—and make that conversation reasonably easy to start.

This guide helps a nonprofit, small organization, or mission-driven team review one important visitor journey: from arriving with a real question to completing an inquiry and understanding what happens next. It is not a conversion forecast, an accessibility audit, a legal review, or a substitute for testing with real people. It is a structured way to identify where an otherwise interested visitor may lose orientation, confidence, or momentum.

Executive summary

An inquiry problem is not automatically a traffic problem, a copy problem, or a reason to rebuild an entire website. A visitor may arrive on the right page and still fail to act because:

• the organization is difficult to identify or place;
• the offer is described in internal language;
• the page does not answer the visitor’s decision questions;
• proof is absent, vague, or hard to interpret;
• the call to action is premature or unclear;
• the form asks for too much, gives too little guidance, or fails without useful feedback; or
• the submission provides no clear confirmation or expectation.

Reviewing the full inquiry journey helps separate isolated friction from structural failure. A strong review follows one realistic priority visitor rather than judging every page at once.

Use the seven-part framework in this guide:

1. Recognition: Am I in the right place?
2. Relevance: Is this meant for a situation like mine?
3. Understanding: What is offered, and what decision does it help me make?
4. Trust: What gives me a responsible reason to continue?
5. Action: What is the next step, and what does it commit me to?
6. Exchange: Can I complete the inquiry comfortably and successfully?
7. Expectation: What happens after I submit?

The goal is not to manufacture urgency. It is to make a reasonable next decision easier.

Start with one visitor, one question, and one action

The phrase “our website is not converting” is usually too broad to guide a useful improvement. It mixes several different questions:

• Are the right people reaching the site?
• Are they reaching the right page?
• Do they understand the organization and offer?
• Do they have enough evidence to trust the next step?
• Is the action appropriate for their level of readiness?
• Does the form work?
• Does the organization respond in a way that continues the experience?

Choose one priority journey before reviewing the site. Write it in one sentence:

A [specific visitor] arrives with [a specific question or situation] and needs to decide whether to [take one next action].

For example:

An executive director who is uncertain whether the organization needs a website redesign arrives from a referral and needs to decide whether to begin a planning conversation.

That statement establishes a review boundary. It does not assume the visitor will inquire. It defines the decision the website should support.

Next, identify the likely entry page, the pages or sections the visitor may use, the primary call to action, the inquiry method, and the confirmation or response expectation. Test that path on desktop and a narrow mobile viewport. Use a keyboard as well as a pointer. If possible, ask someone who was not involved in building the site to attempt the journey and explain what they think is happening.

The seven-part inquiry journey

1. Recognition: “Am I in the right place?”

Before evaluating details, a visitor needs to identify the organization and understand the page’s purpose.

Review:

• Is the organization’s name visible and consistent?
• Does the page identify the type of work or resource in plain language?
• Can the visitor distinguish a service, product, educational resource, and case example?
• Does the page indicate who the information is for?
• If the visitor arrives directly from search, email, social media, or a referral, does the page still make sense without the homepage?

Recognition often breaks when a page assumes the visitor already knows the organization. It can also break when a branded or aspirational phrase appears without a literal explanation.

Evidence to inspect: page title, main heading, first paragraph, navigation context, browser title, social preview, and the language immediately surrounding the first call to action.

Possible improvement: add a literal descriptor, name the audience, or clarify the page type before adding more promotional copy.

2. Relevance: “Is this meant for a situation like mine?”

A visitor can understand the topic and still be unsure whether the organization works with people or organizations like theirs.

Review:

• Does the page describe a recognizable situation rather than a generic aspiration?
• Are audience, geographic, timing, maturity, or service boundaries visible where they matter?
• Does the page help someone recognize when the offer is not appropriate?
• Are adjacent services differentiated?
• Can the visitor identify the smallest useful starting point?

Relevance does not require claiming that an offer fits everyone. Clear exclusions can improve trust because they help visitors avoid an unsuitable inquiry.

Evidence to inspect: “who this is for,” service scope, exclusions, representative deliverables, timing language, and links to related or alternative resources.

Possible improvement: replace broad phrases such as “transform your digital presence” with the real decision, obstacle, or deliverable the engagement addresses.

3. Understanding: “What is offered, and what decision does it help me make?”

Visitors need more than a list of capabilities. They need to understand what happens and what useful result the work is intended to produce.

Review:

• Is the offer named in terms a buyer can explain to a colleague?
• Does the page describe the starting information required?
• Are the stages or activities concrete?
• Are deliverables visible?
• Are exclusions and dependencies visible?
• Is timing described without implying certainty before scope is known?
• Does the page distinguish advisory work from implementation?

The useful question is not “Does this page contain enough words?” It is “Can a serious visitor describe the engagement accurately after reading it?”

Evidence to inspect: service summary, process, deliverables, exclusions, timing, representative output, and call-to-action language.

Possible improvement: organize the page around the buyer’s decision and the evidence they will receive rather than around an internal list of skills.

4. Trust: “What gives me a responsible reason to continue?”

Trust is not created by adding more praise. It is created by giving visitors evidence they can interpret.

Depending on the service, useful trust evidence may include:

• a clear explanation of method;
• representative outputs;
• bounded examples;
• prior professional experience with careful attribution;
• source-linked public evidence;
• transparent limitations;
• named responsibility and response expectations;
• privacy or data-handling boundaries;
• accessible design and usable controls; and
• the ability to learn without making an immediate inquiry.

Review:

• Does the page distinguish an example from a client result?
• Are claims specific enough to verify?
• Are source and attribution boundaries visible?
• Are testimonials or recommendations presented faithfully?
• Does the page avoid implying outcomes that depend on factors outside the organization’s control?
• Can the visitor see what the service does not establish or guarantee?

Trust can also decline when a page displays large numbers without context, uses inflated language, or obscures the maturity of a service or product.

Evidence to inspect: case examples, source notes, recommendations, credentials, author identity, process boundaries, privacy guidance, and limitations.

Possible improvement: replace generic credibility claims with one inspectable example, one clear boundary, and one explanation of how the work is reviewed.

5. Action: “What is the next step, and what does it commit me to?”

A call to action should match the visitor’s readiness.

“Buy now” may be inappropriate for a scoped professional service. “Learn more” may be too vague. “Contact us” may not explain what the conversation is about.

Review:

• Is there one primary next action?
• Does the action label describe the decision or topic?
• Is the action visible after the visitor has enough context?
• Does the destination match the label?
• Is there a lower-commitment alternative for someone who is not ready?
• Does the page avoid false urgency, scarcity, or pressure?
• Do repeated calls to action use consistent language?

For an advisory service, a calm inquiry-first action may be appropriate: “Discuss a website decision.” A useful fallback might be another decision guide or a downloadable checklist.

Evidence to inspect: button labels, link purpose, placement, repetition, destination URL, nearby expectation-setting copy, and the availability of a resource-first path.

Possible improvement: use a specific action label and add one sentence explaining what the first conversation will—and will not—do.

6. Exchange: “Can I complete the inquiry comfortably and successfully?”

The form is part of the service experience. It should collect enough information to route and understand the request without asking a new visitor to disclose unnecessary or sensitive material.

W3C’s Web Accessibility Initiative recommends simple, short forms that request only information needed for the process. Its guidance also emphasizes labels, instructions, input validation, and clear notifications. GOV.UK’s service guidance similarly recommends knowing why each question is asked, how the information will be used, and how it will be kept current and secure.

Review:

• Does every field have a visible, descriptive label?
• Are required and optional fields clear?
• Are instructions available before the visitor needs them?
• Does the form ask only for information needed at this stage?
• Is sensitive or confidential material explicitly discouraged when the public form is not an approved channel?
• Can the visitor use the form by keyboard?
• Does the form remain usable at narrow widths and zoomed views?
• Are errors identified clearly and connected to the affected fields?
• Can the visitor recover without losing appropriate work?
• Is there a reasonable alternative contact method?

Do not treat a clean visual design or an automated score as proof that the form works for everyone. Essential interactions require direct testing.

Evidence to inspect: labels, instructions, required indicators, field order, error messages, focus behavior, mobile layout, confirmation behavior, privacy guidance, and fallback contact route.

Possible improvement: remove unnecessary fields, strengthen instructions, make errors actionable, and test the exact transaction in a clean session.

7. Expectation: “What happens after I submit?”

Submission is not the end of the visitor journey. The website should confirm whether the action succeeded and set a reasonable expectation for what follows.

W3C guidance calls for clear feedback about successful or unsuccessful form submission. Success messages help confirm that the task is complete; error messages should explain how to resolve the problem.

Review:

• Does the visitor receive an unmistakable success confirmation?
• Does the page avoid ambiguous states such as a form simply disappearing?
• Is a response window stated only if the organization can support it?
• Does the visitor know who will respond and what the response is likely to cover?
• Is there guidance for urgent, unsuitable, or sensitive requests?
• Does the organization have an internal owner and follow-up process?
• Can the team distinguish a successful submission from a delivery failure?

The public expectation and the internal operating process need to agree. A promise to respond within a stated period is useful only when ownership and capacity support it.

Evidence to inspect: success page or message, error state, email confirmation if used, response-time statement, routing rules, internal notification, and fallback procedure.

Possible improvement: write one clear success message, state the next step conservatively, and assign internal ownership before publishing a response promise.

Three hypothetical decision examples

These examples illustrate how the framework can guide a decision. They are not client results.

Example 1: The credible organization with a buried action

A community organization has clear program information and current leadership details. Its service page answers most visitor questions, but the only inquiry link appears in the footer and says “Contact.” The form then asks for ten fields, including information that is not needed for an initial conversation.

Likely finding: the foundation may be sound. The highest-value work is a focused inquiry-path improvement: a specific call to action, clearer expectation copy, fewer initial questions, and transaction testing.

Not yet justified: a full redesign solely because inquiry volume is disappointing.

Example 2: The multi-audience site with no clear route

A nonprofit serves residents, referral partners, donors, volunteers, and grantmakers. The homepage presents all five audiences in one undifferentiated narrative. Program pages use internal department names. Visitors must understand the organization chart before they can find the right next step.

Likely finding: the inquiry problem may be structural. Audience routes, information architecture, page purposes, and navigation labels need review before isolated call-to-action changes.

Possible next decision: determine whether the current platform and templates can support a revised structure or whether a bounded redesign is warranted.

Example 3: The strong message with a fragile form

A small professional organization has a specific offer, clear scope, and credible examples. On mobile, however, the inquiry form is difficult to navigate. Required fields are unclear, error messages appear only at the top, and keyboard focus does not move predictably.

Likely finding: the offer does not need to be rewritten first. The essential transaction needs direct accessibility and interaction review, followed by repair and human verification.

Important boundary: identifying these signals through this framework is not an accessibility conformance determination.

The inquiry-readiness self-assessment

Choose one priority visitor journey. For each statement, mark Yes, No, or Unknown. “Unknown” is evidence that the path needs inspection, not a failure score.

Recognition

• The page identifies the organization, page purpose, and audience without requiring a homepage visit.
• The main heading and opening explanation use language the intended visitor is likely to understand.
• A service, resource, example, and product are visually and verbally distinct.

Relevance

• The visitor can recognize a situation like theirs.
• Scope and meaningful exclusions are visible.
• Adjacent offers or paths are distinguishable.

Understanding

• The visitor can explain what the engagement or next step involves.
• Required starting information, stages, deliverables, timing conditions, and exclusions are clear.
• Advisory work and implementation are not blurred.

Trust

• Important claims have appropriate context, attribution, or source support.
• Examples are clearly labeled and do not imply unearned client outcomes.
• Limitations, maturity, and data-handling boundaries are visible where material.

Action

• One primary action is easy to find after enough context is available.
• The action label describes the topic or decision.
• A lower-commitment resource path exists for visitors who are not ready to inquire.

Exchange

• The form asks only for information needed at the initial stage.
• Fields have visible labels and useful instructions.
• Keyboard, narrow-screen, zoom, error, and recovery behavior have been directly checked.
• Sensitive or confidential material is discouraged when the form is not an approved private channel.
• A fallback contact path is available.

Expectation

• Success and error states are unmistakable and actionable.
• The visitor knows what happens next and when a response may reasonably occur.
• Internal ownership, routing, and follow-up support the public expectation.

How to interpret the results without inventing a score

Do not add the answers into a percentage and call it an inquiry-readiness score. The items are not equally important, and a single essential failure can matter more than several cosmetic strengths.

Instead, classify the evidence:

Focused improvement

The audience route, offer, and site structure are broadly understandable, but one or two stages contain bounded friction. Examples include weak action labels, excessive form fields, thin expectation copy, or missing trust context.

Structural decision needed

The visitor cannot reliably find or understand the relevant path because audience routes, navigation, content relationships, or templates are failing across several pages.

Specialist review needed

The path raises accessibility, privacy, security, legal, analytics, payment, or platform questions that exceed an ordinary planning review. Route those questions to qualified review rather than implying they were resolved.

Evidence gap

The team is relying on assumptions. The page has not been tested in a clean session, nobody has attempted the journey by keyboard, form delivery is unverified, or the intended visitor’s decision questions have never been examined with real people.

An evidence gap is not proof of a defect. It is a reason to avoid confident conclusions.

A practical 60-minute review

If time is limited, use this sequence:

1. Define the journey: one visitor, one question, one action.
2. Open the likely entry page directly: do not begin from the homepage.
3. Read only what appears before the first primary action: write down what the visitor can know.
4. Follow the action in a clean browser session: note redirects, labels, and expectations.
5. Complete the form with synthetic information: do not submit real confidential material.
6. Repeat with keyboard and a narrow viewport: record interaction and layout problems.
7. Capture the success or failure state: confirm what the visitor is told.
8. Classify findings: focused improvement, structural decision, specialist review, or evidence gap.
9. Choose the smallest next intervention: do not default automatically to redesign.

If a real submission is required to verify routing or delivery, obtain the organization’s authorization first, use a controlled test identity, and document the transaction. A visual inspection alone cannot establish that the inquiry reaches the right person.

What this review can and cannot show

This framework can help an organization:

• define one priority inquiry journey;
• identify orientation, relevance, trust, action, form, and expectation gaps;
• separate bounded friction from possible structural constraints;
• create a clearer evidence request for a designer, developer, content strategist, or specialist; and
• choose a smaller next decision before committing to a rebuild.

It cannot establish:

• a conversion rate or expected increase in inquiries;
• product-market fit, demand, or customer preference;
• accessibility or WCAG conformance;
• legal, privacy, security, or regulatory compliance;
• that form submissions are delivered without transaction testing;
• that an inquiry will become a client; or
• that a redesign or focused improvement will produce a particular business result.

Use analytics, direct transaction evidence, and real-person research where appropriate. Keep observations separate from explanations that have not been verified.

The next decision

If this review reveals a clear, bounded problem, the next step may be a focused correction. If the journey breaks across audience routes, pages, templates, or platform constraints, a broader website decision may be needed.

Wingspan Labs’ Website Decision & Clarity work examines one site and one priority visitor journey to separate structural constraints from focused improvements. The intended output is a decision brief, an evidence-and-friction record, and a prioritized action backlog—not a promised conversion result.

Primary next step: Discuss a website decision.

Resource-first alternative: Read Do You Need a Website Redesign or a Clearer Plan?

Author and source note

Prepared by Kevin Hintzman, MBA, Founder and Principal of Wingspan Labs. The framework reflects Wingspan Labs’ website-planning approach and draws on public guidance from the World Wide Web Consortium’s Web Accessibility Initiative, the U.S. Web Design System, GOV.UK’s Service Manual, and Digital.gov’s plain-language guidance.

References inform the review questions; their inclusion does not mean Wingspan Labs, this guide, or a reviewed website has been endorsed, certified, or found conformant by those organizations.

References

1. World Wide Web Consortium, Web Accessibility Initiative. “Forms Tutorial.” https://www.w3.org/WAI/tutorials/forms/
2. World Wide Web Consortium, Web Accessibility Initiative. “Labeling Controls.” https://www.w3.org/WAI/tutorials/forms/labels/
3. World Wide Web Consortium, Web Accessibility Initiative. “Form Instructions.” https://www.w3.org/WAI/tutorials/forms/instructions/
4. World Wide Web Consortium, Web Accessibility Initiative. “User Notification.” https://www.w3.org/WAI/tutorials/forms/notifications/
5. GOV.UK Service Manual. “Structuring Forms.” https://www.gov.uk/service-manual/design/form-structure
6. U.S. Web Design System. “Form.” https://designsystem.digital.gov/components/form/
7. Digital.gov. “Plain Language Guide Series.” https://digital.gov/guides/plain-language

Continue the decision

Related practical guides.

View all resources

Decision guide

Do you need a website redesign or a clearer plan?

Separate foundational constraints from focused improvements before committing time and budget to a rebuild.

Decision guide

What makes a website accessibility review meaningful?

Understand the scope, methods, evidence, and limitations that distinguish a useful review from a dashboard score.