Early Access Signup Form Template
Fill your first cohort with the right users, not just the fastest ones — a signup that measures fit and urgency in four taps.
We're letting people in gradually, in small groups. Tell us what you're working on and how badly you need this — it genuinely decides who gets in first.
Early access is a selection problem disguised as a signup problem. Anyone can collect emails; the hard part is knowing, when you have fifty invite slots and five thousand names, which fifty. This form is built to make that decision cheap — every question maps to a column you will actually sort by on invite day.
Why these fields. Email is the invitation channel, nothing more asked, nothing wasted. The "what are you building" free-text is the fit detector: one honest sentence separates the developer with a live use case from the tourist collecting beta badges, and reading a hundred of these takes twenty minutes that will save your support team a month. The platform question is capacity planning — if most of the queue wants iOS and your iOS build lags, that number should reorder your roadmap, not just your invites. And the urgency scale (1 to 5, anchored "someday" to "yesterday") is a self-report that works precisely because it is cheap: people who slam 5 and describe a real project are your activation cohort, while the honest 2s are your future waves.
Cohort selection is a sort, not a project. On invite day, export the CSV and sort by urgency, then skim the build descriptions in order — or filter by platform when a build ships. The form has already done the interviewing.
The invite_code field powers member-gets-member growth. When you invite someone, hand them a personal link like ?invite_code=wave1-ana. Signups arriving through it carry the code invisibly, so you can trace which early users pull in the best next users — the strongest expansion signal an early product gets — and prioritize their friends accordingly.
What we left out. Company, role, team size, phone. Pre-launch curiosity is fragile, and every identity field you add trades queue size for data you can infer later from the email domain and the build description. There is also no "agree to feedback calls" checkbox — ask for the call after they're in and delighted, not before.
Who uses this. Product teams gating a private beta, developer-tool startups sequencing API access, and hardware companies staging pre-orders behind readiness.
Make it yours. Rewrite the platform options to your real surface area, tune the urgency anchors to your product's vocabulary, and keep the intro's promise — actually use the answers to sequence invites, because early users compare notes. Turn on email notifications for a daily pulse of who's queueing, and let the responses view be your invite-day war room.
Frequently asked questions
How should I pick who gets invited first?
Export the CSV and sort by the urgency score, then read the "what are you building" answers from the top. High urgency plus a concrete use case is the profile that activates and gives real feedback.
What does the hidden invite_code field do?
It records a code from the share link (like ?invite_code=wave1-ana) without respondents seeing it. Give invitees personal links and you can trace which members recruit the best next members.
Can I cap the queue or close signups?
Yes — Settings supports closing by date or after a set number of responses, with a custom closed message. A visible cap ("first 500 get wave one") also adds honest urgency to your launch post.
Why an urgency scale instead of a yes/no question?
A five-point scale with labeled ends gives you a sortable gradient instead of a binary everyone answers the same way. The anchors ("someday" vs "yesterday") keep self-reports roughly honest.