splitforms.com
CONSULTATION REQUEST · TAILWIND CSS

Consultation Request for Tailwind CSS

Discovery-call request with service, budget, and timeline qualification. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Tailwind CSS
form.htmlhtml27 lines
01<form action="https://splitforms.com/api/submit" method="POST">
02 <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03 <input type="hidden" name="subject" value="New consultation request">
04
05 <label for="name">Full name *</label>
06 <input id="name" type="text" name="name" placeholder="Tomás López" required>
07 <label for="email">Email *</label>
08 <input id="email" type="email" name="email" placeholder="tomas@example.com" required>
09 <label for="phone">Phone *</label>
10 <input id="phone" type="tel" name="phone" placeholder="+1 555 0184" required>
11 <label for="topic">Topic *</label>
12 <select id="topic" name="topic" required>
13 <option value="">Choose…</option>
14 <option>General inquiry</option>
15 <option>Strategy</option>
16 <option>Financial planning</option>
17 <option>Legal advice</option>
18 <option>Other</option>
19 </select>
20 <label for="details">What do you need help with? *</label>
21 <textarea id="details" name="details" placeholder="Be specific so we can match you with the right advisor." required></textarea>
22
23 <!-- honeypot — bots fill every field -->
24 <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
25
26 <button type="submit">Send</button>
27</form>
500
submissions / mo, free
5
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Tailwind CSS + Consultation Requestplatform-specific integration guide

Why Tailwind CSS developers choose splitforms for consultation request

Tailwind CSS handles the styling side — utility classes for layout, spacing, colors, and responsive breakpoints. But styling a form is only half the job; you still need email delivery, spam filtering, webhook routing, and storage. The consultation request on this page combines Tailwind's utility-first CSS with splitforms' backend API: Tailwind makes it look right, splitforms makes it work. No form library needed — just standard HTML inputs with Tailwind classes, posting <code>FormData</code> to one endpoint. Works in Next.js, React, Vue, Astro, or any framework that supports Tailwind.

§ 00Quick answerHTML · lead capture

Yes — this is the shortest safe path for Tailwind CSS.

Use the HTML snippet on this page, keep the consultation request fields visible in your Tailwind CSS UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains full name, email, phone, topic, what do you need help with?. Required fields are full name, email, phone, topic and what do you need help with?.

native tailwind css reality

Tailwind is a styling layer — it has no opinion on form submission, networking, or backend.

use case fit

Discovery-call request with service, budget, and timeline qualification.

§ 01Consultation Request × Tailwind CSSwhy this combination, in 80 words

Built for Tailwind CSS developers who hate operating a backend.

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

Splitforms is the form backend for Tailwind CSS 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 codeHTML · 27 lines

Drop into any Tailwind CSS project.

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

form.htmlhtml27 lines
01<form action="https://splitforms.com/api/submit" method="POST">
02 <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03 <input type="hidden" name="subject" value="New consultation request">
04
05 <label for="name">Full name *</label>
06 <input id="name" type="text" name="name" placeholder="Tomás López" required>
07 <label for="email">Email *</label>
08 <input id="email" type="email" name="email" placeholder="tomas@example.com" required>
09 <label for="phone">Phone *</label>
10 <input id="phone" type="tel" name="phone" placeholder="+1 555 0184" required>
11 <label for="topic">Topic *</label>
12 <select id="topic" name="topic" required>
13 <option value="">Choose…</option>
14 <option>General inquiry</option>
15 <option>Strategy</option>
16 <option>Financial planning</option>
17 <option>Legal advice</option>
18 <option>Other</option>
19 </select>
20 <label for="details">What do you need help with? *</label>
21 <textarea id="details" name="details" placeholder="Be specific so we can match you with the right advisor." required></textarea>
22
23 <!-- honeypot — bots fill every field -->
24 <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
25
26 <button type="submit">Send</button>
27</form>
§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first consultation 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 consultation request into your Tailwind CSS project

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

snippethtml
<form action="https://splitforms.com/api/submit" method="POST">
  …
</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 consultation 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?
§ 03cTailwind CSS production notesnative path · deploy · gotchas

What changes when this consultation request lives in Tailwind CSS.

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

without splitforms

Tailwind is a styling layer — it has no opinion on form submission, networking, or backend. The 'native' approach means writing utility classes for visual treatment and bringing your own delivery mechanism: a Next.js route handler, a Vite + React + fetch combo, an HTMX endpoint, etc. Tailwind UI ($299 one-time) sells styled form templates but doesn't include a backend either. Tailwind v4's @theme directive changes how tokens are defined, not what forms do. The shape of the problem stays: utility classes for look-and-feel, splitforms for delivery. Drop the snippet on this page into any framework with Tailwind configured and you have a styled, working form in 60 seconds.

deploy notes

