What a Conversion Rate Optimisation Agency Should Check in a New Zealand RFQ Form

Key Insights

• An RFQ form should collect enough information for a viable quotation while allowing buyers to explain what they don't yet know.
• Test uploads, mobile entry and error recovery together, because a working submit button doesn't establish a working enquiry route.
• Measure accepted quotation requests and quoting workload alongside completion rate before removing required fields.

A facilities manager has a specification ready to send to a New Zealand supplier. On a phone, they complete the RFQ form and try to attach the drawing. The upload fails with an unexplained error. After another attempt, the page resets and their description disappears. The supplier records no enquiry, and the buyer sends the job to someone else.

A conversion rate optimisation agency should investigate that whole interaction. The question isn't simply whether a shorter form produces more submissions. It's whether a buyer can send a request the supplier can assess, recover from mistakes and understand what happens next. A form that creates more incomplete enquiries may move work from the website into the quoting team's inbox without improving sales.

Start with the information needed to make the next decision

Sit with the people who assess incoming RFQs. Ask which answers determine whether they can quote, which shape the first response and which can wait. For an equipment supplier, application and approximate quantity may be essential. A precise delivery address may be unnecessary until the buyer confirms a site. The answer depends on the offer.

Trace a few recent requests from submission to quotation. Where did the team need clarification? Which missing details prevented assessment, and which fields were collected but never used? Give each required field a commercial reason. If nobody can identify the decision it supports, review whether it belongs at this stage.

W3C's forms guidance advises asking only for information needed to complete the transaction or process. Applied to an RFQ, that means preserving information required for a credible assessment while postponing details that the buyer can't reasonably supply yet. It doesn't mean stripping a technical request down to a name and email address.

Allow uncertainty where it exists. A buyer may know the problem and operating conditions without knowing the final specification. A clearly labelled “not yet confirmed” option can be more accurate than forcing a guessed number. Give the quoting team enough context to recognise when a technical conversation should precede a formal price.

Make the attachment step dependable

Put accepted file types and size limits beside the upload control before the buyer chooses a file. Use the formats your quoting team can actually review. If the engineering team requires a particular drawing format, explain that requirement and offer an approved alternative route when an initial PDF or image is sufficient for assessment.

Test a valid attachment and deliberate failures. Try an oversized file, unsupported format, interrupted connection and a filename containing spaces or punctuation. Verify whether the explanation tells the buyer what to change. An error code or a red outline alone leaves them guessing whether to compress the drawing, rename it or abandon the request.

On mobile, test selecting a file from the locations buyers use, including cloud storage and a photo library where relevant. Check whether upload progress is visible and whether the final confirmation distinguishes a selected file from one successfully received. A filename appearing on screen doesn't prove the attachment reached the team.

Commercially sensitive drawings need an appropriate handling route. Explain who will receive the material and direct restricted information to the channel your organisation has approved. If an upload fails, a fallback should preserve the request's identity so the separately delivered drawing can be matched to it without exposing it through an unsuitable channel.

Let buyers correct errors without starting again

Show required fields clearly and describe the expected format before submission. A label such as “Project reference” needs context if some buyers won't have one. Avoid making internal terminology a condition of contacting the supplier.

W3C's validation guidance recommends accommodating different input formats and identifying required inputs. Its notification guidance explains how clear error messages can help people locate and correct problems. Those principles apply directly to an RFQ interrupted by a missing field or invalid attachment.

Preserve valid entries when a submission fails. Take the buyer to the relevant error and explain the repair in text, with keyboard and assistive-technology access checked. If two fields conflict, identify the relationship instead of marking both wrong. A buyer should know whether the requested quantity is outside the offer or the form simply expects a different number format.

Keep browser checks and server checks consistent. The interface may accept a file that the server later rejects, or allow a phone format that the CRM refuses. Test the saved record and received attachment, then confirm the quoting team sees the same information the buyer submitted.

Test the form under the conditions buyers face

Use a phone with a smaller screen and an ordinary connection, then complete the request through to receipt. Check whether the keyboard obscures the next control, whether dropdowns can be operated and whether the description field allows enough room to review a technical explanation. Desktop resizing won't reveal every mobile failure.

Test keyboard navigation as a complete journey. The order should make sense, field labels should remain available and focus should reach errors and confirmation messages. If a file control depends on dragging, provide an alternative selection method. Ask the development team to assess the accessible implementation where the issue requires more than a visual correction.

Check the confirmation against the sales process. State that the request was received, explain the next step and give a realistic response expectation the team can meet. Avoid implying that a submission is an accepted order or final quotation. Include a reference when it helps the buyer and supplier discuss the same request.

If the buyer needs to evaluate the product before specifying it, a demonstration before a quotation may be the appropriate route. Keep that choice visible without turning every RFQ into an unnecessary booking step.

Judge the repair by the quotations it enables

Measure form starts, validation failures, upload outcomes and completed requests where your measurement setup permits. Keep personal descriptions and attachment contents out of general analytics. Then connect submissions with the quoting team's assessment: accepted for quotation, clarification needed, outside scope or duplicate.

Compare the rate of accepted RFQs and time spent preparing each quote after a change. Removing a field may raise completions while increasing clarification calls. Repairing uploads may produce fewer visible submissions than a radical redesign but restore high-value requests that previously vanished. Evaluate the result against the supplier's actual workload and opportunity quality.

For a low-volume New Zealand supplier, a handful of sessions won't support a confident test winner. Combine observed failures with confirmed sales records and allow a longer measurement period. Conversion rate optimisation in New Zealand should make the enquiry route measurable without claiming certainty the data can't support.

Give Your Conversion Rate Optimisation Agency a Real RFQ

Take a representative specification and submit it from a phone, including an attachment and a deliberate error. Follow the request into the quoting team's hands, then inspect what they need before responding.

Ask Digital Squad to examine your RFQ journey from first field to received specification, so the next improvement removes a verified obstacle to a viable quotation.