How do I add a quote request form to my website without paying for a form app?

This page may contain affiliate links from which Blur Studio earns commissions.

A missing quote form costs you leads quietly. Someone lands on your site ready to ask for a price, finds no way to do it without calling, and leaves. The fix doesn't need to be complicated or expensive. If your site already runs on Netlify, or you're willing to move it there, the form itself is free and takes about ten minutes to wire up properly.

The options, from simplest to most capable

Before building anything, it's worth knowing what you're choosing between:

• Do it by hand: a plain "email me at..." line. Free, but every lead has to compose their own email, and plenty won't bother.
• Google Forms: free, works anywhere, but it looks and feels like a survey, not part of your site, and the link usually lives off your domain.
• Typeform or Jotform: polished, flexible, but both charge once you go past a small number of monthly submissions, and you're paying for a tool just to collect a name, email and a few details.
• Netlify Forms: free on every plan if your site is hosted on Netlify, no separate account, no monthly cap on submissions.

For a quote or contact form specifically, which rarely needs more than text fields, a dropdown and maybe a file upload, Netlify Forms covers the job without adding another tool to your stack.

How Netlify Forms actually works

There's no JavaScript, no API key, and no separate signup. You write a normal HTML form and add one attribute:

<form name="quote-request" method="POST" data-netlify="true">
  <input type="hidden" name="form-name" value="quote-request" />
  <label>Name <input type="text" name="name" /></label>
  <label>Email <input type="email" name="email" /></label>
  <label>What do you need a quote for? <textarea name="details"></textarea></label>
  <button type="submit">Request a quote</button>
</form>

At deploy time, Netlify scans your built HTML for that attribute, registers the form, and starts collecting submissions into a dashboard under your site's Forms tab the moment it goes live. There's a real gotcha here worth knowing before you launch: Netlify has to see a real, static copy of the form's HTML in your built output to register it. If your form only renders client-side through JavaScript (common with React, Vue or a single-page app framework), Netlify's build-time scanner won't find it, and submissions quietly go nowhere. The fix is simple once you know it: keep a plain, static version of the form (even a hidden one) somewhere in your HTML output so the scanner has something to detect, then let your JavaScript take over the actual rendering.

Step by step: setting up the form

1. Write the form in plain HTML with the fields you actually need: name, email, phone, job type, and a details field. Add data-netlify="true" to the form tag and a hidden form-name input matching the form's name attribute.
2. Deploy the site. Netlify's build process detects the form automatically; you don't need to register it manually anywhere.
3. Turn on notifications. In your site's dashboard, go to Forms, then Submission notifications, and add your email address (or a webhook URL if you want it sent somewhere else, covered below).
4. Submit a real test. Fill out the live form yourself and confirm the email lands and the submission shows up in the dashboard before you tell anyone the form is live.
5. Add spam protection (the next section) before you publicize the form, not after.

What the limits actually are

Netlify's own documentation sets a few concrete caps worth knowing before you design the form:

• 8MB maximum per form submission, counting all fields and any attached file together.
• One file per input field. If you want a customer to attach two photos, you need two separate file inputs, not one that accepts multiple files.
• 30-second timeout on each submission, which matters if you're uploading a larger file over a slow mobile connection.

For a quote request with a short description and maybe one reference photo, none of this is a real constraint. It becomes one if you're trying to collect large files, multiple attachments, or anything with sensitive personal data attached, where Netlify's own docs point you toward a third-party integration (Very Good Security) rather than handling that itself.

Where submissions actually go

Three places, and you can use more than one at once: the Forms dashboard inside your Netlify site (where every submission is logged and searchable), an email notification to whichever address you set, and an HTTP webhook if you want to push submissions into another system automatically. That third option matters more than it looks: a webhook means you can connect the form to a Slack channel, a spreadsheet via a service like Zapier or Make, or your own script, all without Netlify needing to know what you're doing with the data. I couldn't confirm a dedicated, built-in Zapier integration for Netlify Forms specifically on Netlify's own pages, so if that's the exact path you want, set it up as a webhook pointed at a Zapier "Catch Hook" trigger rather than assuming a one-click Zapier connector exists.

What I'd actually tell you

For a service business collecting quote requests, Netlify Forms is genuinely the right amount of tool. You're not managing a separate login, you're not paying a monthly fee for a handful of submissions a week, and the dashboard is good enough to glance at without building anything on top of it. Where it stops being enough is the moment you need the lead to actually go somewhere a human is already working, your CRM, your team's Slack, your job-scheduling tool, not just an inbox and a dashboard nobody checks after the first month. That's not a Netlify limitation so much as the honest truth about any form tool: the form collecting the lead is the easy 10% of the problem, and routing it to where someone follows up is the part that actually determines whether the lead turns into a job.

When to skip this and use something else

This only works if your site is actually built and hosted on Netlify. If your site lives on Wix, Squarespace, Shopify or WordPress, use that platform's own form tool instead; Netlify Forms has nothing to attach to there. And if you're already paying for Typeform or Jotform and it's working fine, there's no urgency to rip it out just to save a subscription fee that might be small relative to your time.

How I'd approach this

If the form itself is the whole job, set it up yourself with Netlify's own Forms feature; it genuinely doesn't need a developer. Where I come in is the next step: wiring that form so a submission doesn't just land in an inbox, but actually creates a job, a CRM record, or a task someone's accountable for, with no retyping. If you've got a form working today and leads are still slipping through the cracks after it, that routing gap is usually the real problem, and it's a small, well-defined piece of work to fix properly.