Tailwind is purely a build-time concern — utilities are compiled into your CSS bundle, then deployed as static assets. JIT mode (default in v3+) and the v4 engine both purge unused classes; if you build form HTML inside a JS template literal at runtime, Tailwind can't see those classes and purges them — add to safelist or move markup into source files. Works on every host. For dark mode toggled via class, set darkMode: 'class' in v3 config or use @variant dark (.dark &) in v4 CSS. The @tailwindcss/forms plugin resets input styles aggressively — pick one (plugin OR explicit utilities), not both.

Tailwind CSS gotcha

JIT mode purges classes inside template strings

If you build the form HTML inside a JS template literal, Tailwind's JIT can't see your classes and purges them. Either move the markup into a .html / .tsx / .vue file, or add the classes to your safelist in tailwind.config.js.

Tailwind CSS gotcha

Tailwind 4's @theme replaces tailwind.config.js — focus colors break

Tailwind 4 (released 2026) moved theme tokens into CSS via @theme { … }. If you copy a Tailwind 3 snippet using focus:ring-orange-500, the orange-500 token has to be defined in your @theme block or it falls back to no ring color. Use a CSS variable: focus:ring-[var(--accent)] for portability.

Tailwind CSS gotcha

Form gets no styling at all — Preflight not loaded

If you're embedding the form inside a Shadow DOM, iframe, or a CMS that strips global CSS, Tailwind's Preflight (the global reset) doesn't apply. Inputs render with browser-default white backgrounds, ignoring bg-white if you set it in @apply but not as a utility on the element. Always use utilities directly on the input.

Tailwind CSS gotcha

Dark mode classes need `class` strategy explicitly set

Tailwind defaults to media-query dark mode (prefers-color-scheme). If your form has dark:bg-gray-900 and you toggle dark mode via a class on <html>, you need darkMode: 'class' in tailwind.config.js (Tailwind 3) or @variant dark (.dark &) in your CSS (Tailwind 4).

PATTERN A

Pattern A — utility-first inline styles

Every input gets utilities directly on the element — explicit, JIT-safe, no @apply indirection. Works in HTML, JSX, TSX, Vue, Svelte, Astro identically. Use the same wiring for the consultation request fields on this page.

pattern-a.htmlhtml12 lines
01<form action="https://splitforms.com/api/submit" method="POST"
02 class="max-w-md mx-auto space-y-4 p-6 bg-white rounded-2xl border border-gray-200">
03 <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04 <input name="email" type="email" required
05 class="w-full rounded-lg border px-3 py-2 focus:ring-2 focus:ring-orange-500" />
06 <textarea name="message" rows="4" required
07 class="w-full rounded-lg border px-3 py-2 focus:ring-2 focus:ring-orange-500" />
08 <button type="submit"
09 class="w-full bg-orange-600 hover:bg-orange-700 text-white font-semibold py-2 rounded-lg">
10 Send
11 </button>
12</form>
PATTERN B

Pattern B — dark-mode + accessible focus states (Tailwind v4)

Pairs dark: variants with focus-visible: for keyboard-only focus rings. Uses CSS variables for accent color so the same component works in light/dark without rewriting utilities. Use the same wiring for the consultation request fields on this page.

pattern-b.htmlhtml9 lines
01<form action="https://splitforms.com/api/submit" method="POST"
02 class="max-w-md mx-auto p-6 rounded-2xl border bg-white dark:bg-zinc-900 dark:border-zinc-800">
03 <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04 <input name="email" type="email" required
05 class="w-full rounded-lg border bg-white dark:bg-zinc-950 px-3 py-2
06 text-gray-900 dark:text-zinc-100
07 focus-visible:ring-2 focus-visible:ring-[var(--accent)]" />
08 <button class="w-full bg-[var(--accent)] text-white py-2 rounded-lg">Send</button>
09</form>
§ 04Field-by-field rundown5 fields · names you POST

What every field actually does.

Each field below ships in the consultation 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 · Tomás López
emailREQUIRED
EMAIL

Email

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

placeholder · tomas@example.com
phoneREQUIRED
PHONE

Phone

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

placeholder · +1 555 0184
topicREQUIRED
SELECT

Topic

Dropdown — keeps responses normalised so you can filter the dashboard.

General inquiryStrategyFinancial planningLegal adviceOther
detailsREQUIRED
TEXTAREA

What do you need help with?

Free-text context — what the visitor actually wants you to know.

placeholder · Be specific so we can match you with the right advisor.
§ 05Consultation Request on other frameworks21 frameworks · same backend

One backend. Every framework.

The same consultation request template works on every framework splitforms supports. Pick yours.

§ 06Questions6 answered

Consultation Request on Tailwind CSSFAQ.

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

01Does this consultation request work on Tailwind CSS?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Tailwind CSS site without server-side code, plugins, or SDKs. Drop the snippet into a Tailwind CSS page or component and submissions land in your splitforms dashboard.
02How much does the consultation request cost on Tailwind CSS?
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, email, phone, topic…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the consultation 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 Tailwind CSS as on any other framework.
05Can I send the consultation 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 Tailwind CSS 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.
§ 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 consultation request on Tailwind CSS in 60 seconds.

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

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