Most website forms do one thing: they send an email. The email gets buried, and the lead dies in an inbox.
This website treats forms differently, and it supports three kinds of them, because forms actually do three different jobs.
- Get leads.
- Book appointments.
- Get paid via Stripe.
Each job has a form type built for it, and all three feed the same place.
The forms are in the free codebase. What the Second Brain OS Website Operator adds is the wiring underneath: it connects each form type to your CRM so a submission becomes a Lead, Purchase or appointment event on a contact record, and points the data webhook at wherever else you want the payload to go. That is the outcome this post is really about. Your CRM fills itself from the website, every lead has a record from the first touch, and the receptionist from the earlier posts and the site are writing to the same person.
Native forms: get leads
The first kind is the standard form, built directly into the site's own code. Email capture, contact requests, simple lead forms.
Because they are part of the site rather than an embed from elsewhere, they load instantly, match the design exactly, and are fully yours.
They are the right tool for the top of the funnel, where every extra second of load time costs you someone.
A submission here does not disappear.
The person lands in your CRM as a contact, with the submission attached to their record as an event. And if you want, also in a Google Sheet or any destination of your choice.
Tally forms: get leads, and get paid
The second kind is Tally. Tally is, on the face of it, a form builder.
The reason it earns a place here is what it handles that a simple form should not try to:
- Multi-step flows.
- Qualification questions.
- File uploads.
- Conditional logic.
And one thing more, which changes its job description entirely: Tally connects to Stripe.
Stripe is the payment layer most of the internet runs on, and with the two connected, the same form that qualifies a lead can take their money. Order forms, deposits, paid consultations, all without building a checkout.
That is the moment a form stops being lead capture and becomes revenue.
A Purchase event fires, and the emails post shows what you can trigger from it.
Calendly embeds: book appointments
The third kind does not look like a form, but it is one.
A Calendly embed asks the visitor questions, and the "submission" is an appointment on your Google Calendar.
Every Calendly embed on this site carries tracking context, so you know which page, which offer and which campaign produced each booking.
Bookings stop being anonymous calendar entries and become attributable outcomes.
If the visitor arrives via chat instead of a page, the receptionist books them directly. Same calendar, either door.
One person, one record
Underneath all three types sits the same rule: whichever form someone touches, it lands on their contact in your CRM as an activity event.
And the site remembers.
Once someone has given their name and email, the next form they meet, including the booking form, is already filled in.
A small courtesy on the surface; in practice it is the difference between a booked call and an abandoned one.
Lead, payment, appointment. Three forms, three jobs, one record per person.
A note on prices: every price in this series is the price inside its funnel, where each purchase unlocks the next. Bought on its own, outside the funnel, the same product can cost up to 30% more.
Next up: what those form events can trigger, emails.