Thirty seats next cohort. Applicants see where they stand.
A hard cap for the cohort and a short application form. Every applicant sees their place in line, you read the answers in one export, and the form tells the 31st person the truth.
The problem
The interest form has 400 names and the cohort has 30 seats
You put a Google Form on the landing page and it collected everyone who was mildly curious. Now you have to email 370 people that they did not get in, and the 30 you want never heard back. Nobody who signed up knows whether they are 5th or 350th.
The recipe
Exactly what the button sets up
Capacity, reset time, opening hours, and the form fields. It is a starting point, not a cage. Every value is editable in Settings and the builder.
Recipe
Spring cohort
- 30 seats total. The form closes when the 30th applicant joins.
- No opening hours. Open the list when you announce the cohort and pause it after.
- Asks for name, current role, and what they want to build.
- Applicants see their position in line.
- The running count is hidden, so applicants only see their own number.
- Capacity
- 30 in total
- Signups open
- Any time
- Form asks for
- Email, Name, Current role, What do you want to build during the course?
- Counter on the form
- Hidden
How it works here
How the list works
Cap the cohort
Thirty seats. The form closes at 30 instead of collecting a mailing list.
Ask real questions
A dropdown for role, a long text field for goals. Multi-step forms if the application is long.
Show the place in line
"You're #18." Applicants stop emailing to ask.
Hide the count
Turn off the public count when you do not want 30 of 30 on the page.
Read the answers
CSV export with position, email, role, and the full text of every answer.
Reopen for the next cohort
Pause between cohorts. Clear the list or raise the cap when the next one opens.
Why it holds up
What matters most
You stop over-collecting
A capped list is a courtesy. People who cannot get in are told so on the spot.
Positions are honest
Assigned under a database lock, never reused, visible in the export in order.
The form looks like the course
Inter, your accent color, rounded corners. Tokens, set once.
It works with your site
A script tag on Webflow or Framer, an iframe on anything else, or a POST from your own form.
FAQ
Questions people here ask
Can I accept applicants out of order?
Yes. The position is a number, not a rule. Read the export and invite whoever fits.
Can I charge tuition through the form?
No. Unwaited does not take payments. Send a checkout link to accepted applicants from your own tool.
Does it email applicants when they are accepted?
Applicants get a confirmation with their place in line when they apply, and a "your turn" email when you send it from the Entries tab. Acceptance details still go out from your inbox.