You don't need a form strategy. You need six forms, none of them longer than a screen or two, and a rule for what happens after someone presses submit. Founders tend to spend an evening on the form and no time on the rule, then wonder why the demo request from three weeks ago never got a reply.
So this page starts from the forms, not the tools. For each of the six you get the fields to ask for, the ones to leave out, the place the response should land and who picks it up. A short tool list follows near the end. If you're comparing form builders on logic, payments and price in depth, go to the custom form builder comparison instead.
The six forms on one page
Copy this table into your notes and fill in real names. The follow-up times are our suggestions, chosen for a very small team, and you should change them to what you'll really do. A promise you keep beats a fast one you miss.
| Form | Fields | Where the response goes | Who follows up, and how fast |
|---|---|---|---|
| Waitlist | Email, one question on the problem they have | Email tool or a contacts list | Automatic confirmation; a founder reads answers weekly |
| Demo request | Work email, name, company, team size, what they want to solve | Sales pipeline, as a new lead | Founder or first salesperson, same working day |
| Investor intro | Name, firm, email, check size, how they heard of you | Fundraising tracker, not the sales pipeline | Founder personally, within 24 hours |
| Job application | Name, email, phone, CV, one role-specific question | Applicant tracker, per role | Hiring manager, within 5 working days |
| Feedback or NPS | Score from 0 to 10, one open question, optional email | Shared sheet or product notes | Product owner, weekly; anyone scoring low gets a reply |
| Event signup | Name, email, company, one note field | Attendee sheet, plus your contacts afterwards | Event owner: confirmation at once, reminder the day before |
Every field is a small tax on completion, so each one has to pay for itself. Under GDPR's data minimisation principle, personal data must also be "limited to what is necessary" for the purpose, which gives you a second reason to cut. Before you add a field, ask what you'd do differently depending on the answer. If the honest answer is nothing, delete it.
Waitlist: ask one extra question
A waitlist form is an email field and a button. Add one question, and make it the one you most want answered, such as "What are you using today?" or "What's the hardest part of this for you?" Those free-text answers are often the most useful early research you'll get, and they cost the visitor ten seconds.
Skip job title, company size and phone at this stage. Someone curious about a product that doesn't exist yet won't hand those over, and you can't act on them yet anyway.
The usual mistake is having no confirmation. A person signs up, sees a thank-you line and hears nothing for four months, so by launch they've forgotten you. Send one confirmation right away that says what you're building and roughly when, then write monthly. Embed the form on the landing page rather than linking out to it, so you lose nobody in the extra click.
Demo request: speed beats fields
This is the only form on the list that can make money this week, so give it the fastest route. Ask for a work email, name, company, team size and one line on what they want to solve. Team size lets you sort, and the last field gives you your opening sentence on the call. Leave out budget and timeline, which you'll learn in the conversation and which put people off on a form.
Consider skipping the back-and-forth entirely. Send people from the thank-you page straight to a booking link, so that the request and the meeting happen together. Every response should become a record in your sales pipeline the same day, whether by an integration or by hand. A demo request that lives only in a spreadsheet tab will be forgotten during your first busy week.
Who follows up: one named person, even if that's always you. Prepare with the discovery questions generator and the demo script generator.
Investor intro: keep it off the sales pipeline
Few startups think they need this one until they've raised once. Then an angel asks "how do I reach you about the round?", and the answer is a link on your site, your deck page or your update email. It filters people gently and gives you a record of who came in and how.
Ask for name, firm, email, typical check size and how they heard of you. Add a URL field for LinkedIn if you like. Don't ask for a thesis or a fund size. Serious investors won't fill in an essay for a pre-seed startup, and you can find those on their site.
Where it goes is the part that matters. Investors move through different stages from customers, and a partner at a firm isn't a lead. Put these in a fundraising tracker or CRM so they sit next to your round. Don't let the form automate your first reply either. This is a relationship, so write it yourself, using the investor follow-up generator for a first draft if you're stuck.
Job application: decide whether you need a form at all
A general form builder can do this, but it's the form where a purpose-built tool saves the most, since you need stages per candidate and not only rows. If you're hiring one person this year, a form plus a sheet works fine. Use a file upload for the CV, ask one role-specific question that shows how the person thinks, and write a clear job description first, since that does most of the filtering.
Check how your tool handles uploads. On Google Forms, a respondent has to sign in to a Google Account to upload a file, which is an unnecessary hurdle for applicants.
Be strict about what you collect. Don't ask for date of birth, photo, marital status or salary history unless a lawyer in your country tells you to, and decide how long you'll keep rejected applications. In Nautis, this isn't a Custom forms job: Jobs and recruitment gives you a careers page, an application form and a candidate pipeline. That form asks for name, email, phone, resume and a cover letter. The guide says there aren't custom screening questions yet, so if your one role-specific question matters, you'd need a separate form.
Feedback or NPS: two questions, then read them
NPS is a single question with a standard scale. Bain's method asks how likely someone is to recommend you to a friend or colleague, from zero to ten. Promoters score 9 or 10, detractors score 0 to 6, and the score is the percentage of promoters minus the percentage of detractors. For example, in an illustrative survey with 40 responses, 16 promoters and 8 detractors, that's 40% minus 20%, a score of 20.
Then ask one open question: "What's the main reason for that score?" The number tells you whether to worry, and the text tells you what to do. With a small customer base the score will swing wildly, so spend your time on the comments. Make the email field optional and say what it's for: "Leave your email if you'd like a reply."
The rule that makes it useful: anyone who scores low and leaves an email gets a personal reply within a week. If you want to go deeper with those people, use the customer interview script generator. Don't survey the same customer more than about once a quarter.
Event signup: the follow-up is the point
Whether it's a meetup, a webinar or a demo day, this form is easy, and the mistake comes after it. Ask for name, email, company and one optional note, such as dietary needs or a question for the speaker. Add a date picker only if there are several sessions.
Send a confirmation at once and a reminder the day before, and put the location or call link in both. Share the form in places where people are already gathering. A QR code on a poster lets people sign up in the room for your next one, and it shows which placement worked.
After the event, the list is the asset. Send a thank-you within two days with the recording or slides, and move anyone who asked a real question into your contacts or pipeline with a note on what they asked. If the event sells tickets, you need a form with payments, so check how each tool handles that on the comparison page, or use a dedicated events tool.
A short list of tools for founders
Pick one and build all six in it. A single login and one consistent look matter more than small feature differences. These prices come from each vendor's own page, as of November 2026.
| Tool | Start at | Good for | Watch for |
|---|---|---|---|
| Tally | $0, unlimited forms and submissions under fair use; Pro $29 a month | Most founders' first choice on cost, with logic, payments and Notion, Sheets or webhook connections at no cost | Its name stays on forms until Pro |
| Google Forms | Included in Workspace plans; couldn't confirm a price for personal accounts | Internal feedback and low-stakes signups, with responses in Sheets | Uploads need a Google sign-in |
| Jotform | $0 Starter: 5 forms, 100 submissions a month; Bronze $39 a month | Forms that need payment gateways or templates | Starter's 5 active forms barely covers this list |
| Typeform | Free version with limited responses; Basic $39 a month for 100 responses | Conversational forms where feel matters | Costs rise with responses, and branding removal starts at Plus |
| Nautis Custom forms | Part of Nautis plans from $49 a month, 14-day trial | Teams already running leads, fundraising and hiring there | No documented conditional logic, payments or webhooks |
Our view: unless you already pay for something suitable, start with Tally, and change only when a real limit gets in your way. Nothing here needs a developer, and that includes the embed, which is a snippet you paste into your site builder.
Building these forms in Nautis
If you already use Nautis, you have most of this. Go to Marketing, then Custom Forms, and click Create Form. There are templates, such as a contact form and an NPS survey, or a blank form. The Rating field offers an NPS scale from 0 to 10, and Stepper Mode breaks longer forms into steps. Share gives you a link, embed code, short URL and QR code.
Being plain about the routing, which is the point of this page: the Custom forms guide describes entries living on an Entries page, with CSV or JSON export. It doesn't document responses flowing automatically into the Leads CRM, Contacts or the Fundraising CRM. So for a demo request or an investor intro, someone has to look at entries and create the record by hand. The Leads CRM can import a spreadsheet, and a deal in the Fundraising CRM is added with Add Investor. Demo bookings don't need a form, as Meetings and scheduling gives you a booking link.
Nautis is also not worth buying for forms alone, since its plans start at $49 a month as of November 2026. It makes sense if you want those destinations in one workspace, you accept the manual step, and you're willing to learn a young product. If you need to route responses without touching them, a tool with webhooks and an automation service will serve you better.
FAQ
What is the best no-code form builder for startups on a tight budget?
Start with Tally. As of November 2026 its $0 option lists unlimited forms and submissions under fair use, with conditional logic, payments and connections to Sheets and Notion. Change tools only when you hit a real limit, such as needing a custom domain or its branding removed.
Is a no code form builder for startups enough without a developer?
Yes. Publishing a form, embedding it with a pasted snippet and exporting responses all work without code. Routing responses automatically usually means connecting a native integration or an automation tool such as Zapier or Make, which is also no-code but takes some setup.
What fields should a demo request form have?
Keep it to work email, name, company, team size and one line on what they want to solve. Leave out budget and timeline, which you'll learn on the call. Send every response to your sales pipeline the same day, with one named person following up.
Do Nautis forms send responses to the Leads CRM automatically?
The help center doesn't document that. Entries appear on the form's Entries page and can be exported as CSV or JSON. The Leads CRM accepts spreadsheet imports, so plan for a person to move qualifying responses across.
Should a startup use a form builder for job applications?
For one hire, a form with a CV upload and a sheet is fine. Once you have several roles or candidates, use something with stages per candidate. Nautis Jobs and recruitment includes a careers page and application form, but has no custom screening questions yet.