Request-for-quote forms for architects: how to ask about budget and the plot without scaring clients away

As an architect, you get two kinds of messages: „How much does a house project cost?” and the real, considered enquiry from someone who already owns land and has a clear budget in mind. The trouble is that a plain contact form — name, email, message — treats them identically. You only get to the phone call after three back-and-forth emails, only to learn the person wanted a 30 sqm extension on a budget that won't cover your fee.

A well-designed request-for-quote (RFQ) form fixes this. Not to turn people away, but so you enter the first conversation already knowing the project type, the size, the plot status and the rough order of magnitude of the budget. The good news: you can ask for all of that without scaring anyone, if you ask in the right order and explain why you're asking.

Why a plain contact form costs you the good projects

An empty message box qualifies nothing. The serious client doesn't know which details are useful to you, so they write two vague lines; the wrong-fit client writes the same. You're left with the exact triage work you wanted to avoid.

An RFQ moves the qualifying work out of your head and into the form. Every field has a clear purpose: to learn whether the project matches what you do, what stage the person is at, and whether it's worth booking an hour-long call. It's not bureaucracy — it's respect for both people's time.

The secret is balance. Too few fields and you qualify nothing. Too many, or questions asked abruptly, and the person closes the page. A good form asks exactly enough for the first call, not for the contract.

The fields that actually qualify an architecture project

For an architecture practice, the fields that truly matter are few and concrete:

• Project type: new house, extension, loft conversion, renovation, commercial space, interior design. One choice from a list tells you instantly whether it's in your lane.
• Town or area: it matters for zoning, height limits and whether you work there.
• Approximate size: desired built sqm or plot sqm. A range is enough.
• Plot status: has land, buying it, or still choosing.
• Permit status: has a planning certificate, has a topographic survey, or starting from scratch.
• Desired timeline and rough budget (more on those two below).

All as lists or buttons, not empty boxes. Ticking is easier than writing, and you receive structured, comparable data.

How to ask about budget without scaring the client

Budget is the field everyone fears — client and architect alike. The answer isn't to skip it, but to ask for it intelligently.

Don't ask for an exact figure in an empty box. Nobody wants to type a number that feels like it becomes the anchor for negotiation. Instead, offer ranges to choose from: under one threshold, between two, above another, plus a „not sure, I'm waiting for your recommendation” option.

Put a line next to the field explaining why you ask: „It helps us propose the right solution — not to filter anyone out.” That completely changes the perception — it no longer reads as a barrier, but as advice.

And make budget optional. The serious client fills it in anyway; the unsure one moves on without abandoning the form. A lead with everything else complete but no budget is still worth far more than an empty „message”.

Plot and permits: the questions that show you know the trade

This is where your form sets itself apart from any other „professional”. A client who has built before knows what a planning certificate, a topographic survey and height limits mean. When they see these questions, they understand they're talking to someone who actually does the work, not a middleman.

A few short questions, all as buttons:

• Do you own the land? Yes / In the process of buying / Still choosing.
• Do you have a planning certificate? Yes / No / Not sure what that is (short explainer link).
• Do you have a topographic or geotechnical survey? Yes / No.

These three questions tell you instantly what stage the project is at. Someone with land and a certificate in hand is weeks from signing; someone „still choosing the plot” is a prospect conversation — useful but not urgent. You handle them differently, and it's good to know before the call.

Field order and what happens after „Submit”

Order matters more than you'd think. Start with the easy, uncontroversial questions — project type, town, size. The person builds momentum by ticking. Leave budget and timeline for the end, once they've already invested a few clicks and are less likely to bail.

Mark clearly what's required and what's optional. Ask for one contact channel — email or phone — not both mandatory. Every extra required field is a reason to abandon.

After „Submit”, don't leave them hanging. A clear confirmation message („We've received your request; I'll reply within X working hours with the first steps”) and an automatic email with what's next make the difference between a lead who waits and one who, meanwhile, writes to another architect.

At MPO Web Studio we build exactly this kind of form — with the qualifying logic shaped around your flow — and we give you a free, pre-built demo before you pay anything. We work fully remotely, nationwide. If you'd like to see how it would look on your site, drop us a message on WhatsApp.