Capture organisation and cause
Required fields: organisation name, registered charity / nonprofit status, cause area (education / health / environment / community / arts / other), and a one-sentence description of what the donation funds.
Form template · Quote request
Sponsorship requests pile into a shared inbox with no structure. This form forces the basics — organisation, cause, amount, deadline — so the review team can say yes or no in one read.
Every template is free and fully editable in the drag-drop builder — swap fields, colors, and the button label before you publish.
No server, API route, or SDK — your Donation Request Form posts straight to one endpoint.
Every submission is emailed to you and saved to a searchable dashboard — spam filtered before it reaches you.
It's plain HTML you own — paste the Donation Request Form snippet, swap in your access key, and ship.
Copy and ship
HTML by default — the same field set also renders as React, Next.js, PHP, and cURL in your dashboard. Every variant posts to the same /api/submit endpoint. Replace YOUR_ACCESS_KEY with the key from your dashboard; that's the only edit.
<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 quote request">
<label for="name">Name *</label>
<input id="name" type="text" name="name" placeholder="Jane Builder" required>
<label for="email">Email *</label>
<input id="email" type="email" name="email" placeholder="jane@example.com" required>
<label for="phone">Phone *</label>
<input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required>
<label for="company">Company</label>
<input id="company" type="text" name="company" placeholder="Acme Inc">
<label for="budget">Budget *</label>
<select id="budget" name="budget" required>
<option value="">Choose…</option>
<option>< $5k</option>
<option>$5k–$15k</option>
<option>$15k–$50k</option>
<option>$50k+</option>
</select>
<label for="project">Tell us about the project *</label>
<textarea id="project" name="project" placeholder="Goals, timeline, anything we should know." 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><p class="splitforms-attribution" style="margin-top:12px;font-size:11px;color:#888;text-align:right">
Powered by <a href="https://splitforms.com" style="color:#888;text-decoration:none" target="_blank" rel="sponsored noopener">splitforms</a>
</p>How to add it
To add a Donation Request Form to your site you need three things: a free splitforms access key, the HTML snippet above, and your key pasted into it. No backend, database, or CAPTCHA library — the form posts to one URL and every submission lands in your inbox and dashboard.
Required fields: organisation name, registered charity / nonprofit status, cause area (education / health / environment / community / arts / other), and a one-sentence description of what the donation funds.
Amount requested (range dropdown or open number), deadline for the decision, and recognition offered (logo placement, social mention, event presence). Those three fields decide whether the request fits the giving budget and timeline.
Webhook submissions into the CSR or community-giving team's inbox — or into a spreadsheet the committee reviews weekly. Auto-respond with the typical decision timeline so the requester isn't refreshing their email hourly.
What's included
Companies and foundations field dozens of sponsorship requests a week — most arrive as a wall-of-text email that someone has to read end-to-end before they can tell if it fits the giving guidelines. A structured request form forces the basics up front: registered charity status, cause area, amount requested, event date, recognition offered. The review team can sort, filter, and reply with a template response in minutes instead of an hour per email. Structured intake saves the review team an hour per request — say yes or no in one read.

Where submissions go
Reply-to is wired to the visitor's email, so one tap on Reply answers them directly — while the built-in honeypot and spam classifier filter out bots before they reach you. Every submission is emailed to your inbox and can forward to a webhook or Slack the moment a visitor hits send.

How SplitForms works
Connect your form, collect every submission, and send data where it needs to go — without building backend infrastructure.

Point your form to your unique SplitForms endpoint. That's it.

We instantly capture and organize every submission in your inbox.

Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.

No credit card required. Set up in under 60 seconds.
Connect & automate
SplitForms works with the destinations you route to and the platforms you build on — from Slack and Sheets to WordPress, Shopify, and Next.js.

Trusted by indie teams and agencies shipping forms worldwide
Testimonials
40 quotes on record — from indie hacks to agency migrations.
“I replaced a Lambda + DynamoDB + SES contact form with six lines of HTML. It took eleven minutes, and the dashboard is better than what I was going to build.”
“We migrated 14 client sites off Formspree in a single weekend. The price is a third of what we paid, the API is more honest, and the spam filter actually works.”
“The webhook payload is signed, idempotent, and well-shaped. It reads like code from a competent team, not a CRUD app held together with duct tape.”
“I stopped reaching for Typeform on small marketing sites. splitforms covers 90% of the use case at none of the bloat.”
“I onboarded our whole agency in an afternoon. The MCP integration meant Cursor literally dropped the form straight into our client repos for us.”
“The free plan gave me 500 submissions before I paid a cent, and Pro is five dollars a month. I've spent more on coffee deciding which backend to use.”
“Spam went from forty junk entries a day to zero, with no reCAPTCHA puzzle ruining the form. The honeypot and time-trap just quietly do their job.”
“Point the form action at one endpoint and you're done. No SDK, no client library, no build step. This is how a form backend should feel.”
“Leads land in Slack the second someone submits, and a copy goes to Google Sheets for the sales team. I wired both up in under ten minutes.”
“I run a static Hugo site on a five-dollar VPS. splitforms gave it a real contact form without me standing up a single server.”
Questions
Ask, don't verify. A checkbox confirming registered-charity status plus the registration number in a text field is enough at intake — your team verifies via the public registry before approving. Don't ask for document uploads on the first form; it kills completion on mobile.
Add a 'request type' radio: cash sponsorship / in-kind donation (product, venue, volunteer time) / both. In-kind requests route to operations; cash to the giving committee. Same form, two completely different approval workflows.
Yes — the cause-area dropdown drives a webhook branch. Education requests go to the education-program lead, environment to the sustainability team, and so on. Each reviewer sees only the requests that match their giving focus.
Most companies promise 4-6 weeks for sponsorship decisions; smaller in-kind requests can be turned around in a week. State the timeline in the auto-responder so requesters know when to follow up — silence is what frustrates them, not a slow no.
Require the registered-charity-status checkbox and the registration-number field. Bona fide nonprofits have a number to hand; commercial sponsors posing as charities usually don't. Combined with splitforms' spam classifier, that catches the bulk of abuse.
Simple pricing
Choose a plan that fits your workflow — from a free form endpoint to full automations, exports, and higher submission limits.
Free forever
For side projects and indie devs.
For agencies and growing products.
Pay $59. 3 years sorted.
No credit card required on Free • Cancel anytime