The lead you never see

A purchasing agent shortlists three or four suppliers and contacts all of them the same afternoon. The ones that are easy to quote get a reply first — and usually the work. The ones that aren't get an email, a phone-tag loop, or nothing at all.

When a request dies on your contact form, there's no record of it. It doesn't land in your inbox as a hard case. It doesn't appear in your CRM as a lost opportunity. It is, quite literally, nothing — which is exactly why it never gets fixed. You can't improve a number you don't have.

Three ways a contact form drops a request

Almost every lost request falls into one of three buckets:

  • Files. The buyer has a STEP model, a multi-sheet PDF, a BOM, or artwork. Your form has three text boxes and a silent size limit. They can't send the thing that makes the job quotable, so they email — or move on.
  • Mobile. Sourcing happens on a phone: the plant floor, a trade-show aisle, between meetings. If the form fights a phone, the request is never sent, and you never learn it existed.
  • Speed. Whoever answers first with a real number usually wins. A request that arrives as an unstructured email, hours later, is a request you're already behind on.

Why your analytics can't see it

Analytics measure sessions and pageviews — traffic that arrived. They don't measure intent that failed to convert. A buyer who gave up on your form looks identical to a casual visitor who was never going to buy. Both are a bounce.

The leak is upstream of your CRM and invisible to your traffic reports. It lives in the gap between "someone wanted to send you a request" and "a complete request reached your desk" — and nothing you currently have instruments that gap.

What to measure instead

If you want the leak to stop being invisible, measure the intake itself, not the traffic around it:

  • Request completion rate — of the people who start a request, how many finish?
  • File-attach success — how often does an upload actually complete, on desktop and on mobile?
  • Mobile submission rate — are phone visitors able to send at the same rate as desktop?
  • Time to first response — how long between a request landing and a real number going back?

The fix isn't a redesign

A prettier homepage doesn't close this gap. The fix is intake built for the request: guided fields that capture the spec as structured data, native upload for large files and CAD straight to storage you control, and routing that puts a complete request where you work within seconds.

That's the one thing worth getting right, because it's the one thing that turns quotable work into quotes instead of silence.