Quote Request for Next.js
Lead-capture form for agencies, freelancers, and service businesses. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why Next.js developers choose splitforms for quote request
Next.js Server Actions handle the submit side but still leave you wiring SMTP, spam filtering, file uploads, and a dashboard. splitforms replaces all of that with one <code>fetch('/api/submit')</code> call. The quote request works identically in App Router and Pages Router — it's just a <code>FormData</code> POST, no router-specific magic. Because Next.js pre-renders pages, the form HTML is in the DOM before any JavaScript executes, meaning instant Time-to-Interactive. The honeypot field is invisible to users but catches bots that scrape rendered HTML — especially important for Next.js sites where the form HTML is statically generated and predictable.
Yes — this is the shortest safe path for Next.js.
Use the React / Next.js snippet on this page, keep the quote request fields visible in your Next.js UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.
The posted payload contains name, email, phone, company, budget, tell us about the project. Required fields are name, email, phone, budget and tell us about the project.
Without splitforms, you'd write a route handler at app/api/contact/route.ts, parse the FormData, configure SMTP via nodemailer or Resend (~10 minutes of secrets wrangling), add a Postgres or SQLite store for submissions, and then bolt on rate limiting, a honeypot check, an email-classifier or reCAPTCHA, and webhook fan-out.
Insurance leads are speed-to-quote sensitive — the broker that gets the quote out within an hour of inquiry wins the bind. The form captures line of business and renewal date so the quote process starts immediately.
Built for Next.js developers who hate operating a backend.
Splitforms is the form backend for Next.js sites. One POST endpoint, no SDK, no plugin — drop the quote request into a page and ship.
Splitforms is the form backend for Next.js sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.
- ✓500 form submissions per month
- ✓2 forms on Free; unlimited forms on Pro
- ✓Spam protection (honeypot + classifier)
- ✓Webhooks: Slack, Discord, WhatsApp, custom
- ✓CSV export of all submissions
- ✓Email notifications (CC and BCC on Pro)
Drop into any Next.js project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Next.js page, and ship. No build-time integration required.
Generate, embed, receive.
Three actions stand between you and your first quote request submission. None of them require a backend, a database, or a CAPTCHA library.
Generate a free splitforms key
Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.
Paste the quote request into your Next.js project
Drop the form snippet into a Next.js page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.
Receive submissions
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
The reason this quote request exists.
Speed-to-quote wins · webhooks into AgencyZoom / EZLynx / Applied / Vertafore.
Independent insurance brokers compete with direct carriers (Geico, Progressive, State Farm) and lead-gen platforms (LendingTree Insurance, EverQuote) — the win is speed-to-quote and personal touch. Brokers earn 10-15% commission on auto/home premiums and 50-100%+ on life policies (year-1). The form captures line of business (auto / home / life / business / umbrella / multi-line), current carrier, renewal date, and basic data (driver count / property address / business revenue depending on line). Speed matters: quotes delivered within 4 hours of inquiry close at 35-45%, vs 10-15% for next-day quotes. Webhook into AgencyZoom / EZLynx / Applied Epic so the AMS pre-loads the quote workflow.
Capture line of business
Required: line(s) of business (auto / home / life / business / umbrella / health / multi-line — multi-select), current carrier, current renewal date, primary contact info.
Branch by line
Webhook routes by line — auto/home goes to the P&C team queue, life goes to the life specialist, business / commercial goes to the producer who handles BOPs and umbrellas. Different quote workflows, different carriers.
Quote within hours
Webhook to AgencyZoom / EZLynx / Applied Epic — the AMS pre-loads the quote with current carrier and renewal date. Speed-to-quote under 4 hours triples close rate vs next-day. SMS the quote link via Twilio for the highest urgency leads.
What changes when this quote request lives in Next.js.
These notes come from the Next.js platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
Without splitforms, you'd write a route handler at app/api/contact/route.ts, parse the FormData, configure SMTP via nodemailer or Resend (~10 minutes of secrets wrangling), add a Postgres or SQLite store for submissions, and then bolt on rate limiting, a honeypot check, an email-classifier or reCAPTCHA, and webhook fan-out. Server actions made the wiring slightly tidier in Next 14+, but the operational cost stays the same: a function with a runtime, a database, an outbound email provider, an inbox to monitor, and your name on the spam-filter incident report. Splitforms collapses all of that into a POST to a single URL.
On Vercel, the form works on every plan tier — server actions and client components both run inside the same edge/serverless function. Don't put the splitforms fetch inside a Vercel cron or background function (it's user-facing, latency matters). On Netlify with the Next runtime, server actions need the latest @netlify/plugin-nextjs (≥5.6). For self-hosted / Docker: configure output: 'standalone' in next.config.ts and pass SPLITFORMS_KEY as a runtime env var — never bake it into the image. For static export (output: 'export'), use the client-component path only — server actions aren't supported in static mode.
Don't expose your access key client-side without domain locking
Inlining access_key in a "use client" component makes the key visible to anyone who views source. That's fine if you've enabled allowed-domains in your Splitforms dashboard (Settings → Security) — anyone copying the key from your bundle can't use it from a different origin. If you haven't, use a server action so the key stays on the server.
Server actions need `'use server'` and a real form, not fetch
If you submit to a server action via <form action={myAction}>, Next handles the FormData serialization for you. If you call the action manually with fetch, you have to set the right Content-Type and stringify yourself. Pick one path and stick with it — mixing causes 'Server Action invalid' errors.
App Router + Suspense + useSearchParams = static-prerender bailout
If your form reads ?next=/something to support post-submit redirects, useSearchParams forces the page out of static generation. Either wrap the inner component in a <Suspense fallback={<Skeleton/>}> so the wrapper still prerenders, or accept dynamic rendering for the form route only.
Vercel Edge runtime can't read FormData from `multipart/form-data`
If your route handler uses export const runtime = 'edge' and the form posts as multipart (file inputs), it'll silently miss fields. Use application/x-www-form-urlencoded or remove the edge runtime declaration.
Pattern A — server action (no client JS, key stays server-side)
Form posts to a server action; the action appends the access key from process.env.SPLITFORMS_KEY and proxies to splitforms. Works without JavaScript, key never reaches the bundle. Use the same wiring for the quote request fields on this page.
Pattern B — client component with fetch and inline status
'use client' component using useState for a 4-state status machine. Lets you show a spinner, inline errors, optimistic resets — at the cost of a hydration boundary. Use NEXT_PUBLIC_SPLITFORMS_KEY and rely on splitforms' domain-locking for safety. Use the same wiring for the quote request fields on this page.
What every field actually does.
Each field below ships in the quote request template — rename, remove, or add your own. Splitforms accepts any name you POST.
Name
Greeting + dashboard label so submissions don't all read 'anonymous'.
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
Phone
Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.
Company
Lets you sort enterprise vs SMB inquiries before you reply.
Budget
Filters tire-kickers from real buyers without a sales call.
Tell us about the project
Free-text input — no character limit, expands as the visitor types.
One backend. Every framework.
The same quote request template works on every framework splitforms supports. Pick yours.
Quote Request on Next.js — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship Next.js forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a quote request on Next.js in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Next.js project.