Finding 1 of 3 · Demo request form
The demo form asks for eight fields before explaining what happens next.
Why it is first: it is high severity, we are confident in it, and the change needs no new development.
ViewHide full finding 1
As it is now
northwind.example/request-demo
Request a demo
1 No word on what the demo involves
Submit 3
Proposed revision Our recommendation, not a tested result
northwind.example/request-demo
Book a 30-minute demo
A product specialist shows you Northwind using your own questions. We reply within one business day.
Request a demo
- Where
- /request-demo, desktop and mobile. The homepage's main button also leads here (Finding 2).
- What we observed
-
- Nothing on the page says what a demo involves, how long it takes, or when someone will reply.
- All eight fields are required, including phone number, company size and “current tooling”.
- The button says “Submit” rather than what it does.
- Why it may matter
- Visitors may hesitate to share a phone number, or to fill in a long form, before they know what they are agreeing to. That could mean fewer completed requests. This is a hypothesis; form completion data or a few observed sessions would test it.
Recommendation
Agree with sales which details they genuinely need before the first call. Then test a shorter form: name, work email and an optional note, plus company size only if sales uses it to route requests. Say above the form what the demo covers, how long it takes and who runs it. Label the button “Request a demo”.
- Priority
- First. It is high severity, we are confident in it, and the change is copy and form settings with no new development.
- Trade-off
- Fewer fields means sales learns less before the call. If sales relies on one detail to route requests, keep that field and ask for the rest in the booking confirmation.
- How to verify
- Compare how many people start and finish the form over comparable periods before and after, allowing for changes in traffic. Ask sales whether lead quality changed.