splitforms.com
DEMO REQUEST · GATSBY

Demo Request for Gatsby

B2B SaaS lead capture — qualifies company size, role, use case before the call. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Gatsby
Form.tsxtsx68 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function DemoRequestForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New demo request');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Full name *</label>
32 <input id="name" type="text" name="name" placeholder="Hans Becker" required />
33 <label htmlFor="work_email">Work email *</label>
34 <input id="work_email" type="email" name="work_email" placeholder="hans@company.com" required />
35 <label htmlFor="phone">Phone</label>
36 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" />
37 <label htmlFor="company">Company *</label>
38 <input id="company" type="text" name="company" placeholder="Kraft GmbH" required />
39 <label htmlFor="role">Your role *</label>
40 <select id="role" name="role" required>
41 <option value="">Choose…</option>
42 <option>Founder / CEO</option>
43 <option>Engineering</option>
44 <option>Product</option>
45 <option>Marketing</option>
46 <option>Sales</option>
47 <option>Operations</option>
48 <option>Other</option>
49 </select>
50 <label htmlFor="team_size">Team size *</label>
51 <select id="team_size" name="team_size" required>
52 <option value="">Choose…</option>
53 <option>1–10</option>
54 <option>11–50</option>
55 <option>51–250</option>
56 <option>250+</option>
57 </select>
58 <label htmlFor="use_case">What are you trying to solve? *</label>
59 <textarea id="use_case" name="use_case" placeholder="Replacing Formspree across 14 client sites." required />
60
61 <button type="submit" disabled={status === 'sending'}>
62 {status === 'sending' ? 'Sending…' : 'Send'}
63 </button>
64
65 {status === 'error' && <p>Something went wrong. Try again.</p>}
66 </form>
67 );
68}
500
submissions / mo, free
7
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Gatsby + Demo Requestplatform-specific integration guide

Why Gatsby developers choose splitforms for demo request

Gatsby's static output is excellent for SEO and performance, but static HTML forms have no way to deliver submissions without a backend. Gatsby Cloud offers serverless functions, but wiring SMTP and a dashboard is a substantial project for what should be a simple contact form. The demo request on this page posts from the browser to splitforms — no Gatsby Function, no API route, no build-time configuration. The form works identically whether you deploy to Gatsby Cloud, Netlify, Cloudflare Pages, or any static host.

§ 00Quick answerReact / Next.js · lead capture

Yes — this is the shortest safe path for Gatsby.

Use the React / Next.js snippet on this page, keep the demo request fields visible in your Gatsby UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.

The posted payload contains full name, work email, phone, company, your role, team size, what are you trying to solve?. Required fields are full name, work email, company, your role, team size and what are you trying to solve?.

native gatsby reality

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend.

use case fit

Demo requests are the highest-intent leads a SaaS gets. The form qualifies on company size and use case so the AE walks into the demo prepared, not improvising.

§ 01Demo Request × Gatsbywhy this combination, in 80 words

Built for Gatsby developers who hate operating a backend.

Splitforms is the form backend for Gatsby sites. One POST endpoint, no SDK, no plugin — drop the demo request into a page and ship.

Splitforms is the form backend for Gatsby 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.

✦ what you get on the free plan
  • 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)
§ 02Copy-paste codeReact / Next.js · 68 lines

Drop into any Gatsby project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Gatsby page, and ship. No build-time integration required.

Form.tsxtsx68 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function DemoRequestForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New demo request');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Full name *</label>
32 <input id="name" type="text" name="name" placeholder="Hans Becker" required />
33 <label htmlFor="work_email">Work email *</label>
34 <input id="work_email" type="email" name="work_email" placeholder="hans@company.com" required />
35 <label htmlFor="phone">Phone</label>
36 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" />
37 <label htmlFor="company">Company *</label>
38 <input id="company" type="text" name="company" placeholder="Kraft GmbH" required />
39 <label htmlFor="role">Your role *</label>
40 <select id="role" name="role" required>
41 <option value="">Choose…</option>
42 <option>Founder / CEO</option>
43 <option>Engineering</option>
44 <option>Product</option>
45 <option>Marketing</option>
46 <option>Sales</option>
47 <option>Operations</option>
48 <option>Other</option>
49 </select>
50 <label htmlFor="team_size">Team size *</label>
51 <select id="team_size" name="team_size" required>
52 <option value="">Choose…</option>
53 <option>1–10</option>
54 <option>11–50</option>
55 <option>51–250</option>
56 <option>250+</option>
57 </select>
58 <label htmlFor="use_case">What are you trying to solve? *</label>
59 <textarea id="use_case" name="use_case" placeholder="Replacing Formspree across 14 client sites." required />
60
61 <button type="submit" disabled={status === 'sending'}>
62 {status === 'sending' ? 'Sending…' : 'Send'}
63 </button>
64
65 {status === 'error' && <p>Something went wrong. Try again.</p>}
66 </form>
67 );
68}
ALTPrefer plain HTML? View the universal demo request HTML snippet39 lines
form.htmlHTML
<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New demo request">

  <label for="name">Full name *</label>
  <input id="name" type="text" name="name" placeholder="Hans Becker" required>
  <label for="work_email">Work email *</label>
  <input id="work_email" type="email" name="work_email" placeholder="hans@company.com" required>
  <label for="phone">Phone</label>
  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142">
  <label for="company">Company *</label>
  <input id="company" type="text" name="company" placeholder="Kraft GmbH" required>
  <label for="role">Your role *</label>
  <select id="role" name="role" required>
    <option value="">Choose…</option>
    <option>Founder / CEO</option>
    <option>Engineering</option>
    <option>Product</option>
    <option>Marketing</option>
    <option>Sales</option>
    <option>Operations</option>
    <option>Other</option>
  </select>
  <label for="team_size">Team size *</label>
  <select id="team_size" name="team_size" required>
    <option value="">Choose…</option>
    <option>1–10</option>
    <option>11–50</option>
    <option>51–250</option>
    <option>250+</option>
  </select>
  <label for="use_case">What are you trying to solve? *</label>
  <textarea id="use_case" name="use_case" placeholder="Replacing Formspree across 14 client sites." required></textarea>

  <!-- honeypot — bots fill every field -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">

  <button type="submit">Send</button>
</form>
§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first demo request submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

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.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the demo request into your Gatsby project

Drop the form snippet into a Gatsby 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.

snippettsx
'use client';
  …
</form>
STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now
FROM contact@yoursite.com
New demo request
Maya Iyer maya@studio71.co
Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?
§ 03bSaaS Demo Request Form (Sales Lead Capture)template-specific playbook

The reason this demo request exists.

Webhooks into HubSpot / Salesforce / Close · Chili Piper / Calendly routing.

why it matters

Demo requests cost the SaaS team real money — an AE spends 30-45 minutes on each call. Unqualified demos burn money. The form qualifies on company size, role, use case, current tools, and timeline. ICP-fit leads (right company size, right industry, right pain point) get the AE calendar slot; off-ICP get nurtured via email. The qualifying data also pre-loads the CRM so the AE walks in knowing the prospect's stack and use case — demo close rates climb 30-50% on prepared calls vs cold ones. Most B2B SaaS uses Calendly / Chili Piper for the booking step; the form is the gating layer in front of the calendar.

route the submission
01

Capture firmographic data

Required: name, work email, company, role, team size, use case (1-3 sentences). Optional: current tools, timeline, budget range.

02

Route by ICP fit

Webhook branches on company size and role — ICP-fit leads (e.g. 50+ team, ops/eng decision-maker) book the AE calendar instantly via Chili Piper / Calendly. Off-ICP get nurtured via email instead of burning AE time.

03

Push to CRM

Webhook to HubSpot / Salesforce / Close / Pipedrive with all qualifying fields prefilled. AE arrives at the demo prepared with the prospect's stack and use case in their notes.

§ 03cGatsby production notesnative path · deploy · gotchas

What changes when this demo request lives in Gatsby.

These notes come from the Gatsby platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend. Gatsby v4 had Functions running as Lambda-equivalent serverless routes; v5 removed them entirely. Result: every Gatsby contact form today uses an external service. Splitforms is a drop-in replacement — same shape as Netlify Forms (POST to a URL), same shape as Formspree, but with 5× the free monthly submissions and built-in spam filtering.

deploy notes

Gatsby builds static HTML + JS that deploys to any host: Netlify, Vercel, Cloudflare Pages, AWS Amplify, S3 + CloudFront, Gatsby Cloud (sunset 2024 — migrate). The form posts cross-origin to splitforms regardless of host. Env vars exposed to the browser bundle must be prefixed GATSBY_ — anything else is undefined client-side. The key gets bundled into the JS at build time; lock it to your domain in the splitforms dashboard. For headless Gatsby + WordPress / Contentful setups, the form lives in the React tree, not the CMS — no special CMS wiring required.

Gatsby gotcha

GATSBY_ prefix required for env vars exposed at build time

Gatsby's webpack config only exposes process.env.* variables prefixed with GATSBY_. If you write process.env.SPLITFORMS_KEY, you'll get undefined in the browser bundle. Rename to GATSBY_SPLITFORMS_KEY — and accept that it's bundled into the static JS (lock the key to your domain in the splitforms dashboard).

Gatsby gotcha

Gatsby's <Link> can't wrap a form's submit handler

Gatsby's <Link> component prevents default navigation. If you wrap your form in <Link to="/thanks"> thinking the redirect will fire, it won't — the form's submit event runs, but the navigation is suppressed. Use a hidden redirect input on the form and let splitforms handle the 302.

Gatsby gotcha

SSR + client hydration mismatch on form initial state

If you use useState('idle') in your form and render any state-dependent UI on first paint, Gatsby's static HTML and React's client render can diverge — you'll see a hydration warning. Render the form unconditionally; only render status messages inside the handler-triggered branches.

Gatsby gotcha

Gatsby v5 partial hydration changed how forms hydrate

Gatsby 5 introduced partial hydration via React Server Components. If your form is in a Server Component, the onSubmit handler won't bind. Add 'use client' at the top of the file (or use a separate ContactForm.client.jsx).

PATTERN A

Pattern A — React component (Gatsby v4/v5)

Standard React function component, useState for status. Drop into src/components/ContactForm.jsx and import on any page. Set GATSBY_SPLITFORMS_KEY in .env.production and .env.development. Use the same wiring for the demo request fields on this page.

pattern-a.jsxjsx16 lines
01import React, { useState } from "react";
02export default function ContactForm() {
03 const [status, setStatus] = useState("idle");
04 return (
05 <form onSubmit={async (e) => {
06 e.preventDefault(); setStatus("loading");
07 const fd = new FormData(e.target);
08 fd.append("access_key", process.env.GATSBY_SPLITFORMS_KEY);
09 const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10 setStatus((await r.json()).success ? "ok" : "err");
11 }}>
12 <input name="email" type="email" required />
13 <button disabled={status === "loading"}>Send</button>
14 </form>
15 );
16}
PATTERN B

Pattern B — partial hydration (Gatsby v5)

Gatsby 5's partial hydration mounts only the components marked client-bound. Add 'use client' at the top of the form file so the onSubmit handler binds at hydration time; the rest of the page stays static. Use the same wiring for the demo request fields on this page.

pattern-b.jsxjsx7 lines
01// src/components/ContactForm.jsx
02"use client";
03import React, { useState } from "react";
04export default function ContactForm() {
05 const [status, setStatus] = useState("idle");
06 // ...same body as Pattern A
07}
§ 04Field-by-field rundown7 fields · names you POST

What every field actually does.

Each field below ships in the demo request template — rename, remove, or add your own. Splitforms accepts any name you POST.

nameREQUIRED
TEXT

Full name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Hans Becker
work_emailREQUIRED
EMAIL

Work email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · hans@company.com
phone
PHONE

Phone

Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.

placeholder · +1 415 555 0142
companyREQUIRED
TEXT

Company

Lets you sort enterprise vs SMB inquiries before you reply.

placeholder · Kraft GmbH
roleREQUIRED
SELECT

Your role

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

Founder / CEOEngineeringProductMarketingSalesOperationsOther
team_sizeREQUIRED
SELECT

Team size

Sizing signal — ICP filter without a discovery call.

1–1011–5051–250250+
use_caseREQUIRED
TEXTAREA

What are you trying to solve?

Free-text input — no character limit, expands as the visitor types.

placeholder · Replacing Formspree across 14 client sites.
§ 06Questions9 answered

Demo Request on GatsbyFAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this demo request work on Gatsby?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Gatsby site without server-side code, plugins, or SDKs. Drop the snippet into a Gatsby page or component and submissions land in your splitforms dashboard.
02How much does the demo request cost on Gatsby?
Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.
03Can I customize the fields?
Yes. The template ships with sensible defaults (full name, work email, phone, company…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the demo request?
A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Gatsby as on any other framework.
05Can I send the demo request submissions to Slack or Discord?
Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.
06Will it work on a static Gatsby site?
Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.
07Should I require a work email?
Yes — block free email domains (gmail / yahoo / hotmail) on the email field. Free-email demos are 80% tire-kickers; work email is a basic ICP filter. Use a regex pattern or a real-time validator like ZeroBounce / Hunter to enforce.
08Can I integrate with Chili Piper / Calendly?
Yes — Chili Piper natively pulls form data and routes to the right AE based on territory / industry / company size. Calendly for Sales Teams supports round-robin routing too. Webhook the qualified lead to the booker; the unqualified ones bypass the calendar.
09How do I handle off-ICP demo requests?
Auto-respond with self-serve resources — a recorded demo, free trial signup, pricing page link, customer case studies. Add to a long-term nurture sequence. Don't burn AE time but don't lose the lead either.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a demo request on Gatsby in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Gatsby project.

Get free access key →Read the docs
founders pricing locked in · early access open