Loading tutorials…
Loading tutorials…
Tally's block-based editor is forgiving — which is why most teams build forms that look fine and convert at 18%. This walks through the build path that lands forms at 35-45% conversion.
Who this is forFounders and marketers building their first or fiftieth Tally form for lead capture, demo requests, or customer feedback. If your form converts below 25%, the build is the problem — not the traffic.
What you'll need
Step 1
Every form has one job — qualify a lead, book a demo, capture an email. Write it down before opening the editor.
Open a doc. Write: "This form succeeds when [X happens]. The single CTA is [Y]." If you cannot fit it in two sentences, your form is doing too much.
Lead-capture forms succeed when a qualified email is captured. Demo forms succeed when a calendar event is booked. Survey forms succeed when honest data is collected.
Pick the field that represents success and design every other question to defend it. Every additional question costs 5-10% conversion. Be ruthless.
Rule: if a question does not directly support the one job, cut it.
Step 2
Open Notion/Airtable/HubSpot. Note the exact field names. Build the Tally form to match — same field names, same field types.
Open the downstream destination (Notion database, Airtable base, HubSpot contact properties).
Note every required field name + type. Match Tally blocks exactly: Email block → email field, Number block → number field, Multi-choice → select.
Avoid renaming. If Notion uses "Company name," Tally should use "Company name" — not "Business." Field-mapping errors are the #1 source of broken syncs.
Document the mapping in a Notion doc or sheet. You will reuse it for every form.
Step 3
Tally supports "Standard form" (all questions on one page) and "Form sections" (one question per page, conversational). Pick based on context.
In Tally, click "New form" → start blank.
Decision: one-page form for short, low-friction asks (email capture, newsletter signup) — better completion rate on mobile. Section-by-section for longer flows (multi-step demo qualifier, onboarding wizard) — better per-question completion, lower drop-off.
Rule of thumb: under 5 questions = one page. Over 5 questions = sections (use the "Page break" block).
Avoid mixing modes mid-form unless you have a clear reason. Consistency reduces user friction.
Step 4
Easy questions first (email, name). Hard questions in the middle (budget, team size). Final ask last (calendar, payment).
Order matters more than most builders realize. Tally tracks per-block drop-off, and you will see the same pattern across accounts.
Q1-2: lowest-friction (email, first name). Get commitment early — sunk-cost bias keeps users engaged.
Q3-5: qualifier questions (role, company, use case). These cost the most conversion but yield the most data.
Q6+: high-friction asks (phone, budget, signature). Place here because users who reach Q6 have already invested 60+ seconds — they will push through.
Final block: clear single CTA — book demo, submit, get access. Avoid double CTAs.
Step 5
Every required field needs a one-line explanation. Every form needs at least one trust signal above or below the CTA.
For each question, add a description (the gray subtext under the question title). Format: "Why we ask: [reason]." Example: "Why we ask: so we can match you with the right specialist."
Add a Text block before the first sensitive question (email, phone) with: "We never share your data. Used only for [purpose]."
Below the submit button, add a Text block with social proof: "Trusted by 200+ companies" or "GDPR compliant, no spam."
Tone matters. Tally forms feel personal — keep copy conversational, not corporate.
Step 6
The thank-you page is the form. Custom redirect to a Calendly link, a thank-you page, or a thank-you message with social proof.
Open Form settings → Thank you page. Pick: (a) custom message, (b) redirect to URL.
For demo-request forms: redirect to a Calendly or Cal.com booking page. Embedded directly is even better.
For lead-capture forms: redirect to a thank-you page on your site with a video, testimonial, or next-step CTA.
For surveys: custom message with "Your response has been recorded. We may follow up at [email]."
Pass form fields into the redirect URL (e.g., `?email={email}&name={name}`) so the next page can personalize.
Step 7
Submit from incognito mobile + desktop. Verify Notion/Airtable receives data, redirect fires, Slack notification arrives.
Open the form on incognito desktop and incognito mobile. Submit with real test data.
Verify: data appears in Notion/Airtable, redirect fires correctly, Slack notification arrives within 30 seconds.
Check on three devices: iPhone, Android, desktop. Tally is responsive but custom CSS sometimes breaks on mobile.
Delete test responses from both Tally and the downstream system.
Common mistakes
Asking for too many fields
What goes wrong: Every extra field costs 5-10% conversion. A 10-field form converts at 18%. A 4-field form converts at 38%. Each unnecessary field is costing you 1-2 leads per 100 visitors. At $50 LTV per lead, that is $50-100 per 100 visitors of lost revenue.
How to avoid: Audit every field. Ask: "Could I get this data from enrichment (Clearbit, Apollo) after the form?" If yes, cut the field. Target 4-6 fields for lead capture.
Hiding the CTA below the fold
What goes wrong: Users do not realize they reached the end of the form. They bounce thinking the form is broken. ~15-25% of would-be submitters never click submit.
How to avoid: Keep the submit button visible at scroll end. Add a "You're almost done" Text block before the submit on long forms.
No microcopy explaining sensitive fields
What goes wrong: Phone-number field has 40% drop-off. Budget question has 50% drop-off. Users skip or abandon when they do not understand why you need the data.
How to avoid: Every sensitive field gets a "Why we ask" description. Test: would a stranger know why this field exists? If no, add copy.
Generic thank-you page
What goes wrong: User submits, sees "Thanks!" with no next step. They close the tab. You lose the moment of peak engagement. ~30-50% of post-submit nurture opportunity is lost.
How to avoid: Redirect to a real page with next steps: book a call, watch a video, read a case study. Pass the email field in the URL so the page can personalize.
Not testing on mobile
What goes wrong: 60%+ of form traffic is mobile. A form that renders fine on desktop but breaks on iOS Safari loses half your conversions silently. You will not notice for weeks.
How to avoid: Test every form on incognito iPhone Safari + Android Chrome. Tally is responsive, but custom CSS can break on touch devices.
Recap
Done — what's next
How to set up a Tally account the right way
Read the next tutorial
Hand it off
Building one form is a project. Building 10 forms across a real funnel — landing pages, demos, onboarding, NPS — is a job. A vetted conversion-funnel specialist will build, test, and continuously optimize. From $14-16/hr — most engagements land at $400-1,000/mo.
See specialist rates
4-6 fields for general lead capture. 7-10 fields for high-intent demo-request forms where qualification matters. Above 10 fields, conversion drops below 15% on most accounts.
Under 5 fields: single-page (better on mobile). 5-15 fields: multi-step with logic jumps (better per-question completion). Over 15 fields: reconsider the entire form first.
Tally's response analytics show per-block drop-off. Open Form → Analytics. The biggest single drop is the field to cut or rephrase first.
Tally has no native A/B testing. Build two variants and split traffic at the URL level using a tool like VWO, Google Optimize alternatives, or simply running each variant for 7 days and comparing.
Three things: custom font (Pro), brand colors set in workspace, and conversational microcopy in every description. Avoid corporate language — Tally's strength is that forms feel personal.
Tally
Tally is free for almost everything — which makes most setups sloppy. This walks through the right setup path: workspace structure, brand kit, GDPR, and the integration baseline that prevents 80% of the rework that hits at month three.
Tally
Logic jumps are what turn a static form into a smart one. They are also where most Tally forms quietly break. This walks through the branching patterns that actually hold up at scale.
Tally
Tally's embed code is dead simple. Picking the wrong embed type is where most teams lose 20% of conversions. This walks through inline vs. popup vs. slider vs. full-page — and when each one wins.
Tally
DIY forms are great — until your conversion rate caps at 18% and you cannot tell why. Here is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you are on.