All articles & playbooks
ArticleLead generation5 min read

Give buyers a next step beyond “contact sales”

Someone can be seriously interested and still need an answer before speaking with sales. Your website should help them make that progress.

Start with the decision in front of the buyer.

Look at a product or application page and ask what a visitor is trying to determine. Can the product fit their process? Will it work with existing equipment? What information would a supplier need to recommend a solution?

A general contact button leaves that next step undefined. A more specific action can help the buyer understand what they will receive and help your team prepare a useful response.

Match the action to the question.

Question: Will this fit our existing installation?

Useful next step: Check the compatibility guide or request an application review.

Question: What information do we need before asking for a quote?

Useful next step: Use a project specification checklist.

Offer the smallest useful action.

A next step does not have to be a large downloadable report. A clear comparison, a short demonstration, an application checklist, or a specific answer may do more to help.

Choose one action for the page's main audience. Too many competing choices can make the page harder to use. Keep a direct sales route available for people who are ready.

Be deliberate about asking for an email.

If the material answers a basic product question, consider making it openly available. Removing friction lets the person use it immediately and share it with colleagues.

If you need information to give a relevant answer, explain why. A request for an application review might reasonably ask about the equipment, the application, and the timing. A simple checklist rarely needs that detail.

Tell people what happens after submission. Receiving a resource and joining a marketing list should be separate choices.

Design the response before publishing the button.

Name the person responsible for the request. Decide what they need to know, what they will send, and what response time the team can maintain.

Test the whole route: open the page on a phone, submit the form with test details, check where it arrives, and review the response. A working form is only part of a working handoff.

Check whether the next step helps.

Look at the quality of the requests and the conversations that follow. Ask the team whether the new information makes their response more relevant. Listen for questions the page still leaves unanswered.

Start with one page that matters. Give it one specific next step, make the promise clear, and confirm that your team can keep it.

Want help applying this?

Talk through the situation with Trevor and find out whether a focused project would help.

Talk about your priority