Form Backend for Small Business Websites

The problem: a form with nowhere to send to

A typical small business site is a set of pages: home, services, about, contact. It may have been built with a site builder, plain HTML, or a framework by a freelancer. None of that includes a receiving service for forms. So businesses end up with one of three workarounds: a form that quietly does nothing, a "please email us instead" note that loses the structure a form provides, or a custom backend built and maintained just to catch messages, which means a server to pay for, update and fix when it breaks.

A hosted form backend removes that third option's burden. The receiving part already exists as a service. Your website form simply sends each message to it, the way the guide for static websites describes in developer terms.

The forms a small business actually runs

Contact form

Name, email and a message. The general front door for questions that do not fit anywhere else.

Quote or request form

Name, phone, the service wanted and a few details about the job. Cleaners, repair services, builders, photographers and similar businesses usually need the details up front so the first reply can already be useful.

Service inquiry form

A form on a specific service page, asking about that service. Consultants and professionals often run one per service, each with its own form in the dashboard, so inquiries arrive already sorted by topic.

Appointment or information request form

A form that collects a preferred date, time or topic so you can respond and arrange things. To be precise about what this is: it collects requests. It is not a booking system, it does not check a calendar, and it does not confirm appointments by itself. You still reply and confirm, as you would with a phone message.

Simple lead capture

A short form, sometimes just an email address, for visitors who want a callback, a price list or a future offer. The submissions collect in the dashboard like any other form.

How it works, in plain steps

1. A visitor fills in the form on your website and presses send.
2. The form sends the answers to your form's address at the service (the endpoint).
3. The service checks the message: is it complete, is it a reasonable size, is it spam? A hidden trap field catches most automated spam, and anything flagged is kept apart.
4. The message is stored first, so it exists even if an email fails on its way to you.
5. It appears in your dashboard, and a copy is emailed to your chosen notification address. On paid plans, a WhatsApp alert is also available as an additional notification channel.
6. The visitor sees a thank-you page, yours if you set one, so they know the message went through.

What the business gets

• Every inquiry in one place. All forms feed one dashboard. You can open a submission, mark it read or unread, filter the list and download submissions as a CSV file for your own records.
• An email for every message. New submissions are emailed to the address you choose and verify, so an inquiry reaches your normal inbox without you having to check a dashboard all day. The dashboard copy remains as the backup.
• Spam kept out of the way. Obvious automated spam is flagged and listed separately, and it is not emailed to you.
• No server of yours to look after. There is nothing to install, patch or restart. The website stays exactly as it is; only the form gains a destination.
• It works with the site you already have. The same approach fits a static HTML site, a site built by an agency, or a modern framework site, because the form only needs the service's address.

What you need

• Your existing website, with a form on it (or a page where a form should be).
• A free Form Backend account, and one form created in it per website form you want to receive.
• An email address you control, verified once, to receive the notifications.
• One small change to the website: the form is pointed at the service's address. If a developer or agency maintains your site, this is the entire technical step:

<form action="https://form-backend-tool.vercel.app/api/forms/YOUR_FORM_KEY" method="POST">
  <label>Your name <input type="text" name="name" required></label>
  <label>Your email <input type="email" name="email" required></label>
  <label>How can we help? <textarea name="message" required></textarea></label>
  <input type="hidden" name="_redirect" value="https://your-site.example/thanks">
  <input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send</button>
</form>

That is genuinely the whole integration for a typical business form. Whoever looks after your site can follow the step by step tutorial, and the documentation covers the details such as thank-you pages and limits. If you are the developer as well as the owner, the live demo on the homepage shows a working form before you change anything.

When this is a good fit

• Your website is mainly pages and content, and its forms exist to start a conversation: contact, quote, inquiry, request.
• You or your team reply to inquiries personally, by email or phone, and mainly need those inquiries to arrive reliably and stay organised.
• You do not want to pay for, or think about, a server whose only job is receiving form messages.
• Your form volume is modest, as most small business inquiry forms are, well within the plan quotas below.

When it is not the right tool

• Forms that must receive files. File uploads are not stored. If customers must send documents, drawings or photos as part of the form, you need a different tool for that form.
• Bookings and payments. This service receives messages. It does not run a calendar, take payments or manage orders.
• Automatic replies to the customer. There is no autoresponder. Your visitor's confirmation is the thank-you page; the reply itself comes from you, which for most small businesses is the point, but it should not come as a surprise.
• A full customer management system. This is not a CRM. Submissions are stored, listed and exportable as CSV, but they are not pushed automatically into other software, because outgoing webhooks are not available. If your process depends on automatic syncing into a CRM or similar system, this will not do that job.
• Very large or programmatic forms. A single submission can be at most 25 KB with up to 50 fields, and a form accepts 10 submissions per 60 seconds from one visitor. Inquiry forms sit far below these numbers; data-collection projects may not.

Pricing, plainly

The Free plan costs nothing and includes 250 submissions per form per month across up to 3 forms, which covers the inquiry volume of many small business websites. If a form regularly receives more, Pro is $12 per month for 2,500 submissions per form per month, and Agency, at $35 per month with 10,000 per form, is aimed at people who build websites for several clients. Those are the live prices and quotas, also shown in the pricing section of the homepage. No discounts or guarantees are being offered beyond that, and any question about fit can go to the support page, which reaches the founder directly